![\":wink:\"](\"https://emoji.discourse-cdn.com/twitter/wink.png?v=12\" "\\":wink:\\"")
<\/p>\n
I’ve got an RDP session to my house from work, and something happened (OK, I probably did it…) to my single VM on the host. I’m still getting used to Hyper-V, so I’m honestly not too surprised that I’d goof this up remotely… good thing it’s my own computer <\/p>\n
I had tried to change the network adapter to use the bridged connection on the host - something I’ve done a number of times, just not remotely. Now the host won’t let me connect to the management console, and I can’t use PowerShell to get the status of the VM (The destination host is not available)<\/p>\n
I can ping the host itself just fine, and DNS resolution finds it as well.<\/p>\n
Is there a way to issue a shutdown command to the VM in question or to force the network adapter on the VM (though the name of the VM escapes me at the moment, so if there’s a way to get that, probably a good idea…<\/p>\n
I already tried running a shutdown /i from my DC to see if I could get the host to restart, but I can’t get an uptime return on the Hyper-V server, so I’m not sure if it rebooted or not (or if that would even help… the VM in question is not<\/strong> set to auto start however)<\/p>\n RDP to the server doesn’t work either, so I’m guessing I’m just boned until I get home later. The server is running bare metal Hyper-V 2012 R2.<\/p>\n Help a guy out? No rush since it’s at home…<\/p>","upvoteCount":8,"answerCount":8,"datePublished":"2015-10-13T13:45:55.000Z","author":{"@type":"Person","name":"coloradogeek","url":"https://community.spiceworks.com/u/coloradogeek"},"acceptedAnswer":{"@type":"Answer","text":" Use PSExec and run the command “netsh firewall set opmode disable” against the Hyper-V box to shutdown the firewall.<\/p>\n I suspect<\/em> that when you changed the networking it reset the firewall.<\/p>\n Once that’s done you should have management and RDP back.<\/p>","upvoteCount":7,"datePublished":"2015-10-13T13:59:08.000Z","url":"https://community.spiceworks.com/t/whoops-hyper-v/443114/4","author":{"@type":"Person","name":"Gary-D-Williams","url":"https://community.spiceworks.com/u/Gary-D-Williams"}},"suggestedAnswer":[{"@type":"Answer","text":" I’ve got an RDP session to my house from work, and something happened (OK, I probably did it…) to my single VM on the host. I’m still getting used to Hyper-V, so I’m honestly not too surprised that I’d goof this up remotely… good thing it’s my own computer I had tried to change the network adapter to use the bridged connection on the host - something I’ve done a number of times, just not remotely. Now the host won’t let me connect to the management console, and I can’t use PowerShell to get the status of the VM (The destination host is not available)<\/p>\n I can ping the host itself just fine, and DNS resolution finds it as well.<\/p>\n Is there a way to issue a shutdown command to the VM in question or to force the network adapter on the VM (though the name of the VM escapes me at the moment, so if there’s a way to get that, probably a good idea…<\/p>\n I already tried running a shutdown /i from my DC to see if I could get the host to restart, but I can’t get an uptime return on the Hyper-V server, so I’m not sure if it rebooted or not (or if that would even help… the VM in question is not<\/strong> set to auto start however)<\/p>\n RDP to the server doesn’t work either, so I’m guessing I’m just boned until I get home later. The server is running bare metal Hyper-V 2012 R2.<\/p>\n Help a guy out? No rush since it’s at home…<\/p>","upvoteCount":8,"datePublished":"2015-10-13T13:45:55.000Z","url":"https://community.spiceworks.com/t/whoops-hyper-v/443114/1","author":{"@type":"Person","name":"coloradogeek","url":"https://community.spiceworks.com/u/coloradogeek"}},{"@type":"Answer","text":" Are you RDP’ing directly to the host or to something else?<\/p>\n Are the Hyper-V services running on the host?<\/p>","upvoteCount":0,"datePublished":"2015-10-13T13:50:12.000Z","url":"https://community.spiceworks.com/t/whoops-hyper-v/443114/2","author":{"@type":"Person","name":"Gary-D-Williams","url":"https://community.spiceworks.com/u/Gary-D-Williams"}},{"@type":"Answer","text":" Sorry, guess that should be clarified. I have two ESXi servers at home that run my normal network, so they’re unaffected. The RDP session that I’m using to connect home is running on one of those hosts, Hyper-V is just my lab server for the time being.<\/p>\n Not too clear on which cmdlet will let me see the status of the Hyper-V host. Keep in mind that I’m not<\/strong> connected to the host via RDP currently. RDP sessions won’t connect.<\/p>\n Edit - figured out the remote command to check uptime, and the host itself did reboot, but still having the same problem. d’oh.<\/p>\n Edit Edit - Well, now that’s funny. I initiated a restart via powershell to the Hyper-V host instead of my DC and just like the DC, it rebooted again just fine, but now I’m connecting to the host and can see the status of my VM. Go figure.<\/p>","upvoteCount":0,"datePublished":"2015-10-13T13:53:09.000Z","url":"https://community.spiceworks.com/t/whoops-hyper-v/443114/3","author":{"@type":"Person","name":"coloradogeek","url":"https://community.spiceworks.com/u/coloradogeek"}},{"@type":"Answer","text":" … and all is well. Network adapter is bridged properly in Hyper-V, and my guest VM is getting to the LAN. RDP / Hyper-V Manager is connecting just fine.<\/p>","upvoteCount":2,"datePublished":"2015-10-13T14:00:51.000Z","url":"https://community.spiceworks.com/t/whoops-hyper-v/443114/5","author":{"@type":"Person","name":"coloradogeek","url":"https://community.spiceworks.com/u/coloradogeek"}},{"@type":"Answer","text":" Good to hear, I’ve hit that before - why RDP Is blocked by default is beyond me!<\/p>","upvoteCount":3,"datePublished":"2015-10-13T14:01:56.000Z","url":"https://community.spiceworks.com/t/whoops-hyper-v/443114/6","author":{"@type":"Person","name":"Gary-D-Williams","url":"https://community.spiceworks.com/u/Gary-D-Williams"}},{"@type":"Answer","text":"<\/p>\n