ITGURU Posted March 31, 2022 Posted March 31, 2022 Wondered if anyone can shed some light. It's always been when accessing systems by IP address it is instant and immediately goes past securing network connection and get the certificate issue, say yes to continue and immediately get the desktop. However if i enter the hostname or FQDN of the server in the mstsc box, it takes forever to get past the 'securing network connection' part- it hangs there for a long time before get the certificate warning to continue. What causes this when have no dns issues?
Steve21 Posted March 31, 2022 Posted March 31, 2022 You shouldn't be getting any cert error if you're using a server name unless something is wrong, as it should match your trusted domain and just connect. The reason for getting it via IP is your 10.10.10.10 etc wouldn't match the SSL response of server.domain.com etc When you get the cert warning using the server hostname, if you click view cert what's the error it says on it? as that should help narrow down your issue Steve
ITGURU Posted April 1, 2022 Author Posted April 1, 2022 You shouldn't be getting any cert error if you're using a server name unless something is wrong, as it should match your trusted domain and just connect. The reason for getting it via IP is your 10.10.10.10 etc wouldn't match the SSL response of server.domain.com etc When you get the cert warning using the server hostname, if you click view cert what's the error it says on it? as that should help narrow down your issue Steve I get the certificate warning even when using the IP address - but it just says the certificate is not from a trusted certifying authority which is as expected. whether i connect via IP address or DNS name I still get the certificate warning, just with the IP, the warning is instant, but using FQDN it stays on securing network connection for ages before the security warning pops up.
ITGURU Posted April 1, 2022 Author Posted April 1, 2022 The odd thing is, I have the servers added to mremote aswell and when i select the server in that rdp software it connects immediately when using the FQDN so seems to be an issue with the RDP (mstsc) client.
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