Hi Edit,
I am not sure if this will help you, but, just as a thought....
There are 2 things I can think of off the top of my head.
- You haven't mentioned if you are in an Active Directory domain environment. If one server is in the Domain and another is not then, that MAY explain the difference.
- Not in a Domain and/or using certificates.
- One server has a certificate from a trusted CA and the other hasn't OR...
- both servers are using their default self-signed RDP certificate, and, at some stage, someone has chosen to 'trust' the RDP certificate from the server that isn't throwing the message but has not yet trusted the certificate from the other server which is throwing the message
Do you get a certificate warning/message prior to or after this message?
HTH