My program is half completed for this error. More than 20 days wasted for this problem. I want for it to help you.ĬLIENT - SERVERġ. There is simple diagram for this TCP data flow. In conclusion, I want to close my client socket any time and make new connection to any other servers.įurthermore, let me clarify the network operations using TCP sockets in this KEEP ALIVE option of situation.Īfter deeper investigation, the error code of closesocket is mainly case WSAENOTSOCK: 'The descriptor is not a socket.' I don't know what cause this error code.

Sometimes, the client make error messages 'TCP Spurious Retransmission' to the server. When the client try to open another socket or to do new and any other operations to the server like as data sending or receiving, that makes no normal results, it fail.ĥ. So, the Client cannot close same socket because of the reponse to KEEP ALIVE operation.Ĥ. At that time the server send the control packet to sync of KEEP ALIVE signal, so the client reply to sync msg to the server.ģ. In this video, we explain the differences in retransmission flavors, as well as examine why they occur and what we can do about them. They find their way into our trace files somewhat often. If or when the client close the socket, and I check and run 'netstat' in command line of PC, I always find the same ip:portno is Fin_wait or Close_wait that mean not-closed rightly.Ģ. What is the difference between a regular retransmission and a spurious one What can I do about them if I find them in a trace file Spurious retransmissions are not uncommon.

I am coding a client program using TCP/IP socket comm with Server which have a KEEP ALIVE socket option, and the client receive every data from the server.ġ. For more than 20 years Earth Networks has operated the world’s largest and most comprehensive weather observation, lightning detection, and climate networks.

Wireshark spurious retransmission