• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 529
  • Last Modified:

I keep getting a certificate error when accessing server 2008 TS locally

I just installed server 2008 to test in our environment.  When I go to https:\\server2008\ts, I get a certificate error there is a problem with this sites security certificate.  I just click continue.  Everything works until I try to run a remote program then I get the certificate mismatch name error.  I added the cert opn the server 2008, but it seems like the name is wrong.  Any ideas?
certerror.bmp
0
TriCountyIT
Asked:
TriCountyIT
  • 5
  • 3
  • 2
2 Solutions
 
60MXGCommented:
You might want to type in the whole link like https://Server08.tricountyhospital.org

0
 
TriCountyITAuthor Commented:
Doing it that way I was able to browse to the site with out getting the certificate error, but it still errors out when I try to connect to a remote app.
0
 
60MXGCommented:
What is the error on remote app?  Maybe you need to set your default url or default path in remote app??  Just a thought!
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
TriCountyITAuthor Commented:
the error is the screen shot.  It says there is a name mismatch on the cert.  Since that is happening it wont connect.
0
 
60MXGCommented:
Try to go to your browser and delete all those certificates cached and re-enter the site again!
0
 
TriCountyITAuthor Commented:
The problem is my self signed certificate says server08.tricountyhospital.org.  I am able to access remote programs when I go into the remote connection settings and change it to server08.tricountyhospital.org.  is there any way to change that to just server08 so i dont have to go the the FQDN all the time?
0
 
tigermattCommented:

The problem you are seeing is two-fold. The first issue is the FQDN on the certificate; if this does not match, the system you are connecting from will deem the connection unsafe and throw an error. The second issue is your certificate is a self-signed certificate, meaning most machines will automatically distrust it, once again deeming the connection insecure.

Your best option would be to purchase and install an SSL certificate from a trusted certification authority. This will eliminate both issues. You could use a SAN (Subject Alternate Name) certificate if you wished to address your server by more than one name, such as its FQDN and its NetBIOS (server08) name. Use https://domainsforexchange.net/ for cheap SAN SSL certificates; although it states it's for Exchange Servers, their certificates work equally as well for any other application requiring a certificate.

-Matt
0
 
TriCountyITAuthor Commented:
ya I figured that.  I was able to get it to work for testing purposes for now.  if we stick with the software we will purchase teh cert.  Thanks
0
 
tigermattCommented:

You would need to re-generate the SSL certificate internally (meaning you will need a Certification Authority installed) in order to eliminate the error at this stage. If it is purely a test environment, I'd suggest you simply ignore the error for now.

-Matt
0
 
TriCountyITAuthor Commented:
thanks for your help
0

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

  • 5
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now