aMule Forum

English => Multiplatform => Mac OSX => Topic started by: aMuX on August 03, 2007, 07:10:34 PM

Title: Low ID all the time, but TestPort reports sometimes that it is OK
Post by: aMuX on August 03, 2007, 07:10:34 PM

I always get yellow arrows (Low ID) instead of green (High ID) on on aMule CVS 2.2.0 Rev. 6921 on Mac OS X 10.4.10

When I test the aMule TCP on http://www.amule.org/testport.php I may get two different results, depending on the moment I test it:

Sometimes I get:
Success The TCP port XXXX is available. You should be able to use the ED2K P2P service without any problems.

Most of the times I get:
Error: TCP port XXXX is unavailable. Make sure your firewall or router is allowing/forwarding this TCP service port and your ED2K client is running (i.e. aMule, eMule).
Detailed Error Message
TCP Error 113 Connection refused
Explanation
No info available; this TCP error probably indicates a problem with the networking on your system (i.e. the TCP/IP stack).

I am puzzled. This very same configuration worked for me with all green arrows (High ID) some time ago. Of course I have open the ports in Apple System preferences and the router.

My ISP does not block any port.

Any idea most welcome.
Thanks.

Title: Re: Low ID all the time, but TestPort reports sometimes that it is OK
Post by: aMuX on August 04, 2007, 10:18:01 AM

Fixed!!!

How? Well, it may sound weird, but I just changed both the TCP and UDP ports in all Mac OS X-System Preferences-Sharing-Firewall, my router security (Virtual Servers & Port Triggering) and aMule-Preferences-Connections. After opening aMule I got both arrows green (High ID) immediately.

Just for the records.

Thanks.

Title: Re: Low ID all the time, but TestPort reports sometimes that it is OK
Post by: pietro10 on August 04, 2007, 04:56:24 PM

Okay, can you tell me exactly how you did that? I'm getting low IDs but the test always gives me Success.

Quote from: aMuX on August 04, 2007, 10:18:01 AM

Fixed!!!

How? Well, it may sound weird, but I just changed both the TCP and UDP ports in all Mac OS X-System Preferences-Sharing-Firewall, my router security (Virtual Servers & Port Triggering) and aMule-Preferences-Connections. After opening aMule I got both arrows green (High ID) immediately.

Just for the records.

Thanks.

Title: Re: Low ID all the time, but TestPort reports sometimes that it is OK
Post by: aMuX on August 04, 2007, 07:56:32 PM

Quote from: aMuX on August 04, 2007, 10:18:01 AM

Fixed!!!

How? Well, it may sound weird, but I just changed both the TCP and UDP ports in all Mac OS X-System Preferences-Sharing-Firewall, my router security (Virtual Servers & Port Triggering) and aMule-Preferences-Connections. After opening aMule I got both arrows green (High ID) immediately.

Just for the records.

Thanks.

Quote from: aMuX on August 04, 2007, 10:18:01 AM

Fixed!!!

How? Well, it may sound weird, but I just changed both the TCP and UDP ports in all Mac OS X-System Preferences-Sharing-Firewall, my router security (Virtual Servers & Port Triggering) and aMule-Preferences-Connections. After opening aMule I got both arrows green (High ID) immediately.

Just for the records.

Thanks.

UPDATE: without changing anything (aMule has been on running all that time), now I get the upper arrow yellow and the bottom arrow green. If I go to

http://www.amule.org/testport.php

and check the TCP port, it says:

Error: TCP port XXXX is unavailable. Make sure your firewall or router is allowing/forwarding this TCP service port and your ED2K client is running (i.e. aMule, eMule).

I am puzzled. What is going on? Is it normal that aMule shows both arrows green, but later on one or the two arrows yellow?

Thanks.

Title: Re: Low ID all the time, but TestPort reports sometimes that it is OK
Post by: aMuX on August 05, 2007, 09:58:40 AM

Update: now both arrows are green, without doing anything (aMule has been running all that time).

Checking TestPort thee times in a row shows:

- First the Error reported above.
- Second no prblem.
- Third no problem

So, now TestPort is OK: "Success The TCP port XXXX is available. You should be able to use the ED2K P2P service without any problems".

Are such changes normal?