system.net.sockets and windows 10 error?

927 Views Asked by At

I'm having a very strange problem with an application in windows 10. It consists of several .exe in the same computer communicating between them with sockets using system.net.sockets library. The problem I have is that after installing Windows 10 in a new computer, install all windows updates and then installing that application, connection to sockets doesn't work correctly and the application fails. The strangest thing is that if you leave the computer alone for 1-2 days the applications starts working just fine. The same has happened after installing version 1803 update, it stops working and then works one or two days later. Any idea of what can it be? Has anyone seen something similar?

1

There are 1 best solutions below

1
On

It really seems to be related to the 1803 update you mentioned.

Symptoms:

  • Running an application from a network share will fail when creating a socket;
  • Copying the very same application to a local drive/path will work just fine, without any further modification.

We are also struggling with this while connecting to an Oracle database (both ODBC and ODP.NET) and it seems the issue has recently been acknowledged:

https://support.oracle.com/knowledge/Oracle%20Database%20Products/2399465_1.html

It also seems this is a recurrent Windows bug:

Sorry, no effective solution at the time (other than copying the app binaries to a local folder). I'll update this answer once we get a better solution.


OK, looking a little further I found here in SO that this might be related to a SMBv1 network share, which describes the environment we had here (the network share was disabled because of another bug we faced - thanks MSFT).

Re-enabling SMBv2 / SMBv3 on the server solved the issue.

Related post:

After Windows 10 update 1803 my program can't open a socket when running from network share