Port Forwarding issues with Smarthub SH35A

[Smudger1971]

I'm having a few issues with port forwarding on a new SmartHub SH35A.
I've recently moved from BT where I had on old BT Smart hub with some rules to give me external access to couple of machines on my home network. These worked!
Swapping over to EE - none of the same rules seem to work - except for few rules that have been added via uPNP.

For exmple, my Emby server has created a rule to forward port 8096 through to the server and this works and is seen as open via 'canyouseeme'
I've added rules to forward ports 80,443,8444,5000,5001 and a few others  (all via TCP) to my synology server - which is actively listening on these ports. Internally from my home network I can use these ports, but when I test via 'canyouseeme' - all the ports appear closed.

I've even tried a rule to forward external port 8099 to internal port 8096 (Emby Server) and even that is showing a closed - whilst the uPNP rule 8096 to 8096 is fine.

Any suggestion or fixes would be appreciated

[JimM11]

@Smudger1971 See the very end off the link below.

Smart Hub 7 Plus Port Forwarding Issue - Page 11 - The EE Community

[Smudger1971]

@JimM11 Thanks for this.

I think I'll try:
- using MinUPnP to remove the uPNP rules first , then switch off uPnP and then add them manually 

OR

-  Add all my rules via MinUPnP
Anything to avoid a factory reset on the Hub - but if requires it , then so be it.
 

[JimM11]

@Smudger1971 Link also shows what the 7 Plus is on FW updates, normally happens when unit is first connected, but worth a quick check that yours is up and on the latest, will save you a bit of fighting the 7 Plus hub as the OOB FW is very suspect.

[Smudger1971]

@JimM11 Thanks for all you help with this issue. As promised a brief update

After a few failed attempt at mimicking a uPNP client across various devices on my network, I gave in and reset the Router.

The uPNP client repeatedly failed with error 606 (action not authorised) when trying to add or delete a port - regardless of the machine I used. 
The only command that would work was 'upnpc -l'  to list the ports - BUT that only found port 8096. Port 8920 was also added by my Emby server, but never listed with the upnp client. 
As for the firmware - I'm on r3.35.24-R-1648110-PROD-84001  with app version 3.11.3 - which accoriding to the aforementioned thread, is the latest.

As I've had the router for approx 3 months, I suspect it came with a lower FW version initially and updated after the Emby server had written its port rules. 

For now uPNP has been switched off. 
Again - many thanks for pointing me in the right direction