NAT Strict - Seemingly Tried Everything

Based on the One reporting "Detailed NAT Information: Your network is behind a firewall (or not connected)" and getting the Teredo IP error, it seems that it is not able to fully/properly communicate with the Microsoft Teredo server, which assigns the Teredo
IP and probably also detects your detailed NAT information (that or another MS server does it). Since the test showed port 3544 UDP outbound is not blocked, I'm not sure why there would be a problem--it is possible but seems unlikely that traffic to that
particular MS server is being blocked. Normally, I would suspect double NAT to be the culprit, but that does not seem to be the case given your setup (is usually a problem with DSL, not cable). Can you try wiring the Xbox One directly to your modem, fully
power cycling both, then testing again?

 

Same result unfortunately. Maybe a factory reset on the X1? I can't be sure, but about 1.5 months ago my NAT was open, so maybe it has something to do with the recent X1 updates? Wish I had checked it more frequently to ensure when the issue started.

 

Just to be clear, even with the Xbox One directly wired to the modem, you are getting strict NAT and detailed info indicating it is behind a firewall? Did you confirm the Xbox actually had Internet connectivity from the modem?

I am thinking this is something on your ISP's end.

 

Yeah, it has Strict NAT and the same detailed info as when connected to the router. Yeah the XBox one had internet and could do everything it normally can. I've called ISP, but can call them again, just not sure what to tell them at this point since they
think it is on my end or microsoft's.

 

With my current router which is a tplink i found i couldnt open the nat by setting a static ip outside the dhcp by using the xbox settings app.

I had to use address reservation in the router settings and UPnP. The ip address settings in the settings app are set to automatic. There is no port forwarding or dmz settings set.

Currently my nat is open.

It does sometimes go strict due to the fact i also own a 360 but running the multiplayer test then holding both triggers and bumpers opens it again.

Just to add, using address reservation has been an essential part of getting the NAT open. The NAT would go strict if i didnt use it

 

But OP can't get open NAT even when the One is directly connected to the modem. This means it is not a router setting or NAT issue because there is no NAT when directly connected to the modem. The problem is either with the ISP or Xbox One (perhaps it
is stuck reporting your previous strict NAT--with it directly connected, try doing the advanced triggers+bumpers test multiple times to see if it forces it to pick up the change in your NAT status).

 

Ah ok i missed that part.

Arent you still supposed to login to your isp when connected directly to a modem?

Problem is there doesnt seem to be a login option in the network settings like there was on the 360 meaning that if you connect directly to a modem it cant connect. If there is a login option i cant find it.

With my ISP i have to set username and password in the routers ppoe wan settings to get connection.

Without login i get no connection

 

When I connect directly to the modem I can connect to live and do everything as normal. Just have to power cycle each.

 

Malacath, OP has cable Internet, not DSL. Logging in, PPPoE/PPPoA, etc. are for DSL. No login is required with cable Internet, which is one of the many reasons I prefer cable Internet over DSL. Authentication is done by the cable system checking the
cable modem's unique identifiers to make sure it is authorized to be on the network.

 

So, had my buddy who has an IT history come over and plug in his Xbox1 and his reads as OPEN NAT! What!? Lol. I guess a factory restore is in order...? Thoughts? Theories?

 

Also, no teredo IP errors or anything and BF4 and everything is working great on his console

 

That is odd. Was it directly connected to the modem or? I think there may be some issue with the Xbox not correctly detecting and updating NAT status when it changes (this may explain why some folks have luck by repeatedly running the advanced test--RB+LB+RT+LT--until
the status updates). Have you tried powering down the Xbox by holding power for 10 seconds or so then unplugging the Xbox One power cord for a few minutes and trying the test again?

 

It was connected to the router under the desired setup. We're wary of clearing his cache lest it then go into strict, although not logical, this whole situation has made us cautious.

 

Factory restore fixed it. Open NAT and no teredo error. I'll keep you guys updated if it changes, but chalking this up to the latest system update. I love how helpful you were GZA. Faith in internet forums and humanity restored. Faith in Xbox updates however...lol

 

Glad you got it worked out!