My ports are now open!!!!
I did nothing except changing my network profile from Public to Private (it was set as Public just by a mistake). But I'm not sure if this change has anything to do with this.
As I said I reverted all my router settings to factory settings, and after that I just added a port forwarding TCP rule and another for UDP (the same rule with a single port for TCP/UDP did not work).
At the moment of doing that, I tried to check the port open and it was not, but now I opened eMule and did the port check and all is fine for my TCP and UDP port forwarding. I don't get a low-id anymore.
Maybe it just needed some minutes to apply and reflect the port forwarding changes?.
Also I noticed that the ports are open only while eMule is running, maybe I missed this crucial detail before, because many times I was checking my ports without eMule running (but also with eMule running, and they failed).
At the end and because my settings are in its factory state, I have not set a private static ipv4 address nor modified the DHCP range, nothing of nothing. firewall is enabled in router settings, all as default. I Just added the port forwarding rules, and it works again!
At this point I can't tell what the problem was. But maybe in the future I have this problem again and I'll need to comeback here to read this:
1. Just in case, set Network profile to Private (because it is a domestic network)
2. Just in case, enable all network related windows services. DHCP client service is crucial.
2. Go into http : //192.168.1.1 and set router settings to its factory settings.
3. Add the port forwarding rules (one for the TCP port and another for the UDP port). Port triggering rules are NOT necessary at all. Firewall can be enabled. NAT enabled. uPNP enabled. DMZ disabled. (all as defaults)
4. Check the ports via https : //portchecker.co/ but
with eMule running, otherwise the port scan will fail.
This post has been edited by pitoloko: 06 May 2022 - 04:37 PM