Remote Desktop Connection Cerfificate Error.

Hi,

R. Cord here, Independent Expert. Hope you are doing well.

Let me suggest some first tips:

If your certificate is for a machine named "server.domain.com" and you access it by IP or simply by "server," you'll get the first error. Change your RDP connection to connect to the full FQDN and the first message should also go away.

Recommendation:

If problem happens after system upgrade to Windows 10 version 1803, please make sure that you also had KB4103721 installed on your Windows 10 1803:

https://support.microsoft.com/en-us/help/4103721

other fix:

Check if the server name in the Remote Desktop Connection settings is different from the name on the certificate, which is causing the error message to appear. To resolve this issue, try next steps:

Open the Remote Desktop Connection application on your computer.

Click on the "Show Options" button.

Click on the "Advanced" tab.

Under the "Server Authentication" section, select "Warn me if the remote computer does not support SSL" and "Do not connect if authentication fails".

Close the options window and try to connect again.

If the above steps do not resolve the issue, you can try the following:

Check that the computer name or IP address you are trying to connect to is correct.

Verify that the Remote Desktop Services is running on the remote computer.

Check that the firewall is not blocking the Remote Desktop Connection.

Verify that the date and time settings on both the local and remote computers are correct.

Try connecting to the remote computer using a different username or password.

Try creating a new Remote Desktop Connection shortcut with the correct settings.

Please let me know if you would like further assistance.

With best Regards,

R. Cord

Hello, I think I must have midlead you. I have a workgroup setup and I set up a Work Group in a Priviate Network and in fact this is in my home. I have 2 Dell devices one being an laptop and the other a deskop both systems are running Windows 10 Pro. My working knownledge of Certifiicates is realy none. I have had systems on Private networks over the years and had never run into this issue ever. To keep from wasting your time I am running Windows Ver. 21h2 of which I don't know if this is the issue or when I upgraded Windows Home to Windows Pro. Here is what is going.

When I ping the device name which is DESKTOP-XXXXXXX instead of seeing the IP address associated with the device I am

seeing the reply coming from the IPv6 address. However (note the IP addresses are fake in order to show what I am seeing) when I run nslookup on both name and IP address it resolves both. To me I've never had this issue.

As for the certificate and error I am seeing if you look at the snapshot above when the doing nslookup up

it is giving a server name of which this is the wireless Router for the network. Other than this the RDC errror "The server on the certificate is incorrect." I don't see any server mentioned anywhere and nothing noted in the Details.

This morning I got a new error "The Certificate is not from a Trusted Certifying Authority" But, in looking at the snapshot above this Certificate is in the Trusted Root Certification Authority so, I am at a loss.

Again I am not going to waste your time as this is my mess not yours. I appreciate your response. I know that the help out on the Internet I found to be toally worthless unless you work in a Domain and have servers.

Thanks for your time.

elwoodg20

Hi,

It looks like your devices are responding with their IPv6 addresses instead of their IPv4 addresses, which is causing the ping command to display the IPv6 address.

However, when you use nslookup to explicitly look up the name or IP address, it is able to resolve both the IPv4 and IPv6 addresses.

This behavior is not necessarily a problem, as both IPv4 and IPv6 can coexist on the same network. However, if you prefer to use IPv4 addresses for your workgroup setup, you can try disabling IPv6 on your devices. You can do this by going to the Control Panel, selecting Network and Sharing Center, clicking on your network connection, and then unchecking the box next to Internet Protocol Version 6 (TCP/IPv6).

The SSL certificate is used to secure the connection between your computer and the remote desktop server. When you connect to the server, your computer checks the SSL certificate to make sure that the server is who it claims to be. If there is a problem with the certificate, your computer will display an error message and may not allow you to connect.

In this case, the error message you are seeing suggests that the SSL certificate being used by the remote desktop server has a different server name than the one you are trying to connect to. This can happen if the server name was changed, or if the certificate was installed on a different server with a different name.

To resolve this issue, you will need to obtain a new SSL certificate that has the correct server name. This can usually be done through the organization that manages the remote desktop server. Alternatively, you may be able to bypass the certificate check by clicking on the "Connect Anyway" button in the error message, but this is not recommended as it can compromise the security of your connection.

Regarding the nslookup result, it is normal to see the name of your wireless router as the DNS server if it is the device providing DNS resolution for your network. However, if you are seeing unexpected results or errors, you may want to check the settings of your DNS server. It's also possible that there are issues with the certificate chain, which is the series of certificates that are used to verify the identity of the remote desktop server. If any of the certificates in the chain are not trusted, this can cause the "not from a Trusted Certifying Authority" error that you are seeing.

One thing you can try is to check the details of the certificate that is causing the error to see if there are any issues or warnings. You can do this by clicking on the "View Certificate" button in the error message. This will show you information about the certificate, including the name of the certifying authority and the expiration date.

I hope this helps! Don't hesitate to reach out if you have any further questions.

Regards,

R. Cord