Quote:
Originally posted by Unregistered The numbers don't lie.
2.2.7 is on the rise again because PEOPLE ARE HAVING TROUBLE STAYING CONNECTED WITH 2.3.0
But of course, you cannot confirm this... |
Go to Setup > Service
Then add some of these host.
public.bearshare.net
connect1.bearshare.net
connect2.bearshare.net
connect3.bearshare.net
connect1.gnutellanet.come:6346
connect2.gnutellanet.come:6346
connect3.gnutellanet.come:6346
Also keep your Max host number on the Host tab around 5.
IF YOU ALLREADY DID THIS :
Here is the information to understand about connecting to the gnutella network with bearshare:
When you launch the program it tries to connect to hosts. Go to the
hosts tab to observe this.
Make sure that Automatic is checked.
Which hosts will it try to connect to automatically? The ones that you
have put into the Automatic Connections in Setup -> Services. This
should at least have public.bearshare.net. So go to Setup -> Services
and check.
Ok, so let's assume that you have public.bearshare.net in automatic
connections, and you see that it is trying to connect to this host.
Still not connecting?
Let's check your internet connectivity using another web site.
Go to a DOS prompt. Type "ping
www.cisco.com" and see what happens.
If it say "timed out" then the ping is failing, which means internet
connectivity problems or a firewall is blocking your access to the
internet.
If it say "unknown host" then you have problems with DNS (or internet
connectivity). Check your dns settings.
If the ping is successful, then try to ping public.bearshare.net. The
same logic will apply.
If the ping is successful, but you still can't connect then find out if
a firewall is blocking TCP port 6346. A firewall could be running on
your PC itself, or on a corporate network which is providing you access
to the internet. The firewall must permit TCP port 6346.
Becker