.net - Existing connection close when new TCP connections are made -


I have a TCP listener service on which clients connect, I recently received this error related to disconnection started. I connect it to about 20 customers and the connection works fine. But when I connect another 10 customers to the service, the previous connection breaks with 10053 or 10054 error.

Earlier it was used to run with 100 customers, but I'm not sure what the problem might be. Both service and client are running on Windows Server 2003 because I found out that there is a known problem with many TCP connections (related to 10053) in Windows XP.

OK, the errors you receive are very different.

10053 is a WSAECONNABORTED - The connection was revoked. This is usually due to a problem in your app stack (though this sometimes happens).

10054 is a WSAECONNRESET - The connection was reset by peer. This is usually a problem on the other side of the connection.

How are you testing this? Are the "clients" joining the service with something you wrote? If so, you should track what is happening on the client side when you get 10054.

In addition, this could potentially be due to unrelated network issues related to your software (directly). Is there any change in network infrastructure that you are running?


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -