Start Pxe Over Ipv4 Hyper-v Windows 10
Violetta Wagganer
After upgrading from Windows 10 1803 to 1809 I am no longer able to connect to any running VM's.
I am able to start the VM and see it running in the preview screen but when attempting to connect to the VM, I receive "Cannot connect to the virtual machine. Try to connect again. If the problem persists, contact your system administrator. Would you like to try connecting again?"
Since 1809 upgrade on my Win 10 Pro system when I launch Hyper-V manager and try to connect to my server it site there for like 1-2 min then put ups an error telling me to check the server. What crap every semi-annual update has broken some aspect of RSAT or remote management tools, how hard is this MS! I understand why people stick with LTSB versions now , far more stability!
@hdtvguykeiththanks for your post! Maybe we're missing something idk... Microsoft must have the same issues internally. Since my original reply, I have rebuilt machine and now am running latest insider builds on host and on both VMs with the same outcome. Have noticed though if not using enhanced sessions, sometimes can connect to VMs through console, otherwise just RDP into their ip.
I ended up performing a clean install of 1809 and it was working for a few weeks on my existing VM's. All of a sudden, I hit the exact same issue again.
I migrated away from Hyper-V to VMware workstation in the end.
Glad to see they identified the issue and will be fixed in a future release.
Just upgraded my Workstation to 1903, and now i cant connect to my Hyper-V server that was hosting all my VMs. I get an error say to check the server to make sure the basic services are running and that WinRM cant complete the operation. Nothing has changed, beside me moving to 1903.
Has anyone figure out what needs to be done to get a connection back. I really don't want to RDP to each one of my VMs that i have created for testing, as i have 5 other people that use this too.
I did come across an article with a registry fix, changing the ListenerPort dword from 2179 to 21791 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization. After stopping/started the hyper-v windows services I was able to connect to the virtual machines as normal.
You can run netsh int ipv4 set dynamic tcp start=51001 num=5000 which will reset the dynamic port range to start at 51001 which is a range applications typically have no port reservations to bind to.
Followed by running reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f which disables the HNS (Windows Container Host Networking Service) port exclusion behaviour.
A few months back when I began doing a bunch of linux automation and was waiting for my company ordered machine to arrive, I was mostly working from my personal windows laptop and was fairly invested in Hyper-V as my hypervisor of choice. Both at work and at home I work off of a wireless connection. This has not been a problem running windows guests especially since windows 8.1. There were a few rough edges on windows 8 but those seem to have been smoothed over in 8.1.
So my first go of an Ubuntu 12.04 guest installed just fine and I could interact with it via a hyper-v console but I could not SSH to the guest. It was not being assigned an IP accessible from the outside.
This, in short, is the solution. In other words, do not use an external switch. When you are on wifi, hyper-v will create a bridge between your wifi adapter and the adapter it creates for the external switch. I wont get into the details (because I do not know them), but the Ubuntu guest cannot obtain an IP from DHCP under this setup.
The only residual fallout from this setup, and you may experience this regardless is that sometimes moving to a different network may require resetting one or more of your adapters. For example if you transport your laptop from a work network to a home network. Again, you may experience this even without this setup or you may not experience it at all. Its been rather hit and miss for me but I seem to bump into this more often under this setup.
I'm Matt Wrock with over fifteen years of experience architecting scalable, distributed, high traffic web applications as well as environment and deployment automation. I currently live in Woodinville, WA with my wife, two daughters, four dogs and two cats. Until just recently I worked for Microsoft as a Sr. Software Engineer and now work for Chef Software focusing on Windows. I'm also project founder of and a committer to
d3342ee215