{"id":470,"date":"2019-10-14T15:59:46","date_gmt":"2019-10-14T22:59:46","guid":{"rendered":"https:\/\/blog.iabsolute.com\/?p=470"},"modified":"2019-10-14T15:59:46","modified_gmt":"2019-10-14T22:59:46","slug":"hyper-v-error-access-denied-unable-to-establish-communication-between-hyper-v-and-client","status":"publish","type":"post","link":"https:\/\/blog.iabsolute.com\/?p=470","title":{"rendered":"Hyper-V Error \u2013 Access Denied. Unable to establish communication between Hyper-V and Client"},"content":{"rendered":"\n

While setting up a Hyper-V server for Wayne and Justin to work with some VMs to troubleshoot the SBS 2003 to 2008 replication error, we ran into a roadblock with getting the Hyper-V Manager connected to the Hyper-V Server 2008 box:<\/p>\n\n\n\n

\"image\"\/<\/a><\/figure>\n\n\n\n

Virtual Machines<\/strong><\/p>

Access denied. Unable to establish communication between \u2018Hyper-V Server\u2019 and \u2018Hyper-V Manager\u2019.<\/p><\/blockquote>\n\n\n\n

This is puzzling since the workstation has been connected to this particular Hyper-V server many times using other network profiles. The profile we created for the Microsoft folks was seemingly giving us the connection issue.<\/p>\n\n\n\n

The fix took a bit of searching to find and needed to be accomplished on the Windows Vista system where the Hyper-V Manager was installed:<\/p>\n\n\n\n

Close the Hyper-V Manage<\/p>\n\n\n\n

Click Start and type: %windir% [Enter]<\/strong>.<\/p>\n\n\n\n

A Windows Explorer window will open to the Windows directory.<\/p>\n\n\n\n

Type: dcomcnfg<\/strong> in the Search Windows <\/em>field at the top right hand of the Explorer window.<\/p>\n\n\n\n

You will see the following in your search results:<\/p>\n\n\n\n

\"image\"\/<\/a><\/figure>\n\n\n\n
  1. Right click on dcomcnfg <\/strong>and Run As Administrator<\/strong>.