Still no connecting...
 

Crohrs,

I tried your suggestion and still nothing. I've Dl'd 2.02 and got the dlder trojan, so that's coming off, but even that one didn't go through. Hope you all have an idea.

Hi!

Even wirth theses new adress-hosts:
router1.limewire.com
router2.limewire.com
router3.limewire.com
router4.limewire.com
router5.limewire.com
...
and the port 6346, as being told
NOTHING works.
I'm also using that old V1.3, because I need an installer sneaking around administrator rights.
But I just can't get connected.

Which other versions support install anywhere?
And why can't I use another port in case this specific one is blocked within the network I use?

Regards,
Tom

LimeWire 1.3 is nearly a year old and uses bootstrap servers that no longer exist. Please upgrade!

You can control your client's listening port, but you can't control our bootstrap server's listening port.

Still not connecting...
 

Crohrs,

I can see where he's using a year-old client, and having problems, that he shouldn't be suprised. But maybe he has something there, could a network block on the port be a problem? And if so, is there a way around it. I found a tunneling package, and was thinking of trying that, but I'm not sure it will work with P2P.

The problem isn't just LimeWire though. It's Kaazaa, Phex, Morpheus, Caracho, Gnotella, and others. With the Gnu-based clients, I can see the similarity, and if one is down, the several might be down. But maybe this is one situation to look at in future developments, opening multiple ports so that many pathways exist, even in a 'dynamic' function perhaps.

So the endless red button continues....

Deka

Yes, I think you're right. Most of the people who still can't connect are being blocked by their ISPs. The simple test is to try telnetting to router4.limewire.com, port 6346.

Also, I'm almost positive that ancient versions of LimeWire won't work since the bootstrap service has changed a few times.

Re: Still no connecting...
 

This should not be happening. Thinking of where you would have gotten the version that had the trojan I thought of <http://www3.limewire.com/download/> and it had 2.0.2 modified from last year. It would be good if the archive did not have infected releases. I also think it is important to have older versions so if 2.0.2 could be cleaned up and then reposted that would be great.

Unregistered, if you got the 2.02 from somewhere else say where you did so others will not get the trojan.

telnet router4.limewire.com 6346(macOSX)
 

hi!
masseage from japan

I have connection plob.
I telnetted to routers
I just get this:

[ocha-mobile250-234:~] pei% telnet router.limewire.com 6346
router.limewire.com: Unknown host
[ocha-mobile250-234:~] pei% telnet router4.limewire.com 6346
Trying 64.61.25.171...
telnet: Unable to connect to remote host: Connection refused
[ocha-mobile250-234:~] pei% telnet router3.limewire.com 6346
Trying 64.61.25.140...
telnet: connect to address 64.61.25.140: Connection refused
telnet: connect to address 64.61.25.139: Connection refused
telnet: Unable to connect to remote host: Connection refused
the message means my ISP(university school) is blocking port 6346. right?
but, I was able to connect the host.
and excited Limewire!
I asked my school web system manager that "cange something?" said "no"

please tell me what to do?

pei: try telnetting to router4.limewire.com port 6349. If that succeeds, your school is probably only blocking port 6346. If it fails, they're probably blocking all non-web traffic.

In the former case, you may still be able to use Gnutella, but with great difficulty since most vendors use port 6346 by default. (BearShare is a notable exception.) In the latter case, you're really stuck without the sysadmin's help. :(

LW 1.4
 

Hmmmmm, I'm also using 1.4, and I really don't want to upgrade because of the whole "bundled apps" thing. Every time I get into LW, it tries to connect to gnutellahosts.com:6346 but will not connect. It just disappears from the connections tab. Any suggestions?

crohrs
 

Thanks for your help.

v 1.8 is working with very little tweaking