I'm having a few problems with a Hyper-V Host that I'm unable to remote desktop to a few days after a reboot.
I get the following error when trying to RDP.
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, then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer.
I've checked the following.
- I can RDP to the Hosts VM's without issue
- Checked the system time & time zone against my laptop, and against the domain controller
- It's using the correct DNS servers
- I cant connect using the hostname or the fully qualified domain name [FQDN], but I can connect directly via it's IP address
- The automated backups on the server are showing RPC call failures to the host VM's when trying to backup specific directories
- I cannot connect from the Host through Hyper-V directly to the VM's running on the server
- I've reset the computer account through Active Directory Users and Computers. No change.
When attempting to run the powershell command "Test-ComputerSecureChannel - Repair"
Test-ComputerSecureChannel : Cannot reset the secure channel password for the computer account in the domain. Operation failed with the following exception: The server is not operational.
The server responds for a few days following a reboot. But after that then it fails to connect with the same symptoms. It's a production server, so rebooting it every day is not an option.
Does anyone have any ideas as to what might be causing such an issue?