Here's the likely problem:
Under XP SP2, the number of unresolved outbound connections is limited. If you exceed the limit, outgoing packets/connections are stacked internally until the outbound connections are within tollerance, and then queued connections are resolved in order.
XP SP2 is mostly security upgrades, and this code has been implemented to prevent a computer from spamming the internet, particularly viruses that use wardial like code to search for vulnerable systems, by opening many connections at a time.
For more information, see this link:http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx#XSLTsection127121120120
Note, it is NOT likely MUSHclient with all the open connections, but some other software you are running, like a P2P program, that is hogging all the outbound connections, and thus causing MUSHclient to suffer as it's own connection(s) get delayed in the queue.
Ah heck, here's the relevent text, quoted from the page I gave URL for:
Limited number of simultaneous incomplete outbound TCP connection attempts
Detailed description
The TCP/IP stack now limits the number of simultaneous incomplete outbound TCP connection attempts. After the limit has been reached, subsequent connection attempts are put in a queue and will be resolved at a fixed rate. Under normal operation, when applications are connecting to available hosts at valid IP addresses, no connection rate-limiting will occur. When it does occur, a new event, with ID 4226, appears in the system’s event log.
Why is this change important? What threats does it help mitigate?
This change helps to limit the speed at which malicious programs, such as viruses and worms, spread to uninfected computers. Malicious programs often attempt to reach uninfected computers by opening simultaneous connections to random IP addresses. Most of these random addresses result in a failed connection, so a burst of such activity on a computer is a signal that it may have been infected by a malicious program.
What works differently?
This change may cause certain security tools, such as port scanners, to run more slowly.
How do I resolve these issues?
Stop the application that is responsible for the failing connection attempts.
|