[New Feature] Xbox One update coming

[DanologyUK]

If any of you have difficulties with multiple Xbox One's connecting in the same house, an update has rolled out to the beta update users which allows you to set your xbox to use different port for each console (default is 3074). This will allow you to then manually port forward for each console. 

 

Hope this makes sense. 

[RILLA au]

If any of you have difficulties with multiple Xbox One's connecting in the same house, an update has rolled out to the beta update users which allows you to set your xbox to use different port for each console (default is 3074). This will allow you to then manually port forward for each console. 

 

Hope this makes sense. 

still doesn't help with games using the same port. UPNP ftw when it comes to multiple consoles on the same LAN

[DanologyUK]

If any of you have difficulties with multiple Xbox One's connecting in the same house, an update has rolled out to the beta update users which allows you to set your xbox to use different port for each console (default is 3074). This will allow you to then manually port forward for each console. 

 

Hope this makes sense. 

 

Here are the Microsoft notes about the change. 

 

Some folks in Preview have already noticed a few of these changes in the most recent update that went out to Preview Alpha yesterday, and I wanted to highlight them here:

 

Alternate multiplayer port selection: Under Network settings, Advanced settings there's a new button labeled Alternate port selection. For home networks where UPnP is problematic or unavailable and where multiple Xbox consoles are present, customers can now select an alternate port for multiplayer and chat to use. The default port for Xbox multiplayer and chat is UDP 3074, and when working around NAT issues you can set up either port forwarding or port triggering for this port & protocol to open up the NAT type for a single console. However, this option is only available to one console at a time if all consoles are using UDP 3074. With this new option, you can select a different UDP port from a drop down menu for each console so that you can setup port forwarding rules for each console on your home network. When the console binds to the new port, it will also attempt to port map via UPnP on this new port in case the UPnP issues with the home router are intermittent.

 

Test NAT type: Under Network settings there's a new button labeled Test NAT type. If you are troubleshooting NAT issues with your router and make changes such as enabling UPnP, configuring port forwarding, port triggering, or DMZ settings, you can now click this button to have the console re-run the NAT test and update the page with the new result if the NAT type has changed. A few important notes here:

Several routers that we've tested will require that the router be rebooted in order for any UPnP or NAT rules to take effect. If you're not seeing the expected result after running the Test NAT type, you may want to power down the router and console, then power up the router and wait for it to come online, and then power up the console.

If your router has detected a Moderate NAT type and you re-run the NAT test, it will likely display that the NAT type is now Open. Because of how NAT types are detected, re-running NAT tests back-to-back on a Moderate NAT type will often result in the NAT being falsely detected as Open. You'll need to either reboot the router or wait a while for the router to flush stale NAT entries from memory to get an accurate result.

 

Some under-the-hood UPnP improvements: We've been improving and optimizing the UPnP port mapping process, and this release contains some further enhancements to make the port mapping process even more resilient and streamlined.