|
-
Oct 1st, 2001, 12:19 PM
#1
Thread Starter
Member
Winsock - Problem closing ports
I'm making a simple chat application using a Winsock TCP connection. It's working fine however when I close the two peer-peer clients and then restart them again, I get a "10048 Address in Use" message. If I run the "netstat" command from the command prompt, I can see that the port I am using is still open. I use the winsock.close method in my attempts to close the connection, but it always leaves one of the peers still listening on a port, even though I call the close method in both peers. After a few minutes, the TCP/IP stack automatically removes that port, but this is an unacceptable waiting period. Right now I'm running both peers on the same computer, using the loopback 127.0.0.1 address. Any ideas on how I can properly close the ports of both clients?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|