![]() |
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 |
Look under statistik - horizon shared... How many hosts do you have? Which connection? After 8 minutes I have at least 1000 with six hosts... Morgwen |
117 after 16 minutes |
they dropped and now I'm down to 2 hosts with a total of 48 for horizons |
Hmm, I cannot confirm this! But if you donīt like bearshare... Try Xolox or Morpheus! Morgwen |
You can't confirm this? So I might be lying? Why don't you accept the fact that some of us are having trouble connecting with Bearshare?! |
Well, now its not accepting incoming connections. Time to reboot. |
yah Quote:
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 |
Quote:
Morgwen |
Quote:
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 :confused: |
nope.. Quote:
Becker |
Re: nope.. Quote:
I totally agree! Morgwen |
I see a lot of people going back to 2.2.7 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... |
Re: I see a lot of people going back to 2.2.7 Quote:
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... :rolleyes: 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 |
Re: I see a lot of people going back to 2.2.7 Quote:
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? :confused: 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! :) |
like talking to a hole in the wall 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 |
Re: like talking to a hole in the wall Quote:
Becker |
I know you are trying to help, and I appreciate it. I usually set my minimum to 2 or 3 and my max to about 7. I'm not a newbie, give me some credit :-) I get connections, they just don't stay. They time-out, cancel or leave. I can't keep a good connection going for very a long. |
did you.. Did you try connecting for a bit then unchecking auto connect but leaving accpect checked? you must share and search though.. Becker |
Thanks, but I'm sick of messing with it. I'm using Limewire now :-( |
Hi! You can choose which client you want but have you heared something about Gator, EZula or Web 3000? If not... choose one of the other clients! Morgwen |
I'm sure he is fully aware of the programmes you describe Morgwen,after all he is a long time user of previous Bearshare versions and is probably fully versed on such items. In his defence I am also suffering the same symptoms he is describing,previous versions were fine,not now,its a shame cos I'm a keen user of Bearshare,but these stability problems are holding me back somewhat. |
Yes Batfink you are right but... bearshare is fully operational after deinstalling the tools Limewire not! Its a difference but I donīt want to defend bearshare here! Morgwen |
We are all having problems connecting it seems like. |
All times are GMT -7. The time now is 02:26 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright Đ 2020 Gnutella Forums.
All Rights Reserved.