The latest build going out to Preview Alpha contains some small, cool features that I'm really happy about:
UPnP Failure Notification: If a Moderate or Strict NAT is detected and the console was also unable to successfully port map via UPnP, the console will display UPnP not successful under
Network Settings. A link will also be displayed that points to xbox.com/xboxone/UPnP. We've got some updated documentation that covers the most common causes of UPnP mapping failures and how to work around the issues that will be updated under this link, but our publication team currently has their work cut out for them with the drafts I sent as they have to fix all of my run-on sentences and penchant for abusing commas whenever possible.
Double NAT Detection: If a Moderate or Strict NAT is detected alongside a double NAT, the console will display Double NAT detected under
Network Settings. A link will also be displayed that points to xbox.com/xboxone/DoubleNAT. The documentation for this support page is also in progress, and I've heard that the publication team is now working with Microsoft Research to leverage machine learning to try to translate my documentation into something that resembles human readable text.
Some notes on these features.
- We only display the UPnP failure and double NAT detection notifications if the NAT type is not Open. If you have a router that doesn't support UPnP but still provides an Open NAT, there really isn't a need to spend time configuring workarounds like port forwarding rules, DMZ settings, etc. Ditto for a double NAT.
- Double NAT detection relies on some UPnP calls to your router. If UPnP isn't supported on your router or isn't functioning for some reason, we won't be able to detect the presence of a double NAT. This isn't a showstopper though as we will still detect that UPnP isn't working alongside a non-Open NAT. Once UPnP is working on your router but the NAT type still isn't detected as Open, the console will then be able to check for the presence of a double NAT.