Joanne Posted December 21, 2016 Posted December 21, 2016 As part of the DirectAccess setup, it wants to be able to connect to an internal website to check if it is on site or off site. I have IIS setup on another server, it has its certificates, but when I browse to it I get: In IIS it has 2 certificates. One is self signed and the other is from another server on the network. Can anyone shed light? Google isn't helpful!
Sagima Posted December 21, 2016 Posted December 21, 2016 I don't use direct access but my initial thoughts would be... Don't use a self-signed cert. Use one from your CA which your domain machines will trust. If you do you need to use the self signed one add that machine to the trusted ca list using group policy Make sure you are using the FQDN of the server everywhere so the names match up 1
Joanne Posted December 21, 2016 Author Posted December 21, 2016 I seem to have cracked it - https://www.sslshopper.com/article-how-to-create-a-self-signed-certificate-in-iis-7.html
Joanne Posted December 21, 2016 Author Posted December 21, 2016 I don't use direct access but my initial thoughts would be... Don't use a self-signed cert. Use one from your CA which your domain machines will trust. If you do you need to use the self signed one add that machine to the trusted ca list using group policy Make sure you are using the FQDN of the server everywhere so the names match up I think my problem was that I wasn't using the full on https:\\SERVER.DOMAIN!! Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now