DL probs after router config
 

I recently completely reinstalled my system from scratch (wiped the hard drive, reinstalled Windows XP, installed all the upgrades to XP (SP2, etc.), reinstalled LimeWire Pro 4.2.6, etc), and then tried some new router configurations in an attempt to make StarCraft and other games work better on my shared network connection.

Basically, I upgraded the firmware on my wireless router (LinkSys BEFW-11S4 V4), and then set it up to give all four computers on the network static IP addresses. Then I set up port forwarding for StarCraft, which works MUCH better now.

Unfortunately, it's hosed my LimeWire connection. I can find all kinds of files, but when I try to download them, it just lists them as being "Queued." That status never changes, and the file never downloads. When the XP firewall popped up and asked if I wanted to allow LimeWire, I of course clicked "Yes/Allow" or whateve it said. LimeWire still didn't work, so I tried specifically allowing port 6346 in the firewall exceptions. No luck.

I could specifically forward port 6346 to one of the computers on my system, but (I think) that would mean that ONLY that computer would be able to use LimeWire.

A couple other setup details:
Cox Communications is my service provider. They suck rocks, but I don't think they're the problem, since I didn't have this problem before I messed with the router.
I use a Toshiba cable modem, which is connected directly to the router. One computer is directly wired (ethernet) to the router, the other three are all wireless.
I still have occasional problems (probably unrelated?) with the router, such that all computers on the network lose their network connection, and the only thing that fixes the problem is to unplug the router and plug it back in. I have no idea why this works.

Any help you can provide would be greatly appreciated. Thanks!

-- David:confused:

Did you allow both TCP and UDP access, when you configured for port 6346. They have to be set individually. It sounds like you have configured for TCP but not UDP.

Nope, I allowed them both individually.

Yes that's right. You can only use one port forward per computer. So for your others you'd need to set a diferent number for a separate port forwarding. eg: Comp 1= port 6346, comp 2= 6344, comp 3 = 6348, etc.
Ummm ... this doesn't apply to everyone but apparently just selected customers they filter their speeds for p2p use. See: http://www.gnutellaforums.com/showth...threadid=33712 I hope this does NOT apply to you. It only seems to apply to some people. But it not only applies to LW for some people as other p2p forums have proven.

I see a way to do that in LimeWire as far as what ports to LISTEN on, but I don't see a way to specify outgoing ports. Since my problems are with downloading (and probably uploading, too, but that's a secondary concern that I haven't addressed yet), how would changing the listening ports help that?

If you could post some specific instructions on how to configure limewire to use specific ports that you think might solve this problem, I'd appreciate it. I know how to do the port forwarding configuration in the router, I just need to know how to tell each LimeWire client to use a different port.

Thanks,

-- David

Sure. Instruction for your model are here: http://www.portforward.com/routers.htm & look to 3rd row from left & vey near top & you'll find your model.

1st. Set up a static ip. 2. Forward a port. 3. Force ip within LW.

For computer 1. that can be done for port 6346. For computer 2 that can be done for port 6344 or example. Yes you can have separate port forwards. So different port setttings for each computer.

Direct Linksys instructions here: http://linksys.custhelp.com/cgi-bin/...type=search_nl & http://linksys.custhelp.com/cgi-bin/...p.php&p_tbl=13

Interventions not working
 

Okay, I set up port forwarding in the router to send limewire packets coming in on 6346 to automatically go to my desktop PC. (Doing this as an experiment, I didn't bother to set up any other computers on other ports.)

LimeWire is set to force the IP, using port 6346. The Windows XP firewall is set to accept connections on port 6346 for both TCP and UDP. The program LimeWire is set to "enable" (allowed) under the "exceptions" tab of the XP firewall.

Still... No... Luck...

Everything I try to download just goes straight to "Queued," and never tries to connect beyond that.

One thing I noticed is that UPnP is not configured at the moment, either in the router or in the firewall. Is this necessary? I've never messed with that before.

I do see a few incoming searches coming into my computer, though when I click on "Show incoming searches," I get a popup message/dialog box that tells me that I won't see many incoming searches, because I'm "shielded by an Ultrapeer" or something like that.

I've really reached the end of my technical ability, here. :-/ Any advice would be appreciated.

-- David

NEW INFO: 2/23: I tried booting up LimeWire on my Mac, and it works perfectly!! Tell me how this makes sense: the router is now set to forward port 6346 to my desktop PC, which is 192.168.1.203. Despite the static IP and port forwarding, and everything I can do to force the IP and allow exceptions in the firewall, there seems to be NO WAY to make my PC run limewire properly. My mac laptop, on the other hand, is set to static ip 192.168.1.202, and is using the default port 6346. Mind you, the router is NOT set to forward port 6346 to this IP address, it is set to forward it to my desktop PC. Yet, I'm downloading from LimeWire right now on my Mac with great download speeds, and my PC just sits there saying "Queued." Does anybody have ANY idea what's going on here???

More new info: In Windows Firewall, the firewall is enabled on "Network Bridge" and "Wireless Network Connection 2." Under these two settings, nothing is checked in either the "Services" or "ICMP" tabs. Is there something there that I need to check? Under "Exceptions" in the Windows Firewall, UPnP is not checked. Does it need to be?

Second though (or third or fourth or...): I turned the firewall OFF, and it still doesn't work. So, it would appear that the firewall is not the problem. NOW does anybody have any ideas?

I can't answer all your questions b/c I'm not a windows user per se. If your modem/router does have UPnP capability then that's good. Enable it & in firewall setting on LW & that should fix that side of things & I don't believe port Forw. is then necessary. UPnP is new in LW 4.4 & that's as much as I know about it. It should be able to communicate with your device directly then. For games though that'd be different.

I wonder if your issue is different for your pc. Try getting rid of all those older incompletes that are at 0% in both your incomplete folder & downld window. This will help to speed up LW opening & settling down.

Keep in mind all files are going to be queued as soon as you open LW. Give it some time before working with it. Even allow them all try to connect as they will one by one.

Even if you are firewalled there may be some people able to upload from you. But the majority will be blocked out. Of course the ways to check are 1. After LW's been open for more than 30 mins do this test: Bug Report instructions & sample image Is it True/False? If false then there is a firewall there somewhere. 2. Check your statistics: Tools>Stats 3. Library window to far right of shared files will list those that have found your files under 'hits' & those that have successfully or unsuccessfully been able to upload from you further to the right of that.

As for more suggestions, perhaps another member might be able to suggest something.
(Deleting your LW preferences folder sometimes seems to do some magic here; instructions here: Fixes for Limewire)

Hmmm here is thought I have a network adapter that I had to configure also for my ethernet card to work properly.

I'm not sure if your comp. has one also or not. You can find out by going to control panel>systems>hardware>device manager> network adapters.

My network adapter and ethernet card are both listed there.

Just a thought that might help.