aMule Forum
English => Multiplatform => Mac OSX => Topic started by: DRK on September 30, 2005, 05:34:34 PM
-
Hi.
I' using aMule v2.0.3 and in the last days I've been getting low-id. This is weird because I've never had any kind of problems, always having High-ID.
I'm using a D-Link 504T and I have all the needed ports forwarded.
The strangest part is that when I use a Windows box that I have in my LAN, I connect with High-ID.
I'm in Mac OS X v10.3.9 with all the latest updates.
Can you guys help me?
Thanks in advance.
-
Is your Mac assigned a static IP? The rules you set up to forward the ports to the Mac are configured with a specific IP address. However, sometimes your router will assign a different IP address to your Mac when it goes to renew its DHCP lease. If your Mac was assigned a different IP address than the one used in the port-forwarding rules, then they would cease to function properly.
The other possibility is that your ISP has detected high bandwidth on certain ports and is now blocking those ports. Your Windows machine might not be affected because (presumably) it is using different ports than the Mac.
-
Originally posted by ken
Is your Mac assigned a static IP? The rules you set up to forward the ports to the Mac are configured with a specific IP address. However, sometimes your router will assign a different IP address to your Mac when it goes to renew its DHCP lease. If your Mac was assigned a different IP address than the one used in the port-forwarding rules, then they would cease to function properly.
The other possibility is that your ISP has detected high bandwidth on certain ports and is now blocking those ports. Your Windows machine might not be affected because (presumably) it is using different ports than the Mac.
I'm not using DHCP, so both computers have static IP.
I've tested aMule with the ports that I was using in my Windows machine but still can't get High-ID.
-
Just a wild guess: Given that you are from Portugal, you are probably using an ipfilter.dat. Is it possible that a recent update of your ipfilter.dat is causing your problem?
-
Originally posted by lionel77
Just a wild guess: Given that you are from Portugal, you are probably using an ipfilter.dat. Is it possible that a recent update of your ipfilter.dat is causing your problem?
I have tested aMule without upfilter.dat and it remains the same.