Unable to Connect to Hyper-V 2016 Remotely
-
@dustinb3403 said in Unable to Connect to Hyper-V 2016 Remotely:
@jaredbusch Should the correct response be "fix the firewall on the Hyper-V Manager side of things".
No, because that is a troubleshooting step. It could be a different cause.
-
@obsolesce said in Unable to Connect to Hyper-V 2016 Remotely:
@scottalanmiller said in Unable to Connect to Hyper-V 2016 Remotely:
Any ideas how to regain access to the box?
I bet it has to do with Windows Updates. Ensure both the host and machine you're trying to connect from are up to date... but first, make sure the
Hyper-V Virtual Machine Management
service is running. Also, try restarting the WS-Management service if that doesn't work. (if a reboot wasn't done or can't be done)Hyper-V is definitely up to date, that might be when it broke. I've tried several clients, would be surprised if they are not, but I'll definitely try that.
-
Not sure what fixed it. Found a fresh Windows 10 host. Made sure it was COMPLETELY updated. Installed the Hyper-V Tools fresh. Fixed a DNS entry for the server in question. Turned off the firewall on the Windows 10 client. And then it connected. Not sure which piece was the fix(es).
-
@scottalanmiller said in Unable to Connect to Hyper-V 2016 Remotely:
Not sure what fixed it. Found a fresh Windows 10 host. Made sure it was COMPLETELY updated. Installed the Hyper-V Tools fresh. Fixed a DNS entry for the server in question. Turned off the firewall on the Windows 10 client. And then it connected. Not sure which piece was the fix(es).
So you didn't test connecting between each change? How else would you be able to pinpoint the issue?
Turn the firewall back on and try and connect.
-
@dustinb3403 said in Unable to Connect to Hyper-V 2016 Remotely:
@scottalanmiller said in Unable to Connect to Hyper-V 2016 Remotely:
Not sure what fixed it. Found a fresh Windows 10 host. Made sure it was COMPLETELY updated. Installed the Hyper-V Tools fresh. Fixed a DNS entry for the server in question. Turned off the firewall on the Windows 10 client. And then it connected. Not sure which piece was the fix(es).
So you didn't test connecting between each change? How else would you be able to pinpoint the issue?
Turn the firewall back on and try and connect.
When experiencing the issue I had, it would continue to work once the firewall was back on, until reboot.
-
@obsolesce I'm going to agree with him on this. Windows updates screws everything up in our settings regularly and it can affect almost anything it seems.
-
@dustinb3403 said in Unable to Connect to Hyper-V 2016 Remotely:
@scottalanmiller said in Unable to Connect to Hyper-V 2016 Remotely:
Not sure what fixed it. Found a fresh Windows 10 host. Made sure it was COMPLETELY updated. Installed the Hyper-V Tools fresh. Fixed a DNS entry for the server in question. Turned off the firewall on the Windows 10 client. And then it connected. Not sure which piece was the fix(es).
So you didn't test connecting between each change? How else would you be able to pinpoint the issue?
Turn the firewall back on and try and connect.
Not by the end, got on a new box and was trying to be as pristine as possible.
-
@scottalanmiller said in Unable to Connect to Hyper-V 2016 Remotely:
Hyper-V 2016 14393 (Latest Build)
We can reach the server via RDP, but that is all. No cools like vmconnect, WAC, or the Hyper-V manager can talk to the server, so we can't see the consoles of running VMs (or do much of anything.) We can manage the machine via PowerShell, but nothing else.
We get some RPC errors, but we have restarted the RPC service, and we've disabled and re-enabled the Remote Management system in Hyper-V, but to no effect.
Any ideas how to regain access to the box?
Restart-Service "Hyper-V Virtual Machine Management" -Force
-
@scottalanmiller said in Unable to Connect to Hyper-V 2016 Remotely:
Not sure what fixed it. Found a fresh Windows 10 host. Made sure it was COMPLETELY updated. Installed the Hyper-V Tools fresh. Fixed a DNS entry for the server in question. Turned off the firewall on the Windows 10 client. And then it connected. Not sure which piece was the fix(es).
Watch for an updated version of RSAT (Remote Server Administration Tools) as some updates may tweak things that require the RSAT tools to be updated.
-
I gave up on using hyperv manager and used Windows Admin Center instead.
-
@hobbit666 said in Unable to Connect to Hyper-V 2016 Remotely:
I gave up on using hyperv manager and used Windows Admin Center instead.
Not sure if I had mentioned it, but that's what we normally used but it broke first. Then we went to Hyper-V manager and it was broken as well. WAC is our normal tool for this stuff.