Ads error 5381

[bobvolz]

I have a client with a Windows 2018 Server running Ads 12. He has a 25 user Ads license. About 18 of his PC's run just fine with my app which runs on the C: drive in a folder that contains the .exe files and all the xBase and express and xB2net DLLS. I have verified that they are all there. Now, 4 of the PCs, which were fine on Saturday, won't run my app. The error is 5381. Even when I try to run xDot from the f: drive on the server I get the same error. Some of these PC's are Windows 11. Is anyone having any issues like this? I have restarted the server which restarted Ads and I've made sure all the DLLS are OK.
There is a lot of confusing comments on the Web regarding this error. Has anyone solved this problem? I use UNC for the network paths and even if I map the drives it makes no difference.
Any thoughts on this would be appreciated. I know at least one of the PC's had a Windows update over the weekend.

Bob Volz

[k-insis]

Might be this one:

Do you still use shraing over SMBv1? (If you don't know sysadmin should know) It is XPP errror because of SMBv1 (which should not be used anymore) related.

Programs run from SMBv1 share are not allowed to create sockets.

https://community.sap.com/t5/technology ... p/12511016

I have a client with a Windows 2018 Server running Ads 12. He has a 25 user Ads license. About 18 of his PC's run just fine with my app which runs on the C: drive in a folder that contains the .exe files and all the xBase and express and xB2net DLLS. I have verified that they are all there. Now, 4 of the PCs, which were fine on Saturday, won't run my app. The error is 5381. Even when I try to run xDot from the f: drive on the server I get the same error. Some of these PC's are Windows 11. Is anyone having any issues like this? I have restarted the server which restarted Ads and I've made sure all the DLLS are OK.
There is a lot of confusing comments on the Web regarding this error. Has anyone solved this problem? I use UNC for the network paths and even if I map the drives it makes no difference.
Any thoughts on this would be appreciated. I know at least one of the PC's had a Windows update over the weekend.

Bob Volz

[bobvolz]

Thanks for the input but that doesn't appear to be the issue. This client put in a Ubiquity network system that replaced the existing firewall and router configuration that worked fine for many years.

I would think that if the vast majority of users can get in and process under ADs then it is probably not a server problem or Ads problem. These Ubiquity products are quite complicated and I'm at the mercy of them right now.

Thanks again
Bob Volz

[bobvolz]

After many hours of diagnosis this turned out to be a DHCP issue involving the 2 Domain Controllers at this site. Very strange indeed. An older Win 2008 Server was there as a backup but was the main Domain Controller and all of a sudden became unstable. Why it only affected 4 PC's out of 24 I do not know but they were all Windows 11.
Bob Volz