General Environment:
ExchangeServer: UseVMware WorkstationInstalledWindows Server 2003;
DNSName:Virtualad. exchangetest. com;
IP:192.168.0.100Domain:Exchangetest. com;
The public name of the Certificate Service isVirtualad. exchangetest. com, ServerOWASome requirementsSSLSecurity channel.
Client Computer andExchangeThe server is not in the same domain and the client cannot parseVirtualad. exchangetest. comOfIP
Problem: When you accessHttps: // 192.168.0.100/exchange/(Why not useHttps://VirtualAD.ExchangeTest.Com/ExchangeWhen accessing, we have already made it clear),Security alertDialog box, such:
The general description is as follows:
1The security certificate is not trusted.
2The security certificate name does not match the site
Solution:
1The reason is that the certificate is issued by the enterprise and is not acceptedIETherefore, you must install a certificate on the client to trust the certificate issued by the enterprise.
For more information, seeMicrosoftOfSupportArticle
Http://support.microsoft.com/default.aspx? SCID = KB; en-US; 218445
2, The security certificate name does not match the site, Because you requestedHttps: // 192.168.0.100/exchange, AndCommon name(The Certificate Server isVirtualad. exchangetest. com) Inconsistent, so this problem occurs;
Change the request Https://VirtualAD.ExchangeTest.Com/exchange Because the client and serverDNSConfiguration problems, so it cannot be resolved.
Solution: Open the hosts file of c: \ winnt \ system32 \ drivers \ etc, Add
192.168.0.100 virtualad.exchangetest.com
To point to a specificIPIn this way, all the problems have been solved.
Reference resources:
1,SSL enabling OWA 2003 using your own Certificate Authority
Http://www.msexchange.org/tutorials/SSL_Enabling_OWA_2003.html
2,How to configure Certificate Server for use with SSL on IIS
Http://support.microsoft.com/default.aspx? SCID = KB; en-US; 218445