UPnP issues with Instant On mode

Are they in Energy Saver or Instant On mode? There's been some talk of issues with reestablishing UPnP sessions using Instant On mode.

Make sure both are in Energy Saver mode to start with.

After that, I'd blame the SuperHub2. A router with a compatible UPnP implementation shouldn't have an issue. May want to see if there's a firmware update available.

@KING CEREBRAL

Is that with instant on mode or energy saving mode?

The only time I ever get a strict NAT is when the console is in instant on mode.

Sometimes the NAT goes strict even though the IP address hasn't changed and the UPnP ports are being forwarded successfully. It's as though there is a glitch with instant on mode where it reports a strict NAT even though the ports are open.

So on my console there is definitely a fault with instant on mode.

@taidara

Yes, it seems energy mode seems to have fixed my uPNP issue. So it seems to be an issue with instant on and uPNP, however I think the issue is deeper rooted than that. If I disable uPNP and use static port forwards or DMZ, it should still work, but neither
of those seemed to have worked in my testing. <shrug>

To clarify, my NAT is currently open. I'll keep an eye out to see if it changes again.

Looks like there are issues with UPNP (especially D-Link) and the Xbox One when it is set to Instant On instead of Energy Saving mode. Ever since I changed mine from Instant On, my strict NAT issues went away. More details are in this very well written article
I found after searching on this issue for hours.forums.dlink.com/index.php

For some reason Instant On mode does not re-establish the UPnP port forward needed for the Xbox One. Energy Saver forces the console to re-establish the UPnP port forwards on boot-up.

The workarounds at the moment are to either statically assign the console an IP address and manually forward the ports required, or switch the console to Energy Saver mode.