Windows DNS setttings remotely Tim Andersons ITWriting. Biometrics Fingerprint Recognition Pdf Printer here. This was an annoying. I tried to remote desktop into my Hyper V Server today and could not. The message 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. Patch Fr Agatha Christie on this page. Hmm. I typed net time myhypervboxand it was the same as the time on my desktop. A Google or two later, and I discovered that this message is caused by an incorrect DNS setting on the target computer. That made sense, since a DNS server died recently. I had changed the settings on the VMs but forgot to do it on the Hyper V host. Thank you Microsoft for a misleading error message. Of course my Hyper V server has no screen attached. So how to change the DNS settingUmm, not by remote desktop. I fiddled with netsh for a bit. This looks promising, but it was not playing ball. I tried to list the interfaces and it gave an error saying it could not do so when remote access is not running. Further, I have two network cards in this machine, and Hyper V creates virtual interfaces, and I was not sure what the correct network interface name was. Next up was the registry editor. How to enable remote desktop in windows 10 home Can you remote desktop to windows10 home Remote desktop 10 home Where can I find Remote desktop connection on. I have three computers a new win 7 home premium and 2 win XP professional. I can ping all three of them. Archived from groups microsoft. I have a Windows 2003 Standard Edition server which I prefer to remotely administer. JupQNB6&timestamp=1440183457' alt='Vista Remote Desktop Can T Connect' title='Vista Remote Desktop Can T Connect' />Thanks DragonRider. I was thinking. I did observe that I can execute the Remote Desktop application Start Run mstsc and remotely connect to. Run Regedit, choose File Connect Network Registry. That worked. I went to HKEYLOCALMACHINESYSTEMCurrent. Control. SetServicestcpipParametersInterfaces. This lists the network interfaces as GUIDs. I went through them one by one, and in the two cases where the Name. Server entry was set to the dead server, I changed it to the new one. There is also an entry for Name. Server in the top level Parameters key but this was blank and I left it alone. If you want to know what all these keys do, there is a guide here. I rebooted the machine, remotely of course shutdown m myhypervbox rand when it restarted remote desktop worked again. Related posts Trying out Remote Desktop to a Microsoft Azure virtual machine. New in Windows 7 RC Windows XP Mode, Remote Media Streaming. Changing the motherboard under Windows 7. Changing the motherboard or storage controller underneath Windows XP and Vista. USB devices and Hyper V remote client yes, host no.