I've recently noticed that STN has been staying open for extended amounts of time recently. I did a little poking around and noticed in the open sockets list several sockets that were connected to an IP of a computer that was off. These sockets had a timeout of 7000 seconds or more. Microsoft's developer page was one of these, and also others. Heres a copy of my "Sockets in use" Prot From To Timeout ---- -------------------------------- -------------------------------- ------- TCP 192.168.1.105:1430 agassiz.cs.und.edu:ftp 4659 TCP 192.168.1.20:1450 205.188.247.76:http 7066 TCP 192.168.1.20:1449 205.188.247.76:http 119 UDP 192.168.1.20:1440 minnow-ext.and.net:domain 128 UDP 192.168.1.20:1442 minnow-ext.and.net:domain 129 UDP 192.168.1.20:1444 minnow-ext.and.net:domain 130 UDP/TCP/ICMP free=4093,4093,4096 As you can see there are 2 seperate IP's, the .20 is mine, the .105 is my roomates who is using dhcp with his laptop. The laptop is turned off and no longer on the network as it is his computer bag now. So why does the socket stay open so long? This is not a real issue at home, but at work it could be. We are looking at setting it up for a few computers and don't want to keep a line busy all the time. Another question. What are the "minnow-ext.and.net:domain" entries for? I seem them occasionally, but it is not a valid site. Thanks in advance. Culley _______________________________________________ ShareTheNet maillist - [EMAIL PROTECTED] http://www.webserv.com/mailman/listinfo/sharethenet
