none
ISATAP Adapter missing in VM, how to add RRS feed

  • Question

  • We are requiring ISATAP on a 2019 Direct Access (DA) server. Despite we have enabled ISATAP at OS level (set-NetIsatapConfiguration enabled), the ISATAP Interface has no IPv6 address.

    Have then compared the DA server to another similar DA server running on VMware. In the device manager, the VM running on Hyper-V has no ISATAP adapters, as shown in the printscreen of the VMWare VM below.

    How do we get ISATAP support on Hyper-V? Thank you in advance for any help.

    Franz

    Thursday, March 12, 2020 10:10 AM

Answers

  • Hi ,

    I have also checked in my lab. As Leon said, we don't see the ISATAP adapter in the device manager on the server 2019 VM.

    Please see the blow screenshot:

    It seems this behavior is more related with server OS instead of hyper-v.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   


    Friday, March 13, 2020 4:28 AM

All replies

  • Hi,

    You should be able to verify if your ISATAP adapter is ok by running the following command:

    Get-NetIPInterface

    Example output:


    Then check the interfaceindex of your ISATAP adapter and run the following command:

    Get-NetIPAddress -InterfaceIndex <your interface index number> -AddressFamily IPv6

    Example output:


    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 12, 2020 11:32 AM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:

    Thursday, March 12, 2020 12:59 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:

    Thursday, March 12, 2020 12:59 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:

    Thursday, March 12, 2020 12:59 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:

    Thursday, March 12, 2020 12:59 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:

    Thursday, March 12, 2020 12:59 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:

    Thursday, March 12, 2020 12:59 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:

    Thursday, March 12, 2020 12:59 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:00 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:00 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:00 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:00 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:00 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:00 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:00 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:01 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thursday, March 12, 2020 1:01 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server

    Thursday, March 12, 2020 1:02 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server

    Thursday, March 12, 2020 1:02 PM
  • Hi Leon,

    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server:


    Thank you for your feedback. Both Direct Access Servers are showing to ISATAP adapters. But the ISATAP adapter in the working server has a valid IPv6 configuration, the adapter in the not working server has only a local link state address.

    Good server:

    Bad server

    Thursday, March 12, 2020 1:02 PM
  • Hi Leon,

    Thank you for your feedback. The working and the non-working server have two ISATAP interfaces. But only the working server has a valid IPv6 configuration:

    Working server:

    PS C:\Windows\system32> Get-NetIPInterface


    ifIndex InterfaceAlias                  AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     ConnectionState PolicyStore
    ------- --------------                  ------------- ------------ --------------- ----     --------------- -----------
    16      DMZ Netzwerk                    IPv6                  1500               5 Enabled  Connected       ActiveStore
    15      Internes Netzwerk               IPv6                  1500               5 Enabled  Connected       ActiveStore
    17      IPHTTPSInterface                IPv6                  1280              50 Enabled  Connected       ActiveStore
    14      6TO4 Adapter                    IPv6                  1280              50 Enabled  Disconnected    ActiveStore
    13      isatap.{94FDD992-702D-4078-9... IPv6                  1280               5 Enabled  Connected       ActiveStore
    12      isatap.domain.local            IPv6                  1280               5 Enabled  Connected       ActiveStore
    1       Loopback Pseudo-Interface 1     IPv6            4294967295              50 Disabled Connected       ActiveStore
    16      DMZ Netzwerk                    IPv4                  1500               5 Disabled Connected       ActiveStore
    15      Internes Netzwerk               IPv4                  1500               5 Disabled Connected       ActiveStore
    1       Loopback Pseudo-Interface 1     IPv4            4294967295              50 Disabled Connected       ActiveStore


    PS C:\Windows\system32> Get-NetIPAddress -InterfaceIndex 12 -AddressFamily IPv6


    IPAddress         : fe80::5efe:192.168.118.15%12
    InterfaceIndex    : 12
    InterfaceAlias    : isatap.domain.local
    AddressFamily     : IPv6
    Type              : Unicast
    PrefixLength      : 128
    PrefixOrigin      : WellKnown
    SuffixOrigin      : Link
    AddressState      : Preferred
    ValidLifetime     : Infinite ([TimeSpan]::MaxValue)
    PreferredLifetime : Infinite ([TimeSpan]::MaxValue)
    SkipAsSource      : False
    PolicyStore       : ActiveStore

    IPAddress         : fd94:b008:c806:1:0:5efe:192.168.118.15
    InterfaceIndex    : 12
    InterfaceAlias    : isatap.domain.local
    AddressFamily     : IPv6
    Type              : Unicast
    PrefixLength      : 64
    PrefixOrigin      : RouterAdvertisement
    SuffixOrigin      : Link
    AddressState      : Preferred
    ValidLifetime     : Infinite ([TimeSpan]::MaxValue)
    PreferredLifetime : Infinite ([TimeSpan]::MaxValue)
    SkipAsSource      : False
    PolicyStore       : ActiveStore

    IPAddress         : fd94:b008:c806:1::
    InterfaceIndex    : 12
    InterfaceAlias    : isatap.domain.local
    AddressFamily     : IPv6
    Type              : Anycast
    PrefixLength      : 0
    PrefixOrigin      : Other
    SuffixOrigin      : Other
    AddressState      : Preferred
    ValidLifetime     : Infinite ([TimeSpan]::MaxValue)
    PreferredLifetime : Infinite ([TimeSpan]::MaxValue)
    SkipAsSource      : False
    PolicyStore       : ActiveStore

    Not working server:

    PS C:\Windows\system32> Get-NetIPInterface

    ifIndex InterfaceAlias                  AddressFamily NlMtu(Bytes) InterfaceMetric Dhcp     ConnectionState PolicyStore
    ------- --------------                  ------------- ------------ --------------- ----     --------------- -----------
    18      isatap.{D90140F2-E60E-43F6-A... IPv6                  1280              20 Enabled  Connected       ActiveStore
    6       isatap.domain.local         IPv6                  1280              20 Enabled  Connected       ActiveStore
    16      DMZ_vlan165                     IPv6                  1500              15 Enabled  Connected       ActiveStore
    2       6to4 Adapter                    IPv6                  1280              75 Disabled Disconnected    ActiveStore
    13      LAN_vlan164                     IPv6                  1500              15 Enabled  Connected       ActiveStore
    4       Microsoft IP-HTTPS Platform ... IPv6                  1280              75 Enabled  Connected       ActiveStore
    1       Loopback Pseudo-Interface 1     IPv6            4294967295              75 Disabled Connected       ActiveStore
    16      DMZ_vlan165                     IPv4                  1500              15 Disabled Connected       ActiveStore
    13      LAN_vlan164                     IPv4                  1500              15 Disabled Connected       ActiveStore
    1       Loopback Pseudo-Interface 1     IPv4            4294967295              75 Disabled Connected       ActiveStore


    PS C:\Windows\system32> Get-NetIPAddress -InterfaceIndex 6 -AddressFamily IPv6


    IPAddress         : fe80::5efe:192.168.164.15%6
    InterfaceIndex    : 6
    InterfaceAlias    : isatap.domain.local
    AddressFamily     : IPv6
    Type              : Unicast
    PrefixLength      : 128
    PrefixOrigin      : WellKnown
    SuffixOrigin      : Link
    AddressState      : Preferred
    ValidLifetime     : Infinite ([TimeSpan]::MaxValue)
    PreferredLifetime : Infinite ([TimeSpan]::MaxValue)
    SkipAsSource      : False
    PolicyStore       : ActiveStore



    PS C:\Windows\system32>



    • Edited by FranzSchenk Thursday, March 12, 2020 1:09 PM
    Thursday, March 12, 2020 1:09 PM
  • I don't think this is a Hyper-V issue, rather something else, you'll find more ISATAP experts over here:

    https://social.technet.microsoft.com/Forums/en-US/home?forum=ipv6


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 12, 2020 1:20 PM
  • I don't think this is a Hyper-V issue, rather something else, you'll find more ISATAP experts over here:

    https://social.technet.microsoft.com/Forums/en-US/home?forum=ipv6


    Blog: https://thesystemcenterblog.com LinkedIn:

    I just see that I have the two ISATAP adapters in the device manger of a VM running on VMware (see. picture in initial post), and they are missing on a same VM runnunig on Hyper-V
    Thursday, March 12, 2020 1:44 PM
  • You can double check that the ISATAP adapter isn't hidden in the Device Manager:

    1. Open the Device Manager.

    2. Click “View” and click “Show hidden devices”.

    3. Expand “Network adapters”.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 12, 2020 2:09 PM
  • You can double check that the ISATAP adapter isn't hidden in the Device Manager:

    1. Open the Device Manager.

    2. Click “View” and click “Show hidden devices”.

    3. Expand “Network adapters”.


    Blog: https://thesystemcenterblog.com LinkedIn:

    That's exactely what I did. There are no ISATAP adapters on the Hyper-V VM, no visible and no hidden ones
    Thursday, March 12, 2020 2:24 PM
  • Are the servers fully identical on VMware and Hyper-V?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 12, 2020 2:27 PM
  • Are the servers fully identical on VMware and Hyper-V?

    Blog: https://thesystemcenterblog.com LinkedIn:

    The same configuration as Direct Access server. But one is 2016, the other 2019. But even when they are not identical: The question is how to get a working ISATAP adapter on the not working server.
    Thursday, March 12, 2020 2:38 PM
  • I don't see the ISATAP adapter on my guest Server 2019 either in the Device Manager, but on the Server 2016 I do see it in the Device Manager, but both display nicely when running the PowerShell cmdlets, don't see that it's related to Hyper-V, might be something in Windows Server itself.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 12, 2020 2:44 PM
  • Hi ,

    I have also checked in my lab. As Leon said, we don't see the ISATAP adapter in the device manager on the server 2019 VM.

    Please see the blow screenshot:

    It seems this behavior is more related with server OS instead of hyper-v.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   


    Friday, March 13, 2020 4:28 AM
  • Thank you all for your feedback.

    So, the ISATAP adapter is not visible in device manager in server 2019, what seems to be "normal", but we have no explications or MS documentation for that. But our main problem is not solved at all: The ISATAP adapter is not only invisible in device manager, it does not work at all in server 2019.

    But I will post the question in the IPv6 forum, like Leon suggested.

    best regards,

    Franz

    Friday, March 13, 2020 8:22 AM
  • Hi ,

    Thanks for your understanding.

    Please mark the useful reply as answer to end this thread up.

    If there is anything we can do for you, please feel free to let us know.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Friday, March 13, 2020 8:25 AM