Hello
We have got a server, call it S1, running Windows Server 2012, and workstations running Windows 10 Enterprise 1909. People regularly need to access this server using the workstations. When people on workstations try to access this server, it initially works (i.e. they enter their credentials and then the "The identity of the remote computer cannot be verified ..." windowappears), but then the "remote desktop can't connect to the remote computer for one of these reasons" error comes up. It goes away when connecting again, but instead shows the following error (without the "The identity of the remote computer cannot be verified ..." screen):
The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
This has been occurring sporadically ever since the server was built, however in the past few days it has appeared on all of the workstations. A few workstations used by sysadmins can still access the server by remotely connecting to another server that is on the same network, then remoting to S1 on the other server, however this is not the case for the rest of the workstations in the room. I've tried pinging S1 and it's replying fine.
I have also checked out the following other solutions to this problem from similar forum posts :
- Replacing mstsc.exe and mstscax.dll - no computers on the network are running W10 build 1511, so can't get the files
- Registry - the only registry options in HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client are (Default) and PinConnectionBar - no RDGClientTransport
- "Connect and don't warn me" - option is greyed out, stuck on "warn me"
- Services - both the Remote Desktop Services and Remote Desktop Services UserMode Port Redirector are up and running.
I can't seem to figure out anything else about why this is happening.