This entry is a user-made guide and not verified by any eMule developer, but is still a helpfull addition for most users. You you can find questions and comments on this topic in a dedicated thread on our forum.

• No IP is known of the machine eMule is running on therefore all requests like queue or connection requests to this client have to be routed over the server, the low ID client is connected to. This routing causes considerable amount of CPU load on the server thus reducing the maximum number of users the server can cope with. Lugdunum's servers limit the number low ID users or even ban them at all.
• Two clients on low ID cannot connect to each other, as it is not possible to route messages over two different servers. This will lead to less sources for the downloads.
• On busy servers it may well happen that the messages gets lost and eMule misses important information about queue progression or download requests. This may lead to fewer credits and worse downloads.

• Misconfigured routers
  Problem: If you are connected to the Internet through a router you have to do some port forwarding on your router in order to get a High ID.
  Solution: There are many routers and it is different from router to router how you forward ports. Similar for all routers is that you have to forward you external IP to your internal IP for all eMule's ports. The official router's section in eMule's documentation gives you some help and www.emulehelp.tk also gives some help regarding port forwarding. Your should also check the manual that came with your router for information regarding port forwarding. If you still have problems forwarding your ports after reading through all the information on these two pages and your manual then create a new thread in the Hardware forum to get support from users on this board. Remember to give all the nessacary information in your thread to make supporters able to help you.
  
  
• Misconfigured firewall
  Problem: If not properly configured your firewall might block the ports eMule uses hence the Low ID.
  Solution: There are many different firewalls and many different ways of configuring each of them. The official firewall's section in eMule's documentation helps regarding this and www.emulehelp.tk also offers help regarding this. Also try checking the information that came with your firewall or is located on the manufactors homepage if the two links posted didn't do the trick.
  
  
• The built in Windows XP firewall is enabled
  Problem: If not properly configured the bulit in firewall in Windows XP will block the ports eMule uses hence the Low ID.
  Solution: The official Windows XP firewall section in eMule's documentation gives a guide to configuring the built in Windows XP firewall. If you are running another firewall you can also disable the XP firewall.
  
  
• Internet Service Provider is blocking eMule's ports
  Problem: A rising amount of ISP's are beginning to block known ports for p2p applications. When a port is blocked no traffic can go through that port and you will be stuck with a Low ID.
  Solution: You can change the ports eMule uses in eMule's preferences -> Connection to something else between 1056 and 65535. Try different ports and try choosing a port not already used for something. If your ISP is blocking ports you might want to think about getting another ISP if possible.
  
  
• Natted connections
  Problem: Your are on some sort of network that gets all its traffic through one IP and then NAT's the traffic to all the users in the network.
  Solution: If you are on a natted connection there is really not that much you can do. Some ISP's let you get a "public" IP for a little fee every month but not all ISP's. If you really want a High ID you should consider getting another ISP.