Using Mac OS X 10.1.4. Previous version of LimeWire worked just fine. Upgraded to new version and it stopped connecting at all. Two of my co workers have same problem now.

1) try telnetting to router4.limewire.com port 6346 - if you don't see a "gnutella ok", your access to gnutella has been blocked. It's entirely possible you never noticed before, because you usually don't need to connect to router4.limewire.com to connect to gnutella.

2) If 1) works, you might want to try connecting to router4.limewire.com manually.

3) If 1) doesn't work, try my gnutella.net file from ftp://whitedragon.dyndns.org ( if the host isn't available send an email to gregorio@gmx.li ).

Ok did I do this right and what was the out come? In case you cant tell I have never used telnet

I did both a ssh and a telnet.

The correct command for telnet is:
> telnet router4.limewire.com 6346

If you don't know how to use a command-line application read the help either by adding the parameters "-h" or "--help" to the command or by entering "man [command]"(*N*X, OSX), "info [command]" (*N*X, OSX) or "help [command]" (DOS, WI***)


You can't use ssh (why did you try it anyway if you don't know what it is???)

the "xxxxx%" is actually my user name which automatically comes up in the Mac OS X terminal which does both telnet and ssh.

I did ssh because I had read that the "terminal" does both and that most everyone was moving to ssh. Not being sure I tried it knowing that nothing would blow up if I did.

So any way I typed in the same command you posted and that is what I got. I am assuming that is not what you were expecting.

Oh by the way - thanks for the help.

I tried it again with a different result this time...


[localhost:~] xxxxx% telnet router4.limewire.com 6346
Trying 64.61.25.171...
telnet: Unable to connect to remote host: Connection refused

You need a gnutella.net file to connect:

ftp://whitedragon.dyndns.org/gnutella.net

copy it into your LimeWire folder (I don't know which folder that is on Macs, but it's the one containing your LimeWire.jar file) and start LimeWire. - If you are using LimeWire regularly, you only have to get a gnutella.net file once, since LimeWire will update it, when finding new ultrapeers to connect to.

There was already such a file located where you said it should be however I replaced it with the one from your site. LimeWire connections now trys to connect and a list of IP addresses pops up, then they go away and is replaced with a new list of IP's. This happens over and over but it never establishes a connection to any of them.

I should have stuck with what I had (v.2.3.4), but I was stupidly tempted by the all-singing all-dancing v.2.4.4 and installed it this p.m.

Since then no connections...

Taliban, I've followed all your advice to the letter and absolutely nothing happens after Limewire loads. I've a sneaking suspicion that this is related to the bundled spyware. I binned/blocked it with Ad-aware/ZoneAlarm as I did with previous versions of Limewire.

I remember though that v.2.4.4 connected the first time, only after I let JAVAWS.EXE online. I know that's spyware and I have since blocked its access ... and since have had no connection.

Coincidence???