Hi All, I have a simple question about autodiscover/OOF with INTERNAL clients only: I have exchange 2007 with a 3rd party cert. Everything is working properly with external outlook clients - the problem is with internal ones. I am sure that the problem lies with the fact that from the LAN i cannot resolve the external name of the domain, and when I see outlook trying to do the tests, it doesn't stop on the first one (SCP). What can I do to reslove this? I did solve it by adding the a zone of the external domain name to the internal DNS but I never had to do it anywhere else, and never had a problem.

By default the Autodiscover SCP will be set to Https://yourserverfqdn/autodiscover/autodiscover.xml What is the output of the following command: Get-ClientAccessServer ¦ fl Name,AutoDiscoverServiceInternalUri The EWS (Exchange Web Services) controls the Availability service so let's see how that is configured: Get-WebServicesVirtualDirectory ¦ fl name,internalurl,externalurl I'm curious as to why internal clients are unable to resolve external DNS names?

When I changed the above to the internal netbios FQDN of the server autodiscover works, but then I get a certificate error (because the netbios name does not match the certificate). Internal clients are able to solve external DNS names if you type in the browser https://mail.thenameoftheexternaldomain.com it's not opening the page and that's the source of the problem. Thank you!

So if the clients can resolve the external DNS name then keep all the SCP as the external name. When you say "it's not opening the page and that's the source of the problem." are you referring to OWA? I guess I'm not really clear on what exactly isn't working.

Hi, if I go to https://mail.externaldomain.com/autodiscover/autodiscover.xml it doesn't open, as well as https://mail.externaldomain.com/owa From the outside it's working properly.

Hey, Autodiscover shoud be in this format: https://autodiscover.externaldomain.com/autodiscover/autodiscover.xml When you run "Get-ClientAccessServer ¦ fl Name,AutoDiscoverServiceInternalUri" it should be https://autodiscover... Not https://mail... Do you have a DNS entry for "autodiscover.externaldomain.com'?

I am using SRV record, not the method you're mentioning.

Hi, No matter which Name Services you use(DNS or SRV record), all the client from internal network should resovle the autodiscover domain name directly to an internal IP address instead of an external one. I think you need add a record for autodiscover.externaldomain.com name point to an internal address(exchange 2010 CAS IP address)Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, No matter which Name Services you use(DNS or SRV record), all the client from internal network should resovle the autodiscover domain name directly to an internal IP address instead of an external one. I think you need add a record for autodiscover.externaldomain.com name point to an internal address(exchange 2010 CAS IP address) More information: http://support.microsoft.com/kb/940881 (How to configure) http://support.microsoft.com/kb/939184/ (Information about hotfix) http://support.microsoft.com/gp/CUHotFix_LandingPage_Request (Request hotfix) http://msexchangeteam.com/archive/2007/09/21/447067.aspx (Msexchangeteam.com article) Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.