LowID | Windows portable

[irmu]

I keep having LowID on windows using has a have been for the past 2 decades, portable version of my mule.
I'm successfully using 2 other clients - both portable as well - and I get almost instant HighID.
Everything on windows firewall and router is good to go.
I should also mention that I have amule flatpak running with HighID on a debian machine.

[got3nks]

Hi @irmu — LowID just means the eD2k server couldn't open a connection back to aMule's listening TCP port, i.e. that inbound port isn't reachable from the internet. "Firewall and router good to go" can be true for your other clients yet still not cover aMule: Windows Firewall rules are per-program, and a router forward targets a specific port — so a rule/forward that works for another client won't automatically apply to the portable amule.exe or the port it uses. Let's confirm it one step at a time instead of changing several things at once.

1. Find aMule's port. Preferences → Connection → "Client TCP port" (default 4662). Note it down.

2. Rule out a port clash — across your whole network. A given inbound port can only be forwarded by the router to one device, so two P2P clients using that same port can't both be reachable — even on different machines. Close every other P2P client everywhere on your LAN (this PC and any other device), leaving only aMule running for the rest of this test.

3. Test the port from the outside. With aMule running, check whether that TCP port is reachable from the internet using one of these:

• https://www.canyouseeme.org/ (enter the port)
• https://www.yougetsignal.com/tools/open-ports/

If it shows closed, the server can't reach aMule either — that's your LowID. If it shows open but you still get LowID, that's a rarer case and the logfile will tell us more.

4. If it's closed, it's one of two gaps — and now you can fix just the relevant one:

• a router port-forward for that exact TCP port → your Windows PC's local IP (Kad also wants the UDP port forwarded), or
• a Windows Firewall inbound Allow rule for the specific portable amule.exe (a portable build in a new folder doesn't inherit the rule your other client has).

Let us know what the port checker reports (plus aMule's port and version); if it's still stuck after that, paste the connection part of the logfile as text and we'll narrow it down.