Teredo adaptor not obtaining IP address. HELP!

[NeoPrime]

I am at my wits end on this.

I have literally tried everything (barring a complete re-install of Windows) to try and get this working again, i say "again" because this USED to work, before i got a blue screen error and had to re-install windows a few days ago, before that on the original install it worked fine, but alas this is Windows so stuff decides to just stop working for no reason.

I was on the phone to tech support for 2 hours, these idiots didn't have a clue what they were talking about and kept passing me on to different departments who all said they couldn't help, or this issue was above them and had to pass me on to a different department, which usually meant talking to the department i had already spoken to before who said they could not help!

In the end the only solution i got from these so called "experts" was to pay them a ridiculous sum of money for them to remotely control my PC and fix it that way! Because, ya know, supporting your product like a normal company is far too much to ask for.

I've done EVERYTHING on this link, and none of it works (useful):
http://support.xbox.com/en-US/xbox-on-windows/social/troubleshoot-party-chat

When i open CMD and ask for it to show state on the Teredo driver under netsh interface it is only showing me the first 4 lines of the Teredo parameters.
Every thing i have seen online from people who claim to have this problem and fixed it indicates there should be more lines of text/info.

Also tried uninstalling the app itself then reinstalling, that didnt work.

Also tried power cycling the modem, tried disabling/re-enabling UPNP and that didnt work either.

Under device manager Microsoft Teredo networking adaptor is showing as working properly with up to date drivers. Teredo Pseudo interface adaptor is greyed out with a code 45 error saying it is not connected. Someone on Microsoft tech support (one of the varieties) had me install Microsoft 6 to 4 adaptor and that did nothing.

Everything looks like it should be working properly or as it should but Teredo cannot obtain an IP address.

Totally stumped and im certainly not going to pay Microsuck $100 to fix this as its something they should be willing to support for free.

Any help would be greatly appreciated and apologies if i sound a bit pissed off but thats because i am.

 

[NeoPrime]

Nobody have a clue?

 

[NeoPrime]

Thanks for all the help and advice everyone! -_-

 

[tsforrest]

I am not an expert in this particular caveat, so if you have any corrections or more information to add, please do so.

A single command from an elevated command prompt, "netsh int ter set state enterpriseclient", fixed my Teredo problem immediately, but make sure you have the same problem before you try this fix. If anyone else can share more information about the effects of this change, your input would be greatly appreciated. I still don't know if this change might adversely affect Hyper-V or any other Windows apps or components.

First, I have a Windows 10 laptop with Hyper-V installed. Evidently, Hyper-V and other virtual machine solutions make changes to your network configuration that can change your network type to identify as "managed", and this breaks Teredo. The Xbox app gave me the typical error with getting or registering an address for Teredo and provides a link to information to fix it. I tried everything in the linked Microsoft article, only to have nothing correct the problem. I finally stumbled onto a fix that helped someone else, who had another virtual machine solution installed (VirtualBox, I believe).

To see if you might have the same problem, run the following command at a command prompt with elevated privileges (run as Administrator) :

netsh interface teredo show state

If you have a similar problem as my own, you should receive a similar response (particularly the "client is in a managed network" error):

Teredo Parameters
---------------------------------------------
Type : client
Server Name : (Group Policy)
Client Refresh Interval : 30 seconds
Client Port : unspecified
State : offline
Error : client is in a managed network

To fix the problem, I just ran this single command, again from a command prompt with elevated privileges:

netsh int ter set state enterpriseclient

To verify that this fixed the issue, run the following command and verify that you get a similar response as below:

netsh interface teredo show state

Teredo Parameters
---------------------------------------------
Type : enterpriseclient
Server Name : (Group Policy)
Client Refresh Interval : 30 seconds
Client Port : unspecified
State : qualified
Client Type : teredo client
Network : managed
NAT : restricted
NAT Special Behaviour : UPNP: No, PortPreserving: Yes
Local Mapping : :60432
External NAT Mapping : :60432

Running that single command immediately corrected my Teredo problem, and the Xbox app no longer has any network problems. From what I have researched, this solution appears to work for Windows 7 and later. I don't know about Windows Vista, and I have only tried this on Windows 10, but the solution was originally for Windows 8/8.1. I wish I had gathered screenshots along the way. I wasn't planning to share all of this, but after spending so much time following so many complicated and time-consuming fixes only to discover that I just needed to run a single command, I decided to share my findings. Plus, I was just surprised this worked. Just to clarify... The laptop where I was having the Teredo problem is not a virtual machine, but it runs Hyper-V. I don't even have any virtual machines running on it at the time, but by installing Hyper-V, Windows made a lot of changes to the network configuration, adding virtual switches, virtual network adapters, and other stuff needed for Hyper-V. I imagine there are a lot of other people running Hyper-V and other VM solutions that may be struggling through the same issue as I just did. I believe that there are other scenarios where your network type can be changed to "a managed network", so this fix might apply if caused by something other than virtual machine software. I hope this helps keep someone from spending so much time trying all the other Teredo troubleshooting articles when there is such a quick and easy fix for this particular problem.

-TSForrest