In the past few weeks I've noticed aMule only seems to want to connect to PEERATES.NET - at least 95% of the time. The Log file always reads:
Servers: Trying to connect
Connecting to
www.UseNeXT.to (87.230.83.44 - 87.230.83.44.4661)
Connecting to
www.UseNeXT.to (87.230.83.44.4661)
Servers: Connected
Connection established with: PEERATES.NET
Warning: PEERATES.NET (88.191.81.111:1111) - NG: Please try to use a random port instead of 4662 because a lot of ISP's have filters on port 4662. Any number between 80 and 65530 should be OK.
The problem with PEERATES.NET is it has no files I want to download (plus the filtering of port 4662, which I'm guessing now is the reason for low ID - see previous post). So how do I prevent aMule from connecting to PEERATES.NET (can I delete PEERATES.NET from the server list?). Before I used to be able to connect to Sausagetube.net or one of the big eDonkey networks, for example, which always have thousands of files I want to download.
I've also noticed that since the problem of aMule only wanting to connect to PEERATES.NET started, I'm no longer receiving any requests for shared files from my aMule Downloads folder, which currently holds about 5 GB of files. So I don't think its just a coincidence.
Currently my server list contains 194 servers and the URL I always use is:
http://ocbmaurice.dyns.net/pl/slist.pl?download/server-best.met