the problem with the software isn't anything we're not doing, it's because the software is buggered. there's nothing you can do, just re-download the old version here http://www3.limewire.com/download/2.8.6/

other than that i hope Limewire is quick to realise this and solve the problem by re-relasing the updated version again. in all their haste to move everyone on to this newer version they didn't check it for bugs with the Java which we can see is the case here.

DON'T UPGRADE, wait until Limewire's fixed the problem occuring.

The problems only seem to occur on some systems. I would try the upgrade anyway. It might even work because the problems reported here might very well be caused by the users themselves.

The new version should work on the majority of computers on all plattforms ( okay maybe not on MacOS but hey, - if you are using it, it's your own fault and don't even dare to complain).

I should add that this version: http://www3.limewire.com/download/2.9.7/ works on MacOS

__________________
Morgens ess ich Cornflakes und abends ess ich Brot
Und wenn ich lang genug gelebt hab, dann sterb ich und bin tot

--Fischmob

So I'm running Win2K SP3, Limewire 1.7 (because there's fewer ads and spyware), router and firewall. I've had all of this setup for over a year and until about a few weeks ago, could connect to gnutella with no problem. So it isn't the firewall or router. I tried the telnet test and within a few seconds got the message "connection lost". My ISP is AT&T (now Comcast). Does anyone know if they're blocking gnutella or port 6346? I was going to upgrade based on the warning above, but not if I'm blocked. What's the deal with AT&T?

LimeWire 1.7 will not connect anymore since LimeWire's hostcache has been shut down and newer LimeWire versions do not even accept connections from version 1.7 anymore.

The version is irrelevant, and my question is unanswered.

I did the telnet test as specified here:

http://www.limewire.com/index.jsp/refund

"BEFORE PURCHASE, PLEASE PERFORM THIS TEST!!!

Q: I have LimeWire open but I can't seem to connect. I know I have an internet connection so what's going on?

A: Your ISP (AOL, Cablevision, etc....) might be blocking Gnutella traffic. For example, the ISP STARBAND blocks all Gnutella activity at their network. If you're on Windows, perform this test to see if you can connect to Gnutella. Non-Windows users can run this as well if they know where to find the telnet program.

1. From the Start menu, choose "Run".
2. In the resulting dialog box, type "telnet 64.61.25.171 6346". Click OK.
3. A window will pop up. If it doesn't say "GNUTELLA OK" within a few seconds, your ISP is probably blocking Gnutella traffic. In this case, there's not much we can do. Non-Windows users can run this as well if they know where to find the telnet program.

If your ISP blocks Gnutella traffic, LimeWire WILL NOT work on your computer."

This test fails on my machine. As I said, I get the message "connection lost" after several seconds. So I believe it's not just an upgrade issue, but also the likelihood that AT&T is now blocking gnutella. Can someone confirm this for me? Is anyone out there in New England using AT&T (Comcast) and successfully running a version newer than 2.5 today? If so, would you please perform the above test for me and tell me what you get?

The version IS relevant.

Will not ever work anymore because 64.61.25.171:6346 has been taken offline and

Is outdated.

Okaaaayyyy..........that's good to know. Wouldn't it be nice if they told people and updated the web site. They could lose paying customers.

What I meant before is that the version is irrelevant if I couldn't connect because of my ISP and if the test were valid as anyone would expect it to be.

64.61.25.171:6346 is NOT offline. It may not allow downloads, but I can ping it, so that machine is up.

Just installed version 2.9.11 - it works. So AT&T isn't blocking yet. Thanks!

You noticed the port number 6346? Try connecting to that port and you will notice that the server that operated on that port is offline. The ip still exists and it's still the ip of one of LimeWire's computers but the hostcache that used to be there is offline.