Were you to reissue that certificate ever I would suggest considering the use of a true FQDN and not a NetBIOS host name; you may be confusing things when it resolves "servername" to "servername.mydomain.local
Can you get this working from the CSG box itself? You want to work OUT as you troubleshoot...you can test from the outside initially but if it fails I always suggest starting at the CSG, make sure you can connect to itself, and then work your way out to the client.
Well, back to my first thought: "servername.domain:443" this does not match your certificate; again, I am not sure this is part of the issue but it may be a component. Are you using the same DNS namespace internally as externally or do you have a .local or something internally?
I find it odd Verisign issued you a cert with a common name like you are saying.
Main Topics
Browse All Topics





by: pfcjokerPosted on 2009-04-30 at 12:10:38ID: 24273364
Cert has to match how you configure SG. In your case you should not be using FQDN anywhere due to the fact that you got a <servername> cert instead of <servername>.<domain> certificate.
The SG prevents man-in-the-middle attacks by validating the certificates configured - if it finds any mismatches or a cert it is not expecting it will deny the connection.
You will also likely see some SSL related errors in the eventlog that would point you to this issue.