eMule Low ID: connection checklist Blank template | Documentation review: 2026-09-10 | natchecker.com/blog/emule-low-id Client name and version: Operating system / container network: Date and time: Route carrying the client: ISP / VPN LAN IP / DHCP reservation: Router WAN IPv4 (ISP path only): Public IPv4 of the same route: CGNAT / double NAT evidence: VPN provider, protocol, location, forwarding feature: PORT INVENTORY (copy actual client values; defaults are not requirements) Function Protocol Client port Public port Mapping target ED2K peer TCP ___________ ___________ ______________ Client / Kad UDP ___________ ___________ ______________ aMule server UDP, if used ___________ ___________ ______________ Other documented listener ___________ ___________ ______________ Firewall app path and active profile: Rule / policy source (router / VPN): BEFORE AND AFTER (change one thing at a time) Change made: Client running during test: yes / no Tested public IP and ports: TCP test: pass / fail / not tested UDP test: pass / fail / not tested (a TCP-only test is not a UDP result) ED2K server and ID status: High ID / Low ID / disconnected Kad status: Open / Firewalled / disconnected / not used Result after client restart: Result after VPN reconnect; new assigned port if any: Next check: OUTCOME Resolved: ED2K High ID and Kad Open (if Kad is used) Still blocked: ISP access / VPN mapping / client status mismatch Support contact and evidence to provide: Server log, if a passing TCP test disagrees with ED2K status: If inbound access is unavailable: Low ID may remain; downloads can still work. BEFORE BUYING A VPN Ask support: Does this exact plan/add-on, OS, VPN protocol and location provide every port/protocol pair listed above? Does the assignment change? Full subscription + add-on cost and current cancellation/refund conditions: No test results are prefilled. Store this sheet privately; redact IPs and account details before sharing. An open port does not guarantee speed.