: VMware Virtual Ethernet Adapter for VMnet8 : fec0:0:0:ffff::1%1Įthernet adapter VMware Network Adapter VMnet8:ĭescription. : VMware Virtual Ethernet Adapter for VMnet1

: EnabledĬonnection-specific DNS Suffix Search List : Įthernet adapter VMware Network Adapter VMnet1:ĭescription. When I try to remove it with route DEL, Windows says 'OK' but does not remove it. Why is Win10 adding the gateway fe80::10 and how can I get rid of it? It seems to be causing the problem. On the Windows 10 machine access to the ipv6 net works if I manually add a static default route (which would have a smaller metric.) On Windows 8, the client works fine with routing like: On Windows 10, the routing table looks like: After extensive troubleshooting it appears to be something to do with the default gateway, especially when I compare routing tables on Windows 8 clients (which can access the IPv6 Internet). When a Windows 10 client was added to the LAN, it refuses to work on ipv6. A delegated /64 is in use on the LAN and has ran without care and feeding for a long time. NetBIOS over Tcpip.I have been running a he.net tunnel on a Linux machine as the gateway for a small network for a few years. I have checked the ipconfig for the DC and it gives me as the following I am using windows server 2008 R2 on the direct access server and one of the DCs we have which handles dns None of the internal DNS servers that DirectAccess client computers use for name resolution is responding When go to monitoring I found all healthy except DNS with the error I am implemented direct access and almost finished configuration

Tunnel adapter isatap windows 10