aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Confusing LowID  (Read 2226 times)

Sloblocks

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Confusing LowID
« on: June 13, 2005, 03:28:23 AM »
I thought I was pretty savvy regarding networks, routers and ports, but this one has me totally confused. Any help would be much appreciated...

I am running EMule on an Windoze XP machine and aMule 2.0.0 on my new Mac mini (OS10.4). Since they are going through a router (D-Link 264) I have set EMule to listen on TCP4662 and aMule to listen on TCP5662. I've got all the router stuff set up correctly and I can see connections to port 5662 blocked in the Mac firewall log if I switch off the setting I have put in there.
I've also done a netstat and can see that, sure enough, something is listening on ports TCP5662, UDP5665 and UDP5672.

All sounds good, EXCEPT I always get a lowid still.  :(

Any ideas would be greatly appreciated.

Cheers,
Rich.
Logged

tas_mania

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
  • Linux user 10 years
Re: Confusing LowID
« Reply #1 on: June 13, 2005, 12:35:11 PM »
Try a different port on the Mac
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: Confusing LowID
« Reply #2 on: June 13, 2005, 09:23:30 PM »
You can try http://www.amule.org/testport.php.

Either you don't have ports forwarded properly, or there's another firewall involved somewhere.

Oh, and it has nothing to do with your problem, but you should update to v2.0.2.  There's a nasty bug in 2.0.0 with certain servers causing aMule to hang and use all the cpu.
Logged

Sloblocks

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: Confusing LowID
« Reply #3 on: June 14, 2005, 12:30:10 AM »
OK thanks for the advice.

I will try changing the port and I'll upgrade too.

Cheers,
Rich.   :)
Logged