Use just one socket for now and always first receive the pending data and only after that try sending more. You can check that the socket is still connected, that's OK, but do it just once, before trying to receive/send data.

I'd start with some simple code so it's easier to follow - forget about DNS and such, just open a client socket, connect to the server and transmit/receive your data. How many sockets do you open to this server? The code that you use seems kind of complex so I cannot really asses what happens under all circumstances. I see that there are other conversations from the same client to the server: there are 6 conversations of which only 1 really carries some data.

Why exactly this happens is not very easy for me to tell. 192.168.2.110 retransmits its data but the client doesn't receive it and from that moment on the conversation is broken, each side repeating its data until the channel is closed. If (TCPIP_TCP_PutIsReady(appData.socket) >= strlen(buff_httpReq)) I still dont know how to upload here in the forum The log is here įrom the log it is clear that around second 108 of the conversation the TCP client (192.168.2.201) is no longer receiving data. Hello, I have a client with a simple code case APP_TCPIP_SENDING_REQUEST:

What is tcp retransmission wireshark