Well, now its not accepting incoming connections. Time to reboot.

i know people are.. i have been answering support email for bearshare for a few months. when the upgrade to 2.3.0 came around i was flooded by connection questions. all you had to do to fix most of them was to add some new starting host. public.bearshare.net was having problems. i dont know if it still is. also many people are being blocked on the usally port. so that also may be a problem.

Becker

Let me explain again. I don't have trouble getting hosts, they just dont stay connected. They drop constantly and horizons take a long (and I mean LONG) time to come up. When I do get a good host with a decent horizon, *poof* it times-out or leaves.

I have been using 6346 with both 2.2.7 and 2.3.0 and 2.2.7 has no problems, so it's not a port issue.

ii have found that after running bearshare for 10 mins and leting the host fill up then unchecking autoconnect the host stay long as in host. but also this only works if you are actively searching and sharing.
Becker

I accept the fact that you have problems but if I don´t have any I cannot confirm this...

Morgwen

Hi Becker!

I normally get after 2 minutes a stable connection...

and sometimes a host drops but I cannot see a problem here...

I am sure not the only one without any problems!

Morgwen

I have no problems as well. thats why its hard to help people with connection problems


Becker

Yes,

I totally agree!

Morgwen

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...

You think I am lying?

Let me repeat I have no connection problems and cannot confirm this...

On our german bearshare site there are a few people with problems but not more than the version 2.2.7 was released...

let me reapeat I cannot confirm this!

You have problems... but many people don´t have any... you read posts about connection problems, sure because the people without problems don´t post...

I don´t know what is going on... I am only a moderator on two bearshare sites and read all forums daily...
And Becker is a moderator on bearshare.net he cannot confirm this too... but we are only moderators...

So let me repeat for a last time:

There are people having problems with 2.3.0. but not more than with 2.2.7, so you can´t talk about a general problem here... I cannot confirm this!

Morgwen

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

Hi Becker!

He doesn´t have connection problems, he got his connection...

And dropping hosts are normal for the Gnet...

So I don´t no why he is talking about connection problems?

I can help the people with connection problems but if he is out of luck and his horizon is as he said about 117... what can we do, there are several possible reasons - for example local problems with the provider!

Bearshare has a problem with LANs... but we cannot talk here about a general connetion problem, this problem didn´t change since 2.2.7!

All people in Germany, without a LAN, get a connetion...
ok some have to ask but after we helped them there is no problem left...

So if he don´t get a "stable" connection, it might be local problems that should be checked...

But as I said this are no general problems with the version 2.3.0!

Morgwen

P.S.:

Thanks for helping!

I'll try to explain it so that even you two can understand it:

1) I get host with 2.3.0, they just dont stick around.

2) 2.2.7 works fine, 2.3.0 doesn't

mmmmk?

Hi!

The best is ask Vinnie I cannot help you because I don´t know there the problem is...

http://www.bearshare.net/forum/

He is the developer...

Morgwen

what is you max host # and min host #?

Becker