Port forwarding not working

Nonamesleft
Established Contributor
Established Contributor

Hi, I recently moved from a different ISP to EE and I'm trying to open some ports on  my EE smart hub / router.

I am trying to open ports 58110-58120 (TCP and UDP) on one machine (internal static IP 192.168.0.16) and ports 55370-55380 (TCP and UDP) on another machine (internal static IP 192.168.0.111).

If I check the ports with port checker, they are closed and the smart HUB seems to ignore whatever rule I add in there. Tried rebooting, resetting and the usual stuff. Device does not seem to be willing to comply with instructions given.

7 REPLIES 7
bobpullen
Scholarly Contributor
Scholarly Contributor

What hub are you using and when you say "the smart hub seems to ignore..." what do you mean?

Note that port checker is unlikely to be of any use for UDP ports and you will also need to ensure that there is some sort of service listening on the TCP ports for them to be shown as open.

Nonamesleft
Established Contributor
Established Contributor

HI, thanks for the reply. I do have a Smart HUB SH40J. I think it's the latest model, was sent to me like 10 days ago, when I ordered the 1.6Gbps fiber connection.

What I mean is, I can write any port range and the ports would not open. I am aware of the UDP issue, as stated on my post I am trying to open them both for TCP and UDP.  There is a program running on both machines that is trying to listen on those ports for both TCP and UDP. As stated the one running on  192.168.0.16 is trying to listen on ports 58110-58120 and the same program running on a different machine (192.168.0.111) is trying to listen on ports 55370-55380.

I have been able to open some other ports on the router a few days ago and I had no issues with them, I am able to access what I am running from my mobile phone when I am away but for some reason it does not seem to apply the rules that I tried to add today even tho they are saved and I can see them if I reload the page. 

bobpullen
Scholarly Contributor
Scholarly Contributor

So, it's not all of your rules then? Is the (I assume) Plex server working? Of the 7 rules pictured in your other post, which ones aren't working?

Is it just those to the 192.168.0.111 device? If so, is this a Windows machine, and have you checked that the network connection hasn't flipped from Private to Public as part of the router swapout?

Edit: re-read your post and understand that it's a service on more than one local machine. Still worth checking above. I'm a bit confused by the mobile phone observation though. Are you saying that the rules *do* work when you're not connected to the Smart Hub Pro? If so, that's potentially a different issue.

Edit again: another re-read and I wonder if it's a problem with port ranges. It's going to be a PITA but if you delete the rules and re-enter them one by one for each individual port instead then does that change the situation?

Nonamesleft
Established Contributor
Established Contributor

They are both Win 11 machines. Plex does work on both machines and I can access it from outside my home network.  After a few HUB /  Machine reboots it seems that I am now able to reach everything on 192.168.0.111.

Still i am not able to reach ports  58110-58120 (tcp/udp) for 192.168.0.16. Mind, this was not an issue with the previous internet service provider and the ISP is the only thing that changed in the enviroment. 

bobpullen
Scholarly Contributor
Scholarly Contributor

Some progress then ðŸ™‚

Both the hub and the ISP have changed. By entering the affected ranged rules as ~10 individual rules instead then we can at least try and work out if the hub has some sort of bug with port ranges.

Nonamesleft
Established Contributor
Established Contributor

After switching from the 10 port range to a smaller range (58115-58118) it's now working. Thanks for your help, still it does not make much sense to me, I wonder if I have been triggering some kind of bug or something like that. Anyway, thanks for your time and help. Much appreciated.

bobpullen
Scholarly Contributor
Scholarly Contributor

Great stuff.

One to keep an eye on in case we see any other similar reports around these parts.