Thursday, August 2, 2012

DirectAccess Client Connectivity - Teredo state



I ran into an issue to where I was unable to get connected to my DirectAccess server due to an issue with my DA Client IPv6 settings.  It's important to note that the teredo interface state should be "qualified" when it's functioning properly.


The default client type was set to "client".  Once I changed this to "enterpriseclient" everything started working.

C:\Windows\system32>netsh interface teredo show state
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


C:\Windows\system32>netsh int ter set state enterpriseclient
Ok.

C:\Windows\system32>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


This can be configured via GPO.




References


No comments:

Post a Comment