28-01-2026 05:17 PM - edited 28-01-2026 05:49 PM
Hi all,
I had port forwarding working fine yesterday, but overnight I think my Smarthub Pro 7 had a firmware update to
r3.8.26-R-1595999-PROD-1
and I can no longer seem to get this working even after removing the rule and re-adding. I have restarted the router to no avail.
Anyone else having a similar issue? It's only day 2 of me having this hub/router and I've just returned my previous smarthub.
Many thanks
p.s. Something that did cross my mind, netgear recommend a factory reset after upgrading firmware, and I had issues with one of their routers when I didn't do this step, but after it was rock solid; so is the lack of a factory reset potentially an issue?
Solved! See the answer below or view the solution in context.
29-01-2026 10:11 AM - edited 29-01-2026 10:16 AM
OK - so this looks to not be related to port forwarding at all but a windows PC firewall issue I believe.
Booting to linux gives flawless results, so I'll start investigating the windows side.
Thanks for all the suggestions and help
Update - adding incoming rules for port 443 on TCP/UDP has resolved the issue
28-01-2026 06:39 PM - edited 28-01-2026 06:42 PM
@MisterWoody_ Do it if you have nothing to lose, EE Router, new FW so who knows was out over a month ago on the Pro and nothing Forum wise about PF not working!
FW: r3.8.26-R-1595999-PROD-1 and the gui is at App Version is 3.1.3.19 24/12/2025
28-01-2026 07:52 PM
There are quite a no. of reports of this issue for a SH 7 Pro, e.g.:
28-01-2026 09:10 PM
Sounds like a plan - as the router was delivered yesterday, it likely had an older firmware version if it was just taken from a stockpile.
Fingers crossed it won't take too long to reconfigure from default settings. Thanks for the details
28-01-2026 09:12 PM
Weird how the firmware installed when delivered from stock worked with no issues.
I'll go with a factory reset and see how that goes.
Will see if I can do a quick backup and restore if such a feature exists.
Thanks
28-01-2026 09:15 PM - edited 28-01-2026 09:18 PM
@MisterWoody_ You can for sure guarantee that, and it's just best to let the Router update and you are NOW at the latest FW unfortunate the sucker did it Overnight instead of right away for you! So new should not be very painful on the Factory Reset and i really hate saying for it to be done, just don't do it myself and as the EE Router is a no backup/restore facility on it at all even worse advice to give anyone..... Know what i mean.
We were crossing each other over, don't waste you time, NO backup/restore at all, but should i say have a look, been gone from EE nearly a year now you just never know!
28-01-2026 09:18 PM
Factory Reset won't reset the f/ware, just the settings back to the defaults.
Backup/ Restore not present!
28-01-2026 09:44 PM - edited 28-01-2026 09:54 PM
Indeed - I never meant to suggest that it would. As my initial post mentioned this is recommended by Netgear for their routers and after doing that I had a rock solid connection.
So I was looking for best practice.
Unfortunately - after the factory reset it's made zero difference so in this case to the Smart Hub 7 Pro, I assume not applicable.
¯\_(ツ)_/¯
28-01-2026 10:11 PM
@MisterWoody_ There is a lot of PF issues going on with the new EE Router called the 7Plus but NOT the version that you have, and the FW you are posting up for sure is the latest on that EE Pro router, just double and triple check that the IP off the device you are PF to/from has not changed, and in the Advanced Lan section you can go tell the IP to stay fixed to the mac address, all done through the web manager interface, not so sure what you can do with the EE app as most off the time it's a suck and see what works with it! Web manager is normally pretty good but a little slow at times!
28-01-2026 10:26 PM - edited 28-01-2026 10:26 PM
It's a static IP address assigned on the PC itself, so it's not even using DHCP (or at least it shouldn't be).
I tweaked the range that will get allocated too and this IP isn't in the range.
I may boot into linux tomorrow just to confirm it's not a weird windows issue that has cropped up and eliminate that at least.
Going to call it a night though for now - there's always tomorrow 🙂
Thanks for the suggestions though