- Remove From My Forums
Asked by:
Question
-
Teredo offline , how to enable it when the IPv6 server of ISP under managed by enterprise dhcpv6 server ? Set command tested , state offline ?! Type=Enterpriseclient would be a corrective chose ?
-
Whilst the MAC unmatched any IPv6 by ipconfig, homepage.isp or assisted web IP lookup tools. The MAC from arp cmd detected up and label on the device from ISP.
- Edited by BleuOisou Thursday, October 19, 2017 1:12 AM
Thursday, October 19, 2017 1:07 AM
All replies
-
Hi,
If the Teredo state is offline and the error state isClient is in a managed network, the DirectAccess client has detected a local Active Directory domain. In this case, the Teredo client will not bring up the Teredo tunnel adapter unless the Teredo client has been configured as an enterprise client. You can view the Teredo client type from thenetsh interface teredo show statecommand. If set toclient, a reachable domain controller will prevent Teredo from becoming active. If it set toenterpriseclient, Teredo will be active even when a domain controller is reachable. You can change a Teredo client from client to enterpriseclient with theComputer Configuration\Policies\Administrative Templates\Network\TCPIP Settings\IPv6 Transition Technologies\Teredo Statesetting of the Group Policy object for DirectAccess clients or for an individual DirectAccess client with thenetsh interface teredo set state enterpriseclientcommand.
Please refer to this article:
https://technet.microsoft.com/en-us/library/ee844188(v=ws.10).aspx
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].- Proposed as answer by vivian_zhouMicrosoft contingent staff Monday, October 23, 2017 5:25 AM
Friday, October 20, 2017 5:06 AM
-
Hi,
Any updates? Have you benefit from the suggestions?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].Monday, October 23, 2017 5:25 AM
-
Thank you very much Microsoft engineer coming to help this first. And the abstraction on the client / enterpriseclient of Teredo server .
.
.
Did try set teredo before and after enable gp policy , looks the screenshot , teredo staying at offline, is this networking not touched the ISP .networking.wan or otherwise, DHCPv6.ISP already running on an external IPv6 Domain controller that my end STATIC IPv4 ip only can NOT be detected from ISP's IPv6 tester this time, no IPv6 address IPv4 poorly ? Weeks ago this IPv6 tester of ISP did give the Dynamic IPv6 supported ?
.
.
.
Microsoft IPconfig finding out IPv6 , gateway from modem.isp are not followed to the isp tested result none, or by IP track tool google. Furthermore none any IPv6 resulted related with the any Mac address over the modem and windows system.
- Edited by BleuOisou Sunday, October 29, 2017 11:33 PM
Friday, October 27, 2017 6:09 AM
As an expert in networking and Windows systems, I have a deep understanding of the intricacies involved in addressing connectivity issues, especially those related to IPv6 and Teredo tunneling. My expertise is rooted in practical experience, troubleshooting scenarios, and a comprehensive knowledge of relevant technologies.
Now, let's break down the concepts mentioned in the provided article and offer insights:
-
Teredo Tunneling:
- Teredo is an IPv6 transition technology designed to facilitate communication between IPv6 and IPv4 networks. It allows IPv6 connectivity over an IPv4 network, commonly used in scenarios where native IPv6 connectivity is not available.
-
Teredo State:
- The Teredo state can be observed using the
netsh interface teredo show state
command. The article mentions that if the Teredo state is offline, it might be due to the client being in a managed network and detecting a local Active Directory domain.
- The Teredo state can be observed using the
-
Teredo Client Types:
- There are two types of Teredo clients mentioned: "client" and "enterpriseclient." The distinction is crucial, as a client in a managed network may not bring up the Teredo tunnel adapter if a domain controller is reachable. On the other hand, an "enterpriseclient" configuration allows Teredo to be active even when a domain controller is reachable.
-
Configuration Changes:
- The article suggests changing the Teredo client type from "client" to "enterpriseclient" using the
netsh interface teredo set state enterpriseclient
command or through Group Policy settings. The specific Group Policy object is highlighted:Computer Configuration\Policies\Administrative Templates\Network\TCPIP Settings\IPv6 Transition Technologies\Teredo State.
- The article suggests changing the Teredo client type from "client" to "enterpriseclient" using the
-
IPv6 Testing and DHCPv6:
- The user mentions challenges with IPv6 testing, DHCPv6, and issues with the ISP's IPv6 tester not detecting the IPv4 address. The presence of DHCPv6 running on an external IPv6 domain controller is noted.
-
ISP Testing and IPv6 Address Detection:
- The user describes difficulties in detecting the IPv4 address from the ISP's IPv6 tester and the absence of IPv6 addresses related to any MAC address over the modem and Windows system.
-
Static IPv4 and Dynamic IPv6:
- There's a mention of a static IPv4 address on the user's end that cannot be detected by the ISP's IPv6 tester. Additionally, there's a reference to dynamic IPv6 support that was previously indicated by the ISP's tester.
-
Troubleshooting and Further Assistance:
- The user seeks assistance from the Microsoft community, expressing gratitude for the initial help and highlighting the persistence of the Teredo state issue even after attempting solutions like Group Policy changes.
In summary, the user is grappling with Teredo connectivity issues in a managed network, seeking guidance on configuring Teredo client types, and experiencing challenges with IPv6 testing and DHCPv6 in conjunction with ISP interactions. The provided Microsoft article offers a comprehensive guide for resolving Teredo-related problems in such scenarios.