|
flapjack -> Certificate error: Outlook 2007 & Exchange 2007 (10.Jan.2008 2:01:28 PM)
|
When I connect to my Exchange 2007 server via Outlook 2007 from within the network, I get a certificate error. This is because of the way I have my DNS set up, but it shouldn't even be happening, as I'm inside the network.
Basically, the certificate is for domain.net, and the internal network name is obviously not that. I do have that domain added in DNS, and it resolves internally and externally (which works great for EVERYTHING besides Outlook 2007).
The mail server has two domain suffixes. The default network (which doesn't match the certificate), and the external network address domain.net. If you nslookup/ping mail.domain.net or mail.internal both resolve correctly.
The issue lies with setting up Outlook, but I don't understand why it's happening in the first place.
Since I'm internal to the network, I should just be able to type "mail" for the mail server. However, when I go back to check the account properties (after I've finished), Outlook has automatically appended the internal DNS address. When I open Outlook, I get the certificate error message. I've even tried typing "mail.domain.net" as the server address, but checking properties afterwards just shows Outlook to have corrected it to mail.internal-address.
The Outlook 2007 client is running on a Vista machine, if that helps. The mail server is running Win2k3-64. Under System Properties > Computer Name, I've tried clicking "Change", then "More" and changing the primary DNS suffix of the server to domain.net, but that just made it just about inaccessible from the world. It would still receive mail, but you couldn't get to it... even from OWA.
Any ideas on how to fix this? RPC over HTTPS works fine, obviously, as the PC external to the network and the certificate matches. Why is Outlook even looking for a certificate inside the network? Can't I disable that? Maybe it's some function of Vista??
|
|
|
|