For Azure VMs or Windows Servers, corrupted certificates are a common culprit. You can often resolve this by renaming the MachineKeys folder and rebooting to force Windows to generate a new certificate.
Ensure both machines have a steady internet connection. High latency or "dodgy" Wi-Fi can trigger this error even if the initial ping is successful. For Azure VMs or Windows Servers, corrupted certificates
(Windows Server 2012 R2 and older):
Fixing this issue requires understanding its origins. Systems administrators and remote workers generally face this combination of codes due to one of four main problems: For Azure VMs or Windows Servers