Shareaza

Prior to upgrading to Shareaza 2.6.0.0, I had no trouble connecting to Gnutella1 with ver 2.5.5.0. After installing ver 2.6.0.0, I had problems with it, so I uninstalled it and did a clean install of version 2.5.5.0. Now Gnutella1 will not connect. Gnutella1 shows in the Connections box, but disconnected. When clicking network, it shows that Gnutella1 is included and Gnutella1 is checked in the QuickStart dialog.

How can I get Shareaza to connect to Gnutella!? I checked and searched the forums but did not find this problem listed, so any help would be appreciated.

Would you mind checking the connection test results and posting them here?

The easiest suspect (easiest to fix) would be that something went wrong with the "clean install", and the reason you should check it first is because that would be fixed by simply installing 2.6.

i am having a similar problem - first only gnutella2 & edonkey would connect, now only edonkey will connect. i get no search results and the current files aren't downloading. i have uninstalled and reinstalled several times, completing deleting all program files. my connection test says it's fine. i would love some help on this issue.

many people have been having this problem. It could be a bug, or just the degradation of the gnutella network, but regardless there is a work-around Here. If you don't use shareaza for a few days you might have to do this again, so you'll probably want to keep it minimized in the system tray

@cherrybomb666: you should be able to reconnect to G2 by querying some discovery services

Old Death...you asked me to post the results of my connection test...see below...Jason

Results
TCP: The TCP connection has been accepted by your computer and the request has been answered. This means that other clients from the networks can properly connect to you.
UDP: An answer has been received from your client! This means that Shareaza is able to receive UDP packets from the network.
Congratulations, everything seems to be fine and Shareaza should work properly.

OK, this sounds promising at least. Would you mind telling me whet happens if you do a fresh install of the latest version and do chose the option to reset discovery and host cache within the installer?

Old Death...

You asked:
OK, this sounds promising at least. Would you mind telling me whet happens if you do a fresh install of the latest version and do chose the option to reset discovery and host cache within the installer?

I downloaded ver 2.6.0.0 and installed it. I did choose the option to reset discovery & host casche, but Shareaza still will not connect to Gnutella1. It appears in the connection box, but shows disconnected.

Any other suggestions?

Yes, you could try out the work-around that Cyko posted.

See if this helps: https://sourceforge.net/apps/phpbb/shareaza/viewtopic.php?f=3&t=1379&sid=4918062b97a5b8fdc83b9770cef71a36#p8930

Well after a few days of not using shareaza everything but G1 servers was logging in. What was said in this post works but I will fill in what was left out. First off you need to clear your G1 Cache View -> advanced -> Host Cache from here at the bottom click G1 Cache and click on 1 of them. Then press CTRL + A to select them all and then perss the Delete key. After this press the F9 key and in discovery select all of the G1 servers listed by clicking on 1 of them then holding down the CTRL key and click the next one and so on. When they are all selected just press the delete key again. After this they will auto refill and just select one and query one and be fore you know it bingo your connected once again. Btw ya dude was right. not using shareaza for a few days you will have to repeat this.

Note that it is possible to increase the time between two repeats by increasing the amount of time hosts remain within the Host Cache within the Advanced Settings.

I solved all my connection problems to both G1 and G2 by doing the following: switch to power mode (if not already using) and then go to settings- advanced- and select discovery- then look for "Enable G1GWC" in list- it may read "false" by mistake. If it does you need to change it to "true" (by ticking box marked "value") and it should hopefully resolve this problem, as it did for me. Advice was posted on another discussion but I forget where. I've had no problems since following these steps.