Hi,

I've been using LimeWire Pro for over a year now with no problems but since just after Christmas Day it has failed to connect.

I'm on the work LAN and nothing has changed from a network point of view.

I downloaded FrostWire to trial and it will connect no problem, so I'm kinda stumped.

Info:

Win XP Home SP2
LimeWire Pro 4.0.8 (I re-installed it)
Work LAN with ADSL
Allied Telesyn AT-AR240E router
ISP: Eircom.Net

Like I said, I've had no problems for over a year and now nothing so I'm experiencing severe withdrawal symptoms. Any help greatly appreciated.

Ta!

Try using a different port for both. If one is using port 6346, then make the other use a different port to connect thru. That may mean manual port forwarading for one of them. Try a port between (49152 - 65535) for example.

Unless you tell us the router/modem device brand & model number then I can't direct you to instructions for this if you're not sure (but that's if I can find such.)

Thanks LOTRs,

Our modem/router is an Allied Telesyn AT-AR240E.


I don't particularly want to use FrostWire; I just downloaded it to see if it could connect to Gnutella (which it could - first time).

Apart from the failure to connect, my LimeWire is acting a bit weird: when I click on connect nothing happens in the Connections tab for about 60 seconds then it tries to connect to around 10 hosts which drop off one by one and then nothing again.

It stays like this till a window with "LimeWire is unable to connect to hosts on the Gnutella Network" etc continually pops-up and I have to access my Task Manager to force LimeWire to quit.

Like I say, nothing has changed from a network/firewall point of view at work and the only things to change on my PC are the Microsoft Updates.

To be honest, I'm ready to re-program the f*cker with a hammer.

Ta for the help.

Try deleting the LW preferences folder whilst LW is "closed". If you used a previousl LW version then find instructions here Point #2 in Fixes for Limewire (sample at bottom of page.)

For LW 4.10 preferences, it's a little more complicated. You'll need to follow the FrostWire instructions but use the word limewire instead of Frostwire or .limewire. (The prefs folder for the new LW are called limewire not .limewire!) so remember to show hidden files & folders "before" you use the search. How to delete your FrostWire Preferences folder

You should probably search for both .limewire & limewire & delete both lots of preferences. See if doing this helps. Oh & don't forget to make a note of where your downld folder is & other settings, b/c once you delete the prefs folder, you'll need to reset all the options next time you open LW.

Just tried that - didn't work (although at least now it's trying to connect ).

I was thinking of downloading LimeWire 4.10 basic to see if this'll work. Will it conflict with my LimeWire Pro?

Thanks for the help LOTRs.

Yes it might, you may have 2 limewires running simultaneously which in itself will cause problems. But you have your personal pro downld page bookmarked right? Installing LW again will actually most likely uninstall the other version at the beginning of the installation.

Erm, no.

But I do have the original .exe install file. I was going to un-install Pro and install basic 4.10 to try it out.

What do you think?

Yep go ahead. See how it goes. To uninstall you do it from the Start menu > Programs>LW>Uninstaller.

I would tend to recommend the "Offline" installer version though. But that's up to you.

Right, un-installed LimeWire Pro and downloaded the off-line 4.10.2 Basic installer.

Tried to install it 3 times now and I keep getting this:

"The installation is corrupted. Please download and and install LimeWire again"

Tried the on-line version too - same result.

Time to throw in the towel??

Ok, I disabled my Panda anti-virus and 4.10.2 installed no problem.

(Although Panda was blocking what it called "Spyware" from being loaded. Hmmmmm)

Anyway, I can get a connection now though it takes ages, it's not great and it keeps dropping.

Do you think if I upgrade to Pro again it could sort out the weak connection?