aMule Forum
English => Multiplatform => Mac OSX => Topic started by: glynnkjk on December 30, 2006, 10:34:25 PM
-
I hope someone out there can explain this. I have set my TCP port to 39996 and my UPD to 39999 on my Mac, router and the aMule prefs. It was working fine but all of a sudden, upon a restart, the UPD port changed in the aMule prefs. This caused the KAD to be firewalled. I reset it four times and each time I made the change in the prefs and restarted, I got a new UPD port. All four times a different one!!!! Has anyone run into this before? Is there a solution? What can I do to help diagnose the cause for further members that may come across this??
Thanks,
-
Hi glynnkjk!
There are 3 ports aMule uses: a TCP port, an extended server request UDP port (which is port number TCP+3) and an extended client UDP port.
As you see, there is already the extended server request UDP port on port number TCP+3 in your case 39996+3=39999. As you have set the extended client UDP port to 39999 as well and it is not possible to use one port twice aMule changes the extended client UDP port.
Short: Change the extended client UDP port (the UDP port changeable in preferences) to something else and it shall stop changing. :)
Regards
-
Thank You, I must of misread the How To when I was configuring....
Will do and thanks again :baby: