To answer your question I had just a simple winsock1.close . I'm sure that closed the socket but there after I could not make another request without creating an error. I could of trapped it but that still would not have allowed me to make another call. All I could do is close down the project or .exe and restart it. I do not know enough about winsocks to go any deeper than that. What I did figure out is that winsocks is a VERY busy control. What I mean is I ran a packet sniffer before I even made a connection request and it was pumping out packets like crazy to and from both computers. Probably because of the listening port.