I can't get Shareaza to work.
 

I'm not sure if I have to download some patches or connection files to use it, but I can't get Shareaza to connect to any of the 3 networks! :< Any help would be appreciated. By the way, I'm downloading it right from the site.

I am not a Shareaza user but when it comes to connection problems, it is generally a firewalling problem. Things to check:
1. Make sure Shareaza has an exception in your firewall.
2. (i) Your situation may require port forwarding. Find the port(s) Shareaza is using and set up port forward rules. The alternative is to instead set up Port Triggers which is the same thing except less demanding on the setup process. The very first step for port forwarding should always be to set up a Static address on your local LAN network https://portforward.com/networking/staticip.htm (only needs to be done once though.) Note: I would recommend using a relatively high internal address number.
(ii) Log-in to your router and set up port forwarding. Find your brand and then model of router https://portforward.com/router.htm You will need to port forward both TCP and UDP for the same ports. You can either set up separate rules for each or there's usually the option to choose 'both' UDP and TCP. Use the port Shareaza is using. Alternatively you can set up a custom port but remember to also change the port(s) Shareaza is using. What custom ports you can use, see http://www.gnutellaforums.com/tips-t...formation.html though you can choose most ports above 10000 but below 65535.

Shareaza has web cache support so it should still be able to find hosts for each of the networks. In theory the program should only need to find a single active host to be able to connect. That host will pass on bonus hosts for Shareaza to try to connect to.

Things to consider about LAN address to choose for setting up static internal LAN address
 

Hope you don't mind me adding an addendum to my answer. I wish to make a point that you or other persons should take into consideration.

Regardless of using UPnP, Port Forwarding or Port Triggering, all of these can occasionally take longer than usual to kick into action and start working. I am not sure the reason.

One comment I’d like to make about setting up a static address on your local LAN:
For a user on a home network, the router generally reserves the .1 address for the modem-router. The modem-router LAN address will depend on the specific brand and model of modem-router. Examples: 10.1.1.1, 192.168.1.1
That leaves the remainder of .2 through to .255 to use within the sub-net mask.

An issue I experienced was after being away for a month my partner’s iPad had taken my computer’s LAN address in the meantime meaning my computer ended up using the next available LAN address. This meant all the port forward rules for the original LAN address became broken and no longer worked for my computer.

Router’s generally allocate LAN addresses sequentially from .2 onward.

So if your household has many devices that access the internet you might need to think about the above scenario. Such devices might be other computers, Tablets, Mobile phones, Game consoles, TV’s, Wristwatches, Ebook readers, Digital cameras, Smart Home devices, Appliance Controllers, etc.

To overcome this possible problem I recommend setting a static LAN address starting at a much higher number such as .30 or .50, but you could also use .100 or anything up to .255 to be on the safe side so there are no possibilities of LAN address clashes after your device has been switched off for a period of time.