Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an issue with a simple TCP connection between two PCs (both Windows XP SP3) connected by direct wire to each other. These PCs have IP address (server) and on the network adapters used for the direct link.

Below you can see Wireshark screen shots which show the problems we see after an ARP broadcast has been sent from the client. This causes a Windows Socket error 10035 on our non-blocking connection and only after about 1 or more seconds do we receive a FD_WRITE event telling us we can sent again on e.g. the client.

This behaviour is not good for our scenario, but why does communication hang for so long? And what solutions are there? Besides adding a static entry to the ARP cache, which we would like to avoid.



share|improve this question

Have you try repairing TCP/IP Stack. If not:

Open a command prompt (Start->Run->type cmd):

  1. Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

  2. Reset TCP/IP stack to installation defaults: netsh int ip reset reset.log

  3. Reboot and test.

If this does not work you can use this utility:

Repair Windows XP TCP Network Settings With WinSock XP Fix Utility

share|improve this answer
I tried this but it did not help. We ended up adding a static ARP entry instead using the IPHelper API in Windows. – harryuser Jul 12 '12 at 12:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.