Hostcaches

S

SKEET

New member
Recently all five of the default hostcaches I use with Qtella (connect(1-4).gnutellanet.com:6346, gnutella.hostscache.com:6346) seem to have stopped working or something. Does anyone have any reason why? I looked this up in the client-specific forums, and the suggestion was to use the connect(1-4).gnutellanet.com:6346 caches, but they don't work either apparently. Does anyone know what happened to them all? Is it just a problem on my side or are they in fact all screwy? Fortunately I am a member of the Gnutella Developers Forum and there there is a big list of other hostcaches, but I still want to know what happened to these. What I will probably do in the meantime is go to gnufrog.com and enter addresses manually, but that clearly is sucky compared to automatic hostcaches.
 
I've been using all of the host caches you mentioned and router.limwire.com:6346 as well. All of them have been effective in establishing a connection. Strangely enough, I've also discovered that connect.newtella.net is still functioning. I would have though that it been abandoned since the associated client Newtella is no longer actively being updated.
Have you considered that the problem might lie with your ISP, or more likely those damn firewalls that so many people feel are necessasry. I shut mine off whenever I use the Gnet; I'm just fearless or stupid I suppose.
 
Well, I suppose it could be with my ISP, but since a lot of people were reporting the same problem I concluded that the problem was probably more general. Although if the problem is in fact with my ISP I will cancel my subscription on the dot. I don't have any firewalls going, so it can't be that. What I did was go to the Gnutella Developers Forum and copy and paste every single known hostcache into the program, and some of the other ones indeed work. Even if the problem does lie with my ISP then they must only be messing with a few servers. How could I find out, send them an email and ask them 'are you blocking any Gnutella hostcaches'? Well, I guess I'll continue connecting as best I can in the meantime.
 
Youre ISP could conceivably block port 6346, the predominant port used by the Gnutella network, but no ISP could selectively block particular programs on an individual computer. Most likely, all of the clients will work given enough time for them to connect and establish a stable environment. Be patience, some of these clients and hostcaches require more time than others.
 
Well, I know the ISP didn't just go and block that port because it is still possible to connect to other servents and even other hostcaches using port 6346, it's just those hostcaches that I mentioned that don't want to work. In fact, gnutella.hostscache.com:6346 use to work almost immediately. Now none of those that I mentioned work at all. You can tell the thing to connect, leave, and come back in a while, but there will still be no connection. Tonight I have gotten connect3.gnutellanet.com:6346 to work, so in light of all this the problem has to lie with the hostcaches.
 
It was enlightening to see your post. I have not been able to connect to gnotella using those hosts, as well. Unfortunately, I am not a member of any forum and I don't know how to connect back in. I would appreciate any information you can share so I can get back in.

Thanks
 
Can you list some of these Hostcaches for us starving leeches that don't have developer forum access. Thanks in advance.

> Fortunately I am a member of the Gnutella Developers Forum and there there is a big list of other hostcaches
 
technically you don't need to be developer to join the developer's forum... you can go here...

http://groups.yahoo.com/group/the_gdf

and then sign up....
 
Yeah, you don't need to be a Gnutella developer to join. I'm not yet (soon though) and I'm in it. But here is the entire list of hostcaches that I have my program use when I tell it to connect:

connect1.gnutellanet.com:6346
connect2.gnutellanet.com:6346
connect3.gnutellanet.com:6346
connect4.gnutellanet.com:6346
gnutella.hostscache.com:6346
router.limewire.com:6346
connect.cultiv8r.com:6346
xcache.cultiv8r.com:6346
connect3.bearshare.net:6346
gnet2.ath.cx:6346
204.83.201.2:6346
209.190.205.236:6346

You'll probably get something there to connect, it always works for me. There are other hostcaches out there, but I don't have a list of them.
 
That's good to know, I'd never seen that anywhere. I just assumed they were four hostcaches run by the same people, whoever the people are (or would be).
 
Back
Top