nitram_cero Posted October 28, 2008 Report Share Posted October 28, 2008 If you are using uTorrent (or any highly intensive port using program) and Avast and weird things happens, maybe this can help you:I noticed that Avast does packet analisys by "sandwitching" ports. I'll explain:Aparently Avast hooks any program conections to itself (using 2 ports: for connect and listen) and a third one "pops from a system process 0" to the real destination.When this happens to uTorrent (which has a lot of connections) it hogs the system and USES UP ALL AVAILABLE PORTS!Almost none of the programs are verbose enough to tell you this. I ran into this answer by mere luck, as the aMSN (3rd party MSN client) wasn't able to login to my account because there were no ports left, getting the error message directly from the WinSock API.Something I noticed (using "cport" tool) was that a lot of connections were in the FIN_WAIT_2 state. That mean's they are waiting for the "other side" approval to finally kill it, or for timeout.I have "P2P Shield" off, but I think this comes from the "Web Shield" module.Regards-Martín Link to comment Share on other sites More sharing options...
DreadWingKnight Posted October 28, 2008 Report Share Posted October 28, 2008 Then set uT as an exception in the web shield module. Link to comment Share on other sites More sharing options...
nitram_cero Posted October 28, 2008 Author Report Share Posted October 28, 2008 Exceptions for "Web Shield" only work for MIME types and URLs.I'm posting in the Avast! support forum, I'll post here again if I get an answer/solution.In case someone is interested (a.k.a. if I forget to reply here):http://forum.avast.com/index.php?topic=39657.msg332611 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.