I've tried everything & still can't connect!!!
 

I've tried everything listed in the stickys as well as a few things from previous posts and I just can't get Limewire to run. The following are the specs on my setup:
OS: XP SP2
Firewall: None (But it says I am firewalled)
Ram: 512MB
Disk: 48GB remaining
DSL Connection
Modem & router: Modem-Westell 2200, Router- Linksys BEFSR41
Connecting from home
Running Limewire 4.16.6 and Java Version 6 Update 5
ISP: Verizon DSL
Simple test Failed
This is a new problem. I had previously been running Limewire for about 4 years. It stems from the purchase of the new router.
There is a brick wall in front of share files.
Modem is configured with UPnP enabled
I completely uninstalled Norton's antivirus, turned off the Windows firewall, and turned off the router firewall.
USA

The wierdest thing is that I can use the browser part of Limewire just fine. I have been working on this for a week solid and no good. If anyone can help me out, it would be greatly appreciated.

Homeer!
UPnP enabled may not be enough, follow the instructions from PortForward.com - Free Help Setting up Your Router or Firewall ...pick your router make and model 1st.
Did you replace the gnutella.net file? If not do it with this one gnutella.net
hope this helps
johnnie

I agree with johnnienucleo, because like you said, it stems from using a new router and it worked before. Some routers from Linksys have problems with letting Limewire through when using UPnP, that's why just trying to forward the port is a good idea.

There are firmware upgrades and hacks for most routers, but there are no guaranties that it will work, while if you get forwarded properly, your problems are gone forever... or at least to your next hardware change comes up ;)

yeah I did replace the gnutella file. I just tried the portforward and set up a static IP address but it still won't connect. I think I may just have to pay someone to do this. I'm tired of trying to make this work.

Really you should try once more to go over all the steps. It's often the simplest of things that cause the problem when portforwarding. Of course that's also the reason why they are so hard to spot.

Like the other day, I spent over two hours trying to figure out why all of a sudden I couldn't connect to my router through wireless. Turned out a new IP changing software I used I accidentally put 3 instead of 103 as the final number of my IP. Since the only IPs allowed to make changes to it were 101-104, 3 of course was blocked.