On my Windows 2012 (not R2) Standard server, I run several VMs. In the process of trying to shut them down, I consistently find an issue where insead of shutting down, the virtual machine get stuck saying "stopping"
In this helpful thread, people say that the problem is actually Routing and Remote Access (RRAS) being on the same server as the VMs. As such, I had luck restarting the RRAS service on the affected server. For me, this worked. I've tried the other suggestions of killing the process - to no avail.
https://social.msdn.microsoft.com/Forums/windowsserver/en-US/c55f8c8b-958e-449b-95fd-05834c806580/hyperv-vm-stuck-in-stopping-state
Showing posts with label RRAS. Show all posts
Showing posts with label RRAS. Show all posts
Tuesday, November 17, 2015
Thursday, August 12, 2010
my static packet filters nightmare
It's been a bit since I ran into this problem, so I may not be remembering all the details correctly. But here's the gist -
In the course of setting up an Exchange 2010 server, I lost all network connectivity to my 2008 R2 box. I know I broke it, but I wasn't sure how. The answer was that I had enabled static packet filters when trying to set up routing and remote access via Network Policy and Access Services. Static Packet Filters are basically an additional option for denying access to certain ports - but if you have a firewall, you're already using another option for that functionality. I was just clicking through the Network Policy and Access Services installation and hit YES on something I wasn't paying attention to.
To remove the problem once I had realized what I did, I did this (according to my notes):
I opened RRAS and went to IPv4 -> General. Right clicked on my NIC and clicked on inbound and outbound filters each and chose "receive all packets . . . " instead if "drop all packets . . . "
Though looking back at it a couple months later, I don't see the same options when I right click on my NIC in RRAS. But hopefully, someone else will find this helpful at some point.
In the course of setting up an Exchange 2010 server, I lost all network connectivity to my 2008 R2 box. I know I broke it, but I wasn't sure how. The answer was that I had enabled static packet filters when trying to set up routing and remote access via Network Policy and Access Services. Static Packet Filters are basically an additional option for denying access to certain ports - but if you have a firewall, you're already using another option for that functionality. I was just clicking through the Network Policy and Access Services installation and hit YES on something I wasn't paying attention to.
To remove the problem once I had realized what I did, I did this (according to my notes):
I opened RRAS and went to IPv4 -> General. Right clicked on my NIC and clicked on inbound and outbound filters each and chose "receive all packets . . . " instead if "drop all packets . . . "
Though looking back at it a couple months later, I don't see the same options when I right click on my NIC in RRAS. But hopefully, someone else will find this helpful at some point.
Sunday, June 27, 2010
adding VPN (RRAS) functionality to Server 2008 R2
If you're looking to add VPN/RRAS functionality to Windows 2008 R2, you won't find it called by either name. You need to add the role called Network Policy and Access Services (see screen show below).
Subscribe to:
Posts (Atom)