aMule Forum
English => aMule Help => Topic started by: mellowd on December 28, 2007, 09:28:00 AM
-
Hi there.
I've just installed the amule daemon and amule web on my linux server at home. It is a headless server. I have configured amule to connect using port 45161. I have also downloaded a server.met file with a bunch of servers on port 4661. I have correctly forwarded ports on my external firewall.
I can't connect though, looking at the firewall logs I see this: 38.107.161.46:0. Amule is trying to connect to 38.107.161.46 on port 0. Why is this? It's obviously not working, but why does amule keep trying to connect on port 0?
Thanks!
-
Maybe if you post the OS version, which firewall, amule version, wxGTK version and similar stuff, we could help.
Regards.
-
I have exactly the same problem.
When I launch amule, I see that it try to connect servers on port 0. An example :
Amule log :
2008-07-20 14:06:26: Servers: Trying to connect
2008-07-20 14:06:26: Connexion à Donkey University-DU (72.172.89.135 - 72.172.89.135:0)
2008-07-20 14:06:26: Connexion à Donkey University-DU (72.172.89.135:4661) perdue
tcpdump log :
14:06:26.182442 IP 192.168.1.100.45741 > 72.172.89.135.0: S 2191286763:2191286763(0) win 5840 <mss 1460,sackOK,timestamp 5034788 0,nop,wscale 6>
14:06:26.376061 IP 72.172.89.135 > 192.168.1.100: ICMP host 72.172.89.135 unreachable - admin prohibited, length 68
I use an mandriva release 2008.1, and aMule 2.1.3 using wxGTK2 v2.8.6 (Unicoded) (OS: Linux)
I have no firewall at all.
I think the problem really come from aMule, which really try to connect the server on port 0 instead 4661.
How can I solve this problem ?
Regards,
Cyril
-
Please try aMule 2.2.1.