Teredo is stuck on "Restricted (port)"

My nat type changed to restricted port but nothing on my router is blocked my parameters got updated Teredo Parameters
---------------------------------------------
Type : enterpriseclient (Group Policy)
Server Name : xxxxxxxxxxxxxxxxxxx (Group Policy)
Client Refresh Interval : 30 seconds (Group Policy)
Client Port : unspecified (Group Policy)
State : qualified
Client Type : teredo client
Network : managed
NAT : restricted (port)
NAT Special Behaviour : UPNP: Yes, PortPreserving: Yes
Local Mapping : xxxxxxxxxxxxxxxxxxxxxxx
External NAT Mapping : xxxxxxxxxxxxxxxxx

try this open the windows command as administrator and type: netsh interface teredo set state client teredo.remlab.net this ist a puclic german teredo server thats worked für me

sadly, not successfully

client port : unspecified

network: unmanaged

NAT: Restricted (port)

NAT Special Behaviour: UPNP: no, PortPerserving: Yes

sure no problem, I will type it in points:

- I have tried windows default teredo settings.

- I opened the required ports through UPnP and DMZ on my router.

- I reset the router to the factory settings.

- I have tried windows default teredo settings (again)

- I opened the required ports through UPnP and DMZ on my router (again).

- I used fixed internal IP address.

- I changed teredo settings (ex: refresh rate, port, server name, status). (tried it through the powershell and Group Policy)

- I disable my PC's firewall, then I uninstalled it.

- I tried the previous steps again (without the firewall)

- I switched teredo status from Client to Enterprise (and vice versa)

- I checked the registry for anything the could be blocking teredo (through the online troubleshooting guide).

It sometimes connects and like I have mentioned before but with the very same settings it does connect the next time and the NAT status turns from Cone to Restricted (sometimes symmetrical).

My router is enabling the port(s), yet teredo shows it is restricted (and no my ISP is not blocking these ports).

Here is an image of what is happening right now (Top is the Router's readings of the allowed ports):

sure no problem, I will type it in points:

- I have tried windows default teredo settings.

- I opened the required ports through UPnP and DMZ on my router.

- I reset the router to the factory settings.

- I have tried windows default teredo settings (again)

- I opened the required ports through UPnP and DMZ on my router (again).

- I used fixed internal IP address.

- I changed teredo settings (ex: refresh rate, port, server name, status). (tried it through the powershell and Group Policy)

- I disable my PC's firewall, then I uninstalled it.

- I tried the previous steps again (without the firewall)

- I switched teredo status from Client to Enterprise (and vice versa)

- I checked the registry for anything the could be blocking teredo (through the online troubleshooting guide).

It sometimes connects and like I have mentioned before but with the very same settings it does connect the next time and the NAT status turns from Cone to Restricted (sometimes symmetrical).

My router is enabling the port(s), yet teredo shows it is restricted (and no my ISP is not blocking these ports).

Here is an image of what is happening right now (Top is the Router's readings of the allowed ports):

And now this:





What was changed: NAT status (from Restricted to Symmetric)

Hey, GJB. Seems like what the students are likely running into is how the University gateway/firewall is setup for handling unsolicited, inbound connectivity for P2P communications, and possibly consoles failing to acquire a Teredo address. Party Chat and
many multiplayer titles use a P2P mesh topology for network communications, which requires open inbound communications to the Xbox One console. Teredo is used for a few things here, such as detecting the public IP/port of the console if it's behind a NAT (sounds
like it doesn't apply here), detecting what type of inbound/outbound connectivity is allowed to the console behind whatever network gear the console is traversing to reach the outside world, acting as an endpoint for bubble packets to hit, and securing network
communications between the console and its peers.

So first thing first, if any of the students are getting an error that their console can't obtain a Teredo address, that will block Party Chat and many multiplayer games. UDP 3544 outbound needs to be open, and the console will default to a source port of
UDP 3074 when targeting the Teredo server pool. If the console is getting a Teredo address, then next thing would be to see what Teredo is detecting as far as what inbound connectivity is allowed. If you go under Settings, and Network. The Open/Moderate/Strict
NAT detection will be present here. If you go to Test Multiplayer Connection on this page, it will re-detect the NAT type and run a few more tests. After the Multiplayer Test is run, and before selecting "Continue", press and release both triggers and both
bumpers on the controller at the same time. A more advanced test will run, and a more descriptive Teredo NAT type will show (IP Restricted, Port Restricted, Sequential Port Symmetric, etc.) What Teredo detects here will give us a good idea on next steps.