Shareaza won't connect

[bu14-1]

Hi all,

Recently I changed (or tried to change) the port Shareaza uses. Until then it was working fine. I opened up the ports in my router and gateway server and set up port forwarding and the connection test reports that it is working but Shareaza won't connect (I perpetually get the message "connecting to network" down the botom. I have tried reinstalling (using the latest version) and disabling the firewalls and exiting out of other software that may be using up the bandwidth but nothing seems to work. Any ideas?

Thanks.

[ailurophobe]

Can you check if ED2K connects and this is limited to the Gnutella networks? If ED2K connects fine install the latest daily since that seems to fix Gnutella specific connection problems for reasons unknown.

[profyler1]

im having a similliar problem.
im using the latest debug build.

CAnt connect to g2. Actaually it conect to g2 only like 3 hours after i run shareaza. g1 also too slow to conect to peers.... but i dont have problems with edk neither dc++. can someone tell me why is this happening?

firewall and router are ok.

[profyler1]

prints. (sorry, portuguese , but i think u can understand it...)

[bu14-1]

Can't connect to eDonkey either.

Any ideas?

Thanks.

[bu14-1]

Tried a different port and it's working now. Port that didn't work was 30535 I think.

EDIT: Very strange. It only works if port 6346 (default Shareaza port) is open on my router. It is not open on any of my other firewalls and is not set up with port forwarding. Anyway, it's now connecting.

EDIT 2: To clarify, Shareaza is set to use a different port (different to 6346) but will only connect if port 6346 is open on my Billion VNOX router even though it is not open on my gateway server or the workstation.

[profyler1]

i had a lot os improovement after i patched the Windows XP with that patch about the conections (TCP/IP)
although i still have to use the latest dev. build because of the problem with the future host of G2.
i hope they release the next shareaza version soon with that problem fixed.