There are a couple of things in this thread that flagged up as I read through...
...then in Windows Firewall under 'Inbound and Outbound Rules' I've allowed connections for TCP Ports 52100-52200 (local and remote) and also set a static IP address in the Network Adapter Settings.
I have never needed to look at, or change, any Windows Firewall settings. On first run of the MC major build, Windows Firewall prompts, asking if I want to allow Media Center to communicate, I tick everything and allow, and then it never bothers me again until the next major build, 26.0.1 in my case. Everything 'just works'.
Then I apply these settings. I've also tried putting 52199 as the start and end ports, same goes for Windows firewall.
I have never needed to use a range. Start and end ports of 52199 has always been enough, and again, no visits to Windows Firewall settings have ever been necessary.
These are the only settings my router asks for when i go into port forward settings:
Local IP (Static IP - 192.168.0.XX)
Local start port (52100)
Local end port (52200)
External start port (52100)
External end port (52200)
Protocol (TCP)
Then I apply these settings. I've also tried putting 52199 as the start and end ports, same goes for Windows firewall.
I've never used trace route before, I understand I go into command prompt, type tracert then my static IP? This doesn't seem to flag up anything
I set "Protocol" to "Both" and never changed it as that worked for me (I'm not really a network guy and don't know the difference between UPD and TCP)
There should also be an "Enable" option under the protocol setting... That was definately set to "Yes"?
Once added, the details should be listed in the Port Fowarding section. If it is not enabled, enable it and click the "Apply Changes" button.
My understanding is that it shouldn't make a whole lot of difference, but, me...?
I never set the static IP address in Windows. I just leave that alone, and instead prefer to use the "Address Reservation" settings in the DHCP section of the router setup. In my mind, it keeps the whole setup of the server in one place, ie, on the router. I tell the router to always assign that IP address to the PC, then use that address in the port forward settings. Again, all of this has 'just worked' for me.
I have never needed to disable the router's firewall either.
I didn't see it, so, think we should rewind quite a way back and ask...
How are you directing Gizmo to your server?
This could be MC's 'access key' method, or direct input of ip address?
What version of MC are you using?
In latest versions of MC,
http://ex.ter.nal.IP:52199 should default to
http://ex.ter.nal.IP:52199/Panel/ and prompt for login details if you enabled authentication in the MC server settings.
52199 is MC's default server port. Double check under MC > Options > Media Network > Advanced that the TCP port number didn't get changed.
Are you using a VPN service?
If you are, then you have virtually no chance of any of this working as the port forwarding would need to be set up at the VPN source and it's not something they generally offer.
I can run the router they've supplied me in 'modem mode' and then buy a new router as a last resort.
This is unlikely to make any difference. Port forwarding on the Super Hub 3 does work. Something amongst the settings of your Super Hub/Windows/MC/Gizmo is wrong.
-marko