Why is it I can never connect?
 

LW-2.9.8 and Windows XP on a 3.5Mbps Cable Line

Do other Gnutella clients connect on your system? (BearShare, Shareaza, ...)?

that solved it for me!!!new address of the connection utillity (new version is available!!)
http://delphi.mediaceta.net/utilities.php

Install probs w/ LW 2.9.8 free version
 

System: Win 2000, Comcast cable connection

I just installed Limewire 2.9.8 [free version].
Upgraded from LW v2.1.3 free version, which was having connection problems also the past few weeks.

No problem w/the install itself on v 2.9.8 .

When opening LW, the window at the top says "Limewire: Running the Gnutella Network (Disconnected/No Files Available"

But when I click on the 'CONNECTIONS' tab, I see a bunch of hosts scrolling through; eventually, the list scrolls down to nothing/no hosts.

Any ideas? Pls also feel free to repond to me at:
herbwx@comcast.net

Thanx, Herb

Saw this problem for the first time today: couldn't connect through port 6346 when another computer behind my NAT was using another gnutella client on port 6351. After I unplugged the other machine I was able to connect easily. Thought I had this fixed by mapping each machine to different ports. Any ideas on how I can run more than 1 gnutella client on my NAT?

OS 10.2.5 on Mac G3; LW 2.9.10 Pro Beta.

Did you set the FORCED_IP and PORT properly in the advanced options?

Thanks
-greg

Hi Greg

What ARE the "proper" settings? Through trial and error I was able to connect later by UNchecking FORCED_IP. I also tried turning the firewalls on and off, setting and mapping all clients to 6346 and lost track of which settings worked best. btw speeds were fantastic--peaking at 764.328 KBytes/s, and averaging 590 KB/s. Tried up and down.

This allowed me to download/upload between the computers behind the NAT, but reduced uploads to clients outside my NAT to a mere 6 in 12 hours (stats reported a less than 1 meg of HTTP Content.

If you could advise the settings to try, I'll give this another go and document it more carefully.

[edit--the forced IP is correct--the "public" one