Limewire Screws Up Port connections, Help Please!

[Killargh]

Hello there,

Im running Limewire 4.10 on a windows xp sp2 amd athlon pc with more then enough system specs and stuff.

Basically, after opening limewire from between 30-60 minutes and downloading stuff like normal, all outgoing and incomming Network Connections go dead (Includes Internet through LAN). This leads me to think limewires screwing with it somehow. Doesnt happen when limey isnt open though. As soon as its open and is left open for that period of time, everything goes.

Never used to do it until about 3/4 days ago. Any help would be nice, the many helpful and beautiful people of the forums.

Cheers,

[Lord of the Rings]

Do you use the Resume/Find Sources function on many files? If you use it on too many files simultaneously, then on some people's systems it can use up not only LW's resources but also your computers resources. Thus your computer will stop communicating with your modem/router. After opening LW, let it settle for 10-20 mins before using. If you have many shares & many incompletes then perhaps even a little longer. This varies depending on system, etc. "If" you're going to use the Resume/Find resources function, then apply it to just 1-3 at a time. You might also want to consider reducing both downld & upload bandwidths slightly. Also, set both your uplds & downlds for auto-clear. Also, tick the option under Speed for Disable Ultrapeer Capabilities off. Unless you use iTunes, turn off iTunes sharing option.

You might also want to consider deleting your LW preferences whilst LW is closed. But make a note of all your settings because once you do this, you'll need to reset all your options. See points #2 & 3 here: Fixes for Limewire

[Killargh]

Thanks il have a look

[GaWd]

I'm here for much the same reason....except it doesn't seem to permanently mess up my connection.

I've noticed that in Event Viewer, I will get a warning from the TCPIP service:

"TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts".

After that, LW is useless and I have to start another session. To the OP: look in Control Panel-->Administrative Tools-->Event Viewer-->System Log

In it you may see a Yellow triangle with an exclamation point in it from the service 'Tcpip'. If so, see if our errors are the same.

FYI, I am also running an Athlon processor with way more than the base resources required for LW. I don't think this is related to platform, however. This happens whether LW is idle or not. Whether I'm actively searching, or whether waiting for a sluggish download.

Previously I had Windows firewall OFF, but I've now turned it ON and configured it to listen on the proper port.

Sam

[GaWd]

Lord of the:

I pulled some stack info down for you. I think I have the answer, though I don't know why LW does this on my machine. The below debug info repeats over and over and over and over:

31144 DEBUG [MessageDispatch] gnutella.QueryUnicaster.addUnicastEndpoint - QueryUnicaster.addUnicastEndpoint(): obtained lock.
31144 DEBUG [MessageDispatch] gnutella.QueryUnicaster.addUnicastEndpoint - QueryUnicaster.addUnicastEndpoint(): released lock.

Always just like that-obtain release, obtain release, obtain release. If those are separate TCP/IP connect attempts, then that is the answer to my connections problem. I don't have a solution, however.

Sam

[Lord of the Rings]

I'd need to get someone else to look at your issue. But I am aware that windows XP Service Pack 2 restricts the number of concurrent TCP connection attempts. This sounds like a classic case of this. There's a 3rd party patch to increase this number from 10 to 50 (or possibly more with some tuning.) See this link for the patch http://www.lvllord.de/?url=tools

[Killargh]

I was experimenting with different versions of limewire, and after installing and then removing an older version, it reset everything on 4.10. This seems to have solved the problem. Hasnt shut down for the last 3 hours.

Prehaps all it needs is a complete removal (registry, etc) and then re-installed.