Socket 10054 error - not your normal issue - development problem - from the server but why?
Posted on 2005-04-28
Greetings. Things are getting testy in my development lab, and I need some ideas as to how to defuse a situation that's developed. Our environment is mainly Windows Sockets talking to an embedded device we currently have under development. The device has an embedded DHCP server within it, and supports a dedicated ethernet communications network for the application.
One of our tools uses winsock to communicate with the device. Usually, things work fine, but at times, the socket connection fails with a 10054 error - connection reset by peer.
It is my understanding that this error is initiated by the server (server in this context is the application accepting socket connections - our device). True or False?
Now, I know y'all can't help me with the application, and I'm treating the code in the device as a black box. I've never written an extensive server application, but what examples I've seen, I've not noticed a specific command that generates a 10054 error. Is this down inside the stack and something that just happens? What would I do if I were a server and wanted to generate a 10054 error?
I appreciate any feedback.