Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

does someone faced error "The RPC server is unavailable" during connecting to Disk management MMC console to Hyper-V Server R2? Servers are in the same AD domain and MMC console is enabled on Hyper-V.


share|improve this question
Both source and destination are 2008 R2? – Kara Marfia Aug 28 '09 at 14:28
Yes. Both R2. I can access firewall settings, server management snapin but Disk Management returns mentioned error. – GrZeCh Aug 28 '09 at 18:49
up vote 14 down vote accepted

You need to change the Firewall rules on both machines (NOT only the Hyper-V Server)

Run this command on both machines:

netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

share|improve this answer
GREAT. Updating firewall on both sides was the case. Thank you – GrZeCh Aug 29 '09 at 11:35
I'm still getting this. It was succesfull on my physical machine, but when I executed this command on my Virtual Client, it said: "No rules matched the given criteria". That's translated, since the machine runs Dutch language. – KdgDev Oct 1 '10 at 10:14

For errors "RPC Server is unavailable" when trying to use Disk Management MMC or Server Manager MMC or Computer Management MMC to connect to a Windows Hyper-V (Hyper V) Core Server, please note the following: 1. Enabling "Remote Volume Management" needs to be done on both machines... the Core Hyper V Server and the client machine: On the client machine (Windows 7 and Windows 8 ... XP is no longer supported... lol ;), "netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes" will run smoothly.

On the Windows Hyper-V (hyper V) Core Server (in my case I am on Server 2012 R2), I was not eble to run the netsh command. I was able to enable "Remote Volume Management" by using the GUI tool "Corefig for Windows Server 2012 Core and Hyper-V Server 2012"... *downloadable from Version 1.1.1 was stable enough. Good luck!

share|improve this answer

Be aware that Windows is using dynamic port allocation for some services e.g. Disk management. Meaning Microsoft finally uses one of these ports 49152 - 65535.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.