realtimer
asked on
Outlook 2010/Exchange 2013 - There is a problem with the proxy server' security certificate (Error Code 38)
Hello,
We are running an Exchange 2013 server. I have received notice from a few users indicating the following. They are running Outlook 2010 clients. They seem to be okay on a Terminal Server and other workstations. So this appears to be workstation specific.
The errors are:
Security Alert
autodiscover.OutDomain.org
Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
x The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority.
x The security certificate has expired or is not yet valid.
x The name on the security certificate is invalid or does not match the name of the site.
Do you want to proceed.
When I look at the details of the certificate, it says:
Issued to: plesk
Issued by: plesk
Valid from 7/24/2010 to 7/24/2011
When I check the same account from OWA, it shows a completely different certificate. One that is valid till 2017 (this is in fact the correct one). I'm not sure what is happening. Any suggestions?
Thanks in advance.
Real-Timer
We are running an Exchange 2013 server. I have received notice from a few users indicating the following. They are running Outlook 2010 clients. They seem to be okay on a Terminal Server and other workstations. So this appears to be workstation specific.
The errors are:
Security Alert
autodiscover.OutDomain.org
Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
x The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority.
x The security certificate has expired or is not yet valid.
x The name on the security certificate is invalid or does not match the name of the site.
Do you want to proceed.
When I look at the details of the certificate, it says:
Issued to: plesk
Issued by: plesk
Valid from 7/24/2010 to 7/24/2011
When I check the same account from OWA, it shows a completely different certificate. One that is valid till 2017 (this is in fact the correct one). I'm not sure what is happening. Any suggestions?
Thanks in advance.
Real-Timer
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Go to Internet explored, open options and then go to content, there is clear certificate state.
Also check if there is any bad certificates available those are expired. (in personal store and trusted root CA as well.)
Also check if there is any bad certificates available those are expired. (in personal store and trusted root CA as well.)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hello -
I found that the workstation was using a public DNS server instead of the local DNS server. Not sure why this workstation was obtaining a different DNS server from the same DHCP server that the rest of them were using. I set it manually for now till I figure out the rest. This addressed the issue. Thank you.
I found that the workstation was using a public DNS server instead of the local DNS server. Not sure why this workstation was obtaining a different DNS server from the same DHCP server that the rest of them were using. I set it manually for now till I figure out the rest. This addressed the issue. Thank you.
ASKER