With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.
COURSE of the MONTH
9 days, 20 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
the certificate is not from a trusted certifying authority
Posted on 2016-08-05
Please help!
I have a simple server that I have enabled RDP on at work. I go home, fire up Remote Desktop, type in a public IP address, log on with my credentials, and I'm in.
During the logon process, I get an alert like the one attached: "the certificate is not from a trusted certifying authority". If I go through the process of installing the certificate, I get the prompt "The server name on the certificate is incorrect".
I don't want to ignore the prompt (I have to explain the prompt to management). Is there a way I can get rid of it without having to buy an external certificate, setup an enterprise CA, or setting Remote Desktop to not warn me about it (advanced tab > server authentication option)? Can I safely ignore it, since I'm using an IP address that I know, and can be fairly certain it's not a man in the middle attack? I do have NLA enabled on the remote box.
The remote box is server 2012 and my home computer is Windows 7 with the latest version of Remote Desktop.
Thank you all, I appreciate any help I can get.
I have a simple server that I have enabled RDP on at work. I go home, fire up Remote Desktop, type in a public IP address, log on with my credentials, and I'm in.
During the logon process, I get an alert like the one attached: "the certificate is not from a trusted certifying authority". If I go through the process of installing the certificate, I get the prompt "The server name on the certificate is incorrect".
I don't want to ignore the prompt (I have to explain the prompt to management). Is there a way I can get rid of it without having to buy an external certificate, setup an enterprise CA, or setting Remote Desktop to not warn me about it (advanced tab > server authentication option)? Can I safely ignore it, since I'm using an IP address that I know, and can be fairly certain it's not a man in the middle attack? I do have NLA enabled on the remote box.
The remote box is server 2012 and my home computer is Windows 7 with the latest version of Remote Desktop.
Thank you all, I appreciate any help I can get.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3-
3
2
8 Comments
Active today
Self-signed certificates are never 'trusted'. You have to purchase a certificate from a reputable vendor to get it to be "from a trusted certifying authority". Only then will there be a certificate chain that leads back to a "trusted certifying authority".
Active today
Since you don't want to set up a proper certificate you can elect to ignore it. If the certificate changes you will have to agree to ignore it in the future.
Thank you for the responses, I appreciate them.
My understanding is that the point of the prompt is to ultimately help prevent man-in-the-middle attacks. Since I am using NLA and am using an IP address to connect, is a man-in-the-middle still possible, or highly unlikely?
My understanding is that the point of the prompt is to ultimately help prevent man-in-the-middle attacks. Since I am using NLA and am using an IP address to connect, is a man-in-the-middle still possible, or highly unlikely?
Active today
I thought your problem was having to explain why you are getting the prompt. If you use the current cert, each new user will get the prompt and have to accept it. The only way around that is to buy a cert that is traceable to a "trusted certifying authority".
Thanks. Is there a way I can visually tell if the information on the prompt is actually legitimate (spot if something is wrong)?
Active today
Certificate error messages normally give the details of their complaint. A valid certificate will show in the address bar where you can click on it to get more info about it.
Active today
With a self-signed certificate ANYONE can create a certificate using ANY name including the expected name that you are expecting. If you are worried about MITM then vpn into the domain then connect your rdp session. MITM isn't that easy to implement without physical access to the internet endpoints.
Featured Post
The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
If you get continual lockouts after changing your Active Directory password, there are several possible reasons. Two of the most common are using other devices to access your email and stored passwords in the credential manager of windows.
On some Windows 7 (SP1) computers, Windows Update becomes super slow even the computer is reasonably fast. There's one solution that seemed to have worked well for me (after trying a few other suggested solutions).
This Micro Tutorial will teach you how to change your appearance and customize your Windows 7 interface to your unique preference.
This will be demonstrated using Windows 7 operating system.
This Micro Tutorial will give you basic overview of the control panel section on Windows 7. It will depth in Network and Internet, Hardware and Sound, etc.
This will be demonstrated using Windows 7 operating system.
Suggested Courses
Course of the Month9 days, 20 hours left to enroll
762 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.