Hot answers tagged tcp
When a client program (such as a browser) connects to a server, it opens a socket. And (unless the program specifies one, which is very rare), the operating system assigns a unique port number to the socket. This will commonly be in the range 1000-2000. The source IP is, of course, the address of the client host. The server determines the destination ...
I had the same problem and fixed it by : finding the PID with netstat -o Kill it with process xp Interesting to note that netstat can sometimes return a pid but not the corresponding executable name !
The RST is sent immediately and the data is discarded.
Large packets with "don't fragment" are normal. That's how the OS performs MTU discovery – instead of letting the network quietly fragment the packets, it expects an ICMP "Fragmentation required" error to be returned (which would have the correct MTU). If you see the large packets getting retransmitted, it means some router in the middle is misconfigured ...
I think a duplicate ack happens only when the receiver sees a gap in the sequence numbers, meaning a packet was dropped on the way to it; so the problem starts in the direction from 192.168.0.8 to the remote server. The fact that there are no acks (not even duplicate acks) back despite several retransmissions probably means that something is totally screwed ...
Only top voted, non community-wiki answers of a minimum length are eligible