2.3.0 DOES have connection problems
 

Many people have posted (on various forums) and hundreds have read about connection problems with 2.3.0

I found that I had to delete the contents of my Bearshare folder
(excluding the TEMP and DOWNLOAD folder) before reinstalling 2.3.0. It helped me bit, though connections are still sporadic and horizons are still poor. I have often had horizons stuck on 1 for long periods of time before the connection is lost. Other connections are cancelled immediately for no apparent reason (no, they weren't duplicates.)

I won't pretend to know what's going on, but I assure you I had much better luck connecting with 2.2.7

Is the developer of Bearshare trying to mold gnutella? Why do I end up with all Bearshare clients for host connections? I think its a compatibility issue between the clients, but I don't really know. Is what we are seeing the result of a client war? Please, if you know whats going on, tell us.

Re: 2.3.0 DOES have connection problems
 

Is the developer of Bearshare trying to mold gnutella? Why do I end up with all Bearshare clients for host connections? I think its a compatibility issue between the clients, but I don't really know. Is what we are seeing the result of a client war? Please, if you know whats going on, tell us.

this thread may answer you're "all bearshare clients" question:

http://bearshare.net/forum/showthrea...&threadid=5608

or maybe it will cause more questions...sorry.

No!

2.3.0 has no connections problems!

If you use the hostcatcher public.bearshare.net, its normal that you only find bearshare hosts because this is a bearshare hostcatcher... add for example router.limewire.com or others (under setup/service!).

But if you use only the bearshare standard catcher, bearshare is still fully operational - you can download/upload from all other clients...

As for the horizon about 3000 (with six hosts!) is normal!

I never had any connections problems with 2.3.0!

Morgwen

I'm not trying to argue. I have huge success with bearshare. however, i have removed all bearshare host caches and still ended up with only other bearshare 2.3.0 hosts staying connected. (using gnutella and limewire caches). I just wonder if 2.30 somehow seeks out other bearshare hosts firsts when connecting?
It doesn't really matter to me. I manage to stay connected to hosts for hours (and this is on win 98) and get thousands of results for most of my searches...peace!

Funny...
 

As an experiment I removed the default bearshare cache and entered the limewire one you mentioned. Been over 10 minutes and it still hasn't connected. Its wonderful how the clients work together.

Hi!

you have a connection?

you find your files?

and you can download and upload from all gnet clients!

where is the problem?

Morgwen

Finally
 

Bearshare finally connected to router.limewire.com and I STILL have nothing but Bearshare hosts. Horizons are a joke!

Horizons are a joke!

3000 is a joke...

sorry but you have to wait a few minutes...

Morgwen

slow
 

6 minutes and my highest horizon is 35. The others are less than 11.

nope, they dropped
 

8 minutes highest is 14