Page 1 of 1
Connecting to the network...
Posted:
25 Feb 2013 02:21
by paschalleddie1
I'm running Version 2.6.0.0. and Win7. Status indicates, "Connecting to the network...", but Shareaza never connects.
Connection Test 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.
I was able to connecti the past, I'm not sure what changed. Can someone point me in the right direction?
Thanks
Re: Connecting to the network...
Posted:
27 Feb 2013 16:51
by old_death
You probably have a polluted Host Cache. You might want to check whether it is filled mostly by IPs from Taiwan and Mainland China. If this is the case, simply select all IPs and remove them from the list. Shareaza then fills the list again and a connection should be established shortly thereafter.
Re: Connecting to the network...
Posted:
27 Feb 2013 18:21
by paschalleddie1
My Host Cache is completely empty, there are no entries.
Thanks
Note: I've followed the instructions in the G2Connecting Guide -
* Querying Shareaza's GWebCaches
* Resetting Shareaza's GWebCache list
* Adding new GWebCaches for Gnutella2
* Adding new GWebCaches for Gnutella
I have 17 GWebCaches in my Discovery Service.
Re: Connecting to the network...
Posted:
01 Mar 2013 17:50
by old_death
Have you checked the results of your connection test? (Help menu)
Re: Connecting to the network...
Posted:
01 Mar 2013 20:07
by paschalleddie1
Yes, see the first message. Also see test results run today:
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.
Connection Test, as you can see, does not indicate any TCP or UDP problem. Port Forwarding or Firewall is therefor not an issue. Also note that Shareaza was working successfully before.
Re: Connecting to the network...
Posted:
02 Mar 2013 03:50
by taxiboy
Which network? G1 or G2? If G2, then try the discovery services F9 and the query any of the GWebCache entries to get them to connect. If it's the G1 network, there is a posting on copying the url of the G2 that you are connected to into your web browser then looking for a g1 connection there. fyi, it's best if you can find a connection that is using a limewire client so as to fill up the g1 host cache.
Re: Connecting to the network...
Posted:
02 Mar 2013 04:10
by old_death
Re: Connecting to the network...
Posted:
07 Mar 2013 03:03
by paschalleddie1
I've uninstalled and reinstalled Shareaza several times. I've queried all GWebCaches (G2 Network) to no avail. Cannot connect with G1 Network either.
Connection Tests still OK. Any other suggestions?
Thanks
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.
Re: Connecting to the network...
Posted:
07 Mar 2013 03:15
by paschalleddie1
I copied one of the GWebCache urls to my web browser and it loads Skulls! Multi-Network WebCache 0.2.8. The site has lists of Hosts and Alternate WebCaches. Can I use this information in any way and if so how?
Thanks
Re: Connecting to the network...
Posted:
07 Mar 2013 06:52
by old_death
In the network window there is a button labeled "connect to". You can use an IP/port combination from the website to manually connect to the IP of an other network member.
BTW, you might want to try using a port that is different from the default (port 6346), as there seem to be some ISPs which are filtering traffic from that port...