Re: Nat Type Strict on XboxOne Wired Connection using Hub3.0
10-03-201601:34 - edited 10-03-201601:36
Hello, I've just switched from talk-talk and discovered the exact same issue as you.
The problem is caused by the vm hub 3.0 not opening all the required ports for xbox live to work correctly (well at least one isn't opened)
Xbox live needs a precise set of ports to be fully accessible in order to function correctly, you can normally achieve this by either manually port forwarding each required port or simply by adding your xbox one ip address into the DMZ mode. Unfortunately neither option works with the new hub 3.0 and i suspect with all recent posts about errors with xbox live probably other hubs are affected also (hub 2.0)
It seems like the new hub 3.0 comes with port 53 locked down, when you try to port forwarded this port the vm hub refuses the rule stating port reserved. (Nat was showing strict majority of time occasionally going to moderate)
You can try putting your xbox one in the hub 3.0 DMZ mode but as stated above even that refused to work correctly for me, it seemed to open every port needed apart from port 53 again. (Nat stuck at moderate all time)
The only fix i found was to put the hub 3.0 in modem-only mode, very easy to achieve but has its own drawbacks mainly you'll need an external router to plug into the hub 3.0 and have all your devices plugged into that router (switching vm hub 3.0 into modem-only mode basically disables all the built-in router side of things, dhcp,nat,upnp,firewall, everything)
Xbox Live requires the following ports to be open:
Port 88 (UDP)
Port 3074 (UDP and TCP)
Port 53 (UDP and TCP)
Port 80 (TCP)
Port 500 (UDP)
Port 3544 (UDP)
Port 4500 (UDP) Note Some game developers require you to open additional ports.