![]() ![]() This method is preferred as it requires only one registry entry and does not adversely affect existing DNS operation. Recently, Karsten Hentrup brought another effective workaround to my attention that also involves adding a registry entry on the ISATAP client machine. A while back I wrote about implementing some registry entries as a workaround for this issue on Windows 10. ![]() There is a known issue with Windows 10 and Windows Server 2016 DNS client that prevents manage out using ISATAP on these operating systems from working correctly. The DirectAccess client is reachable by its IPv6 address, however. Nevertheless, attempts to connect to the remote DirectAccess client by name fail. In addition, a route to the DirectAccess client’s IPv6 prefix is also present in the routing table. On a Windows 10 or Windows Server 2016 host configured to use ISATAP for DirectAccess manage out, the remote DirectAccess client resolves to an IPv6 address correctly. ![]() Connections to remote DirectAccess clients using Windows 7, Windows 8.x, Windows Server 2008/2008R2, and Windows Server 2012/2012R2 work without issue. Making these changes is no longer required after installing the Creators Update release of Windows 10.įor organizations that have implemented DirectAccess manage out using the Intrasite Automatic Tunnel Addressing Protocol (ISATAP), you may find connecting to remote DirectAccess clients by hostname using Windows 10 or Windows Server 2016 fails. Note: The issue described in this article has been resolved in Windows 10 version 1703 (Creators Update). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |