The current LW for Mac suddenly stopped working: it won't connect and icon on bottom indicates a firewall I assume. Firewall isn't on for this Mac Pro running OS 10.5.4. I have a D-Link router connecting several Macs to comcast at home. Enable UPnP is on and I haven't changed anything lately. Using the D-Link virtual server, I opened port 38313 for the mac trying to run LW.
Curiously, Safari freezes when LW is trying to connect to the web.
I doubt comcast is blocking LW so rather confused by this new problem.
I reinstalled LW with fresh download of current version but no improvement.
thanks

This may be a comcast issue since same problem with a G4 Mac running OS10.4 with current LW. I'm waiting to hear back from Comcast. Location: Maryland.

well, I figured it out. The router has a bunch of computers linked by ethernet cables but I added an Apple Airport Express Base Station for access by portable Mac. The DHCP is turned off in the base station and so is the firewall, plus the Macs that failed to connect were connected to the router by ethernet cables. Since I wasn't going through the base station, I assumed that it wouldn't be an issue. If I turn off the airport, then LW works. This wasted a lot of time figuring out so perhaps this will be of use to someone else?

Help, I used to be able to connect to LW with no problem, the other day my computer gave an error. Which I turned off and turned back on, I have Window XP. Anyways, I opened LW, now since then I have only 1 little red bar on the bottom, it won't connect now for some reason. Can someone please help me as to what may be the problem????? Thanks.

Well, I spoke too soon. Limewire connected once with the airport disconnected but then problem recurred even without airport. There is clearly some kind of conflict since web browsers (safari and firetox) won't access the web when LW is open. Saw this on both macs mentioned above. Messing with settings and resetting router didn't help. Comcast is not blocking LW. This problem occurred after updating to current version of LW for Mac.

kelliegirl: sorry but I have a mac so not much help in this thread.

alf--FWIW, giving each machine at home a static local IP solved most of my networking problems. You have DHCP turned off, so I'm guessing you gave each machine a static IP, like 192.168.1.2, 3, 4, etc. right?

If so, then each machine needs to be mapped to a port in the router's port forwarding section, and the LW prefs need to be set to manual with the appropriate port.

Oh--too many incomplete files trying to connect on startup can also trigger a lockup at times.

Each LW will need to be forwarded to a different port. Routers reserve a single port per program per computer. And will disallow connection from other programs or same program on another computer trying to use the same port. Thus, each of your LW's will need a different connection & listening port. Ranges of other ports to try 49152 - 65535.
And don't forget to set each LW to those ports you allowed for those computers: Manual port forward instructions & sample image

stoef: thanks for the reply but my EBR-2310 DLink router (v.2 probably) is serving via DHCP, and has given all the mac an ip address. I have a wireless Apple airport extreme modem that has the firewall and the like turned off since it's only acting as a bridge; if I turn off the wireless modem problem persists. This happens on a Mac Pro running 10.5 and a G4 running 10.4 of Mac OS. This is all recent and not sure why it suddenly started?I have UPnP enabled. At first I thought it was the airport but maybe just a new version of LW?

Lord of the Rings: thanks for the suggestion but I went to your web page and the settings were blank for setting up the router for port forwarding - Port Forwarding for the Dlink EBR-2310v2
I never had to do this before so not sure why it suddenly appeared.

I have the listening port in LW set for 16762, and set that in port forwarding and virtual server with the ip of the mac running LW. I never had to do any of this before.

When I try to do a search, LW doesn't appear to be connected and I get the message that "Limewire is currently connecting to the network....."

Also, web browsers lose connection to internet when I open LW.

Well this has gone from irritating to just weird. In desperation, I turned off the ethernet router and my Mac, and then swapped out the new AirPort Express Base Station with my old D-Link DWL-900AP+ wireless modem. I then turned on the router and Mac. LW now connects and the firewall icon in LW has disappeard. When I put the AirPort Express Base Station back on, the firewall icon reappears. Rather strange since Mac is not using wireless. It's not clear how to turn off the firewall on the AirPort Express Base Station.

Yeah, troubleshooting internal networks can be a real pain, and will likely continue. With so many devices each trying to make routes to the internet, there are bound to be collisions. I've not used and Airport (or 10.5), so look to google or the Airport Help for making the airport only work as a switch.

The principle to get around all the UPnP or other such protocols is to manually set a unique route from each LW to the internet. This means manually setting the Ip in the OSx Network prefs, setting the Port in LW, and finally using that info to set the router's port forwarding prefs. Quite a pain.

btw, the link LOTR send you will show blank settings until you fill in the box that says "Do not skip this step"

Also, if the browser connections die, that may mean too many incompletes are trying to connect.