![]() I'm not sure why Windows sometimes uses one, and sometimes the other. ![]() I named the machine a long hostname when it was first created, and Windows also created another one, truncated at 15 characters. I'm not sure if that was the problem (or the only problem), because I also have another one: a long hostname. If anyone has any insight as to why hyper-v requires ipv6 all of a sudden, I'd love to read about Thanks for the insight! I had just enabled an IPv6 network at home, and did not connect that to the Hyper-v problem. I noticed that 'server' returned an IPv4 response and 'server.local' returned an IPv6 response.Īfter modifying the power shell commands with every combination, the Hyper-V manager still wouldn't connect.įor kicks and grins, I tried connecting to 'server.local' and, why look at that, it comes right up. While pinging the hyper-v server, for no particular reason I pinged both 'server' and 'server.local'. It used to work fine but as of an update, many months ago, on every workstation it has stopped connecting to the server.Īfter reading through the MS Support document section related to my setup I decided to confirm connectivity, you know Layer-1 foils and all. I'm running Hyper-V manager on Win10 1607, connecting to Hyper-V Core 1607 without a domain, with a configured workgroup. ![]() Randomly this problem pops up on me after updates, and the same fix rarely seems to fix it. Hyper-V manager, connect to 'server.local' instead of 'server' ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |