Chrono79 Posted October 27, 2005 Report Share Posted October 27, 2005 Well, another post about this, I've searched and tried the suggestions in the other posts but none worked for me.XP + sp2 (lvlord patch allowing 500 connections)No router, XP firewall allowing utorrent to connectADSL 256/128utorrent 1.1.7.2utorrent settings:-Maximum global connections: 200-Maximum number of clients per torrent: 40-Maximum number of upload slots per torrent: 3-Maximum global upload rate set at 8kB/sOnly downloading 1 torrent.I've noticed using "netstat -a" a lot (more than 80!) of "CLOSE_WAIT" from the same IP (but from different ports). The IP was from one peer from a torrent. Right now I'm not connected to that peer and the "CLOSE_WAIT" are still there. Is there anything I can do to solve this? (I mean if it's related to my problem: I can't browse because of the time outs, images not loading, etc.) The only way to get rid of the "CLOSE_WAIT" was to disconnect and reconnect to internet (closin utorrent didn't work)I've found this, here:Sometime sockets are in CLOSE_WAIT state, this state conducts when a client doesn't answer back anymore with the last ack N+1. A client crashing while they had a connection is occurring may times as a result the socket isn't closed properly, but much more occurring bad programming is the issue why sockets are closed inappropriate. Most socket developers forget to give a explicit call for shutdown() before the close()/ socketclose(). The shutdown(RDWR) flushes the socket send and receive buffers and tells the other side to stop sending data and that it don't have to expect data anymore. As a close()/ socketclose() is called upon the chance on a CLOSE_WAIT state is out of the question at the side of the software. According to the TCP specifications the server has to stay in CLOSE_WAIT state to be sure that all data (TCP guarantees data transmission) is transmitted. Lot of OS developers saw this problem in the TCP specifications and added a (friendly) timeout to the CLOSE_WAIT that in most cases is adjustable. Windows NT and 2000 doesn't foresee in a CLOSE_WAIT timeout parameter, the only way to free those resources is restarting. When there are structural CLOSE _WAIT(s) on a certain service, the best way is to contact the reseller of the service or client(s) to solve this problem because this is a clear software problem with the service, client(s) or both. Link to comment Share on other sites More sharing options...
Animorc Posted October 27, 2005 Report Share Posted October 27, 2005 Try setting the global max download speed to 15kB/s (or 20kB/s but it might still be slow).And reduce Maximum global connections to 75 or something. 200 is rather high for your connection. Link to comment Share on other sites More sharing options...
Chrono79 Posted October 27, 2005 Author Report Share Posted October 27, 2005 Ok, I'll set that like you said, and will test it for a while. Thanks.Any comment about the "CLOSE_WAIT" thing from ludde or vurlix? Link to comment Share on other sites More sharing options...
tumu Posted October 27, 2005 Report Share Posted October 27, 2005 XP + sp2 (lvlord patch allowing 500 connections)Remove patch, try again. uTorrent doesn't need any system patches.Is there anything I can do to solve this? (I mean if it's related to my problem: I can't browse because of the time outs, images not loading, etc.) Your internets is broken. Fix your internets. Try different networking equipment and/or contact your ISP. Link to comment Share on other sites More sharing options...
Chrono79 Posted October 27, 2005 Author Report Share Posted October 27, 2005 Remove patch, try again. uTorrent doesn't need any system patches.Removed.Your internets is broken. Fix your internets. Try different networking equipment and/or contact your ISP.Mmmm, I don't think so. It's utorrent related. I must say it happens once in a while, not always. I didn't check it with netstat before the last time it happened. I'll keep testing it. Link to comment Share on other sites More sharing options...
hendrix Posted October 28, 2005 Report Share Posted October 28, 2005 i got this advise a while back:go into prefs and set net.low.cpu to true and the same for bt.slow.connect.Did it help? Link to comment Share on other sites More sharing options...
Chrono79 Posted October 28, 2005 Author Report Share Posted October 28, 2005 It was already setted like that, so long it didn't happened again. Now the connections in CLOSE_WAIT state close normally (but there are no more than 20 from the same IP at a time). Link to comment Share on other sites More sharing options...
CaN Posted October 28, 2005 Report Share Posted October 28, 2005 Hi,Go to this thread : http://forum.utorrent.com/viewtopic.php?t=1583I had the same problem and now it's fine !! Link to comment Share on other sites More sharing options...
Chrono79 Posted October 28, 2005 Author Report Share Posted October 28, 2005 Thanks CaN, already checked that. Now it's working fine, setted maximun global connections to 80, download speed sucks but I think it's because of the torrent I'm downloading (tested with a torrent with a lot of seeds and few peers and maxed out dl speed). Link to comment Share on other sites More sharing options...
CaN Posted October 28, 2005 Report Share Posted October 28, 2005 Happy it works for you too Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.