Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ngllgn]

Oh, and the server log also tells me that 'Your XXXXX port is  not reachable. Please review your network config.'

This XXXXX is the same in all the settings in the aMule preferences, the iMac Securtiy/Firewall settings and the Router NAT Virtual Server set-up, port forwarding and port triggering settings.

[Stu Redman]

- If you upgrade from 2.2.5 to 2.2.6 there is no reason to change anything in the router config or in aMule's config. Looks like you have configured your system to death.
- You can either use port forwarding (preferred) or UPnP. Both together makes no sense.
- Disable NAT port triggering
- Disable NAT virtual server
- Just forward your TCP port and your UDP port (and if you use servers the extended server requests (TCP+3) port)
- And make sure your firewall isn't blocking aMule.

[ngllgn]

- If you upgrade from 2.2.5 to 2.2.6 there is no reason to change anything in the router config or in aMule's config. Looks like you have configured your system to death.

Perhaps that's the problem. But after not being able to connect using 2.2.6 for the last couple of weeks having done nothing else but upgrade, I had to try something.

- You can either use port forwarding (preferred) or UPnP. Both together makes no sense.

I have disabled UPnP in aMule.

- Disable NAT port triggering

Done.

- Disable NAT virtual server

Done.

- Just forward your TCP port and your UDP port (and if you use servers the extended server requests (TCP+3) port)

Done, although I have no idea what  servers are involved and what an extended server is, or is not. I have a very simple set-up: one router and one Mac that connects to the router via wifi. But the moment I do this port forwarding in the router, the details appear on the Virtual Servers Setup router page. The one  bit I am unsure about here is what IP address I should be putting in here. Should it be the router IP address?

- And make sure your firewall isn't blocking aMule.

System Preferences/Security/Firewall/Advanced/

I have added aMule (again) here, so that the green light shows next to aMule with the text "Allow Incoming Connections".

I have done this about 6 times now, but I am still getting a low ID, Kad is firewalled and the two arrows in aMule stay yellow (as for the past 2 weeks). Another difficulty with aMule 2.2.6 is that it is very difficult or impossible to drag or move it on the desktop...it seems to freeze a lot of the time. Having said all this, aMule 2.2.2 worked brilliantly for me for a long time on an old iMac and I don't wish to complain about not being able to make it this time yet. There is something that is just not quite intuitive about it still.

[ngllgn]

Well, well. aMule 2.2.6 has just decided to start working. Thanks for your help.