noooodlez
asked on
Certification error connecting Outlook 2007/10 to Exchange 2007.
Following on from another post i made:
HERE
I am having an issue with a certification error between my Outlook Clients and Exchange Server.
I enabled a purchased 3rd party UCC Certificate through Exchange Powershell to allow http over RPC from external. My initial problem was that I did not add all of the required alt names to my first cert. Now everything is working (external clients, OWA) but outlook clients are getting a certificate error on initial connection on our internal network.
The error is telling me that "the name on the security certificate is invalid or does not match the name of the site" and the site to which it is trying to cennect is "Sites"
Sites is a cname that SBS puts into DNS to resolve to it's IIS applications (e.g. http://sites/owa). I dont know why Outlook is coming back with this eror (it should be retrieving data from servername.domain.local, which is an alt name on my certificate).
I have even tried deleting my outlook profile and re-connecting to clear out any links that I may have previously created.
Any ideas why Outlook would connect to sites and get this error??
HERE
I am having an issue with a certification error between my Outlook Clients and Exchange Server.
I enabled a purchased 3rd party UCC Certificate through Exchange Powershell to allow http over RPC from external. My initial problem was that I did not add all of the required alt names to my first cert. Now everything is working (external clients, OWA) but outlook clients are getting a certificate error on initial connection on our internal network.
The error is telling me that "the name on the security certificate is invalid or does not match the name of the site" and the site to which it is trying to cennect is "Sites"
Sites is a cname that SBS puts into DNS to resolve to it's IIS applications (e.g. http://sites/owa). I dont know why Outlook is coming back with this eror (it should be retrieving data from servername.domain.local, which is an alt name on my certificate).
I have even tried deleting my outlook profile and re-connecting to clear out any links that I may have previously created.
Any ideas why Outlook would connect to sites and get this error??
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi, Cheers for getting back to me.
Sounds like the one. I have checked the locations of the XML files and they are valid URLs when I replace mail.contoso.com with the netbios name of the server.
Now I need to know how to configure. The kb article suggests I use mail.domain.com (the name on my certificate). If I use this internally I think I would need to either updated the hosts file or DNS!?
Should I use the netbios name (simpler config) or the mail.domain.com, and make that resolve to the exchange server nic? Will the netbios name cause problems further down the line?
Is there any way I can back up this config in case I need to revert back?
Many Thanks.
Sounds like the one. I have checked the locations of the XML files and they are valid URLs when I replace mail.contoso.com with the netbios name of the server.
Now I need to know how to configure. The kb article suggests I use mail.domain.com (the name on my certificate). If I use this internally I think I would need to either updated the hosts file or DNS!?
Should I use the netbios name (simpler config) or the mail.domain.com, and make that resolve to the exchange server nic? Will the netbios name cause problems further down the line?
Is there any way I can back up this config in case I need to revert back?
Many Thanks.
For the autodiscover,EWS this will try using the cert. on the IIS
You could try configuring the URLs for the Autodiscover, EWS to see if you can avoid this warning