aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Low ID might be a bug?  (Read 3837 times)

Knuty

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 9
Low ID might be a bug?
« on: February 09, 2005, 12:45:13 AM »
I was running Amule 2 for few days. I opened the according ports in order to get a high ID which worked fine, but since today I get all the sudden only low IDs. I did not change anything. Could that be a bug?   ?(
Logged

Supersnail

  • Full Member
  • ***
  • Karma: 4
  • Offline Offline
  • Posts: 186
Re: Low ID might be a bug?
« Reply #1 on: February 09, 2005, 03:56:49 PM »
From the wiki:  http://www.amule.org/wiki/index.php/AMule_problems#aMule_connects_to_server,_but_it_is_always_given_LowID._Why?_and,_can_I_do_something_about_it?
Quote
aMule connects to server, but it is always given LowID. Why? and, can I do something about it?
This can bue due to three reasons:

    * Some necessary port is not opened in your firewall. Read this to get to know what to do and check here if the ports are open.
    * The server is very busy or maybe badly configured, so it's giving you a LowID. There's nothing that can be done in this case other than reconnect or connect to some other server.
    * Some ISP forbid the use of p2p applications, such as aMule, by not allowing traffic through popular p2p ports. In these cases, configure aMule to use some other port. It would be even better if it was some popular port used for some other issue. It's been known that on some ISPs it worked with port TCP 25600.
Logged