Hi all,
We have had this same issue now with two of our Hyper-V host servers. The The symptoms are that when RDPing to the machine it asks for credentials, but then throws the error :
Remote Desktop Connection
---------------------------
Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem
occurs again, contact your network administrator or the owner of the remote computer.
---------------------------
When you try connecting via the Hyper-V manager, you get the error "RPC Server unavailable. Unable to establish communications bettween ..."
I can connect all of the other remote tools to it (event viewer, server manager, services) and can see the following:
In the event viewer there are a multitude of errors, I'm guessing all with the same root cause:
GPO
The processing of Group Policy failed. Windows could not resolve the user name. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
DCOM
DCOM was unable to communicate with the computer <DPM Backup server> using any of the configured protocols.
NETLOGON - Looks like the worst and maybe root cause?
This computer was not able to set up a secure session with a domain controller in domain D01 due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified
domain.
I can see that the service "Remote Procedure Call (RPC)" is started. Restarting it makes no difference. The RPC Locator service isnt started, but don't think this is an issue.
The DNS servers that are configured are the DCs and there are certainly fine for all our other servers and clients. The time is indeed out of sync, but I think this is more because it cannot establish a session with the DCs, which are the NTP servers. All of the guest machines are fine and running perfectly.
Like I said at the start, this has happened to another of our servers, suggesting that this is maybe a wider AD issue. In the case of the first server, a restart solved the symptoms. However, this second server is a bit more of a pain to restart and I want to sort out the root cause.
thanks in advance.