AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Ping transmit failed general failure2/17/2024 : Tuesday, Octo11:58:20 AMĭefault Gateway. (not sure how to keep the original formatting)ĮEthernet adapter vEthernet (HyperV Public):ĭescription. Here is some information from a PC, Hyper-V and a VM to compare It seems like Hyper-V is not getting or passing on the IPV6 DHCP information or Neighborhood discovery information. ![]() ![]() If I try to ping the IPV6 DNS server from the PC's it works.įrom Hyper-V and the VM's I get: PING: Transmit failed. They are also missing a 'Temporary IPV6 address' The Hyper-V VM's are all missing an IPV6 address but have the correct IPV6 DNS address It is also missing a 'Temporary IPV6 address' Note that I haven't set any IPV6 addresses manually - this somehow came from the router. The Hyper-V server has a valid IPV6 address from Starlink and valid IPV6 DNS address from Starlink but is missing the IPV6 gateway address. My Hyper-V system doesn't work for IPV6 (It works fine with IPV4) On all machines (PC, Hyper-V, VM) IPV6 is enabled and IPV6 DHCP is enabled. I have both statically addressed IPV4 and DHCP IPV4 PC's and they work as expected. ![]() My PC's all work correctly and can get out to the internet, both IPV4 and IPV6. I am connected to the Internet via an ASUS router attached to a Starlink dish. I have multiple PC's and a Hyper-V 2016 standalone server with several Windows 10 VM's I'm trying to get IPV6 working on my network and having problems with Hyper-V.
0 Comments
Read More
Leave a Reply. |