Hyper-V Remote Management / Windows 10 client / Hyper-V Server 2012 R2

malikguy 21 Reputation points
2020-08-04T21:08:55.927+00:00

Hello, I've been struggling for a few days now with some crazy issues connecting to my 2012 R2 server via Hyper-V manager from Windows 10.

Setup:

  • Client is a Windows 10 Pro machine running v1903
  • Host is a Hyper-V 2012 R2 machine running v9600

Symptoms:

  • Hyper-V Manager is able to connect to the remote server successfully, however an "RPC" error is displayed when attempting to load the virtual machine list; All other functionality works including creating a new virtual machine
  • Additionally, all functionality of Server Manager works including Windows Powershell for the remote host

15508-image.png

Here's what I've done so far:

Something important to note:
I currently have another server running Windows 2016, v1607 with Hyper-V manager installed. Everything works completely fine from this server so I've also tried to mirror the settings of this machine on my Windows 10 client. This leads me to believe that everything is configured properly on the host as my Win 2016 client is able to connect and manage the host without any issues. I feel like there is something I am missing in my Windows 10 config, but at the same time, I feel like I've tried almost everything. I'm hoping there is an expert here that can shed some light.

Please let me know if there is any additional information that I can provide to help troubleshoot this problem.

Thanks in advance,
Malik

System Center Virtual Machine Manager
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,730 questions
0 comments No comments
{count} votes

Accepted answer
  1. Ian Xue 37,541 Reputation points Microsoft Vendor
    2020-08-05T10:10:26.337+00:00

    Hi,
    As you have enabled remote desktop, could you connect the host with RDP? Is the RPC service running?

    The process of an RPC client connecting to an RPC server can be broken down into four phases.
    Phase 1: Name Resolution: Name resolution is the act of resolving a name to an IP address. This normally takes two forms: NetBIOS Name Resolution or the more common DNS Name Resolution.

    Phase 2: TCP session establishment: TCP session establishment is the act of establishing a TCP connection between the RPC client and the RPC server. TCP sessions will be initiated by the RPC client via a TCP 3-way handshake with the RPC server.

    Phase 3: RPC Discovery: When a client wants to connect to the RPC server supplied by the application it will contact the computer that hosts the RPC Server and discover how to connectto the RPC Server.

    Phase 4: RPC Communication: RPC Communication is the act of making RPC requests to the application endpoint and receiving RPC responses from this application.
    Please refer to the troubleshooting guide here for more information
    https://social.technet.microsoft.com/wiki/contents/articles/4494.windows-server-troubleshooting-rpc-server-is-unavailable.aspx

    Also I find same issues here. Please check if they helps
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/2cc5ceae-55c0-4d2f-999f-fa3a590a7665/rpc-server-unavailable-unable-to-establish-communication-between-servers?forum=winserverhyperv
    https://community.spiceworks.com/topic/2007303-hyper-v-manager-rpc-server-unavailable-rdp-cannot-verify-the-identity

    Best Regards,
    Ian


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.