Autodiscovery uses INTERNAL svr name not EXTERNAL routable DNS name
New Exchange Svr 2007, SP1 deployment. Internal name of server: exchangesvr.spacefoundation.internal External name (DNS): exchange.spacefoundation.org I've configured autodiscovery.spacefoundation.org to route to the svr as well, & it works. I've confirmed the receive connectors have 'exchange.spacefoundation.org' for "Specify FQDN...", as well as ActiveSync, Outlook Anywhere, and anywhere else I found the internal name referenced. Still, when setting up desktop Outlook, autodiscovery runs like a charm, but it looks for exchangesvr.spacefoundation.internal!! How I've made it work is by adding a local hosts file entry for the 'internal' name to the public IP of the svr! Indeed, NOT a desired fix! Any ideas as to why this svr is broadcasting itself using it's internal FQDN? Thanks! -Fred.
August 14th, 2008 11:20pm

Hi Fred, Please understand that for internal Outlook 2007 client which is able to connect to DC, it will query an AD object service connection point (SCP) to get the URL of the Autodiscover service. You can set the AD object service connection point (SCP) by using following command: Set-ClientAccessServer http://technet.microsoft.com/en-us/library/bb125157(EXCHG.80).aspx You can also locate the SCP point manually by using Adsiedit.msc: DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name> For external Outlook 2007 client which is not able to connect to DC, the client locates the Autodiscover service on the Internet by using the primary Simple Mail Transfer Protocol (SMTP) domain address from the user's e-mail address. Depending on whether you have configured the Autodiscover service on a separate site, the Autodiscover service URL will be either https://<smtp-address-domain>/autodiscover/autodiscover.xml or https://autodiscover.<smtp-address-domain>/autodiscover/autodiscover.xml. Therefore, whether does the external user type email address (user@spacefoundation.internal) to configure his profile? For more information regarding Autodiscover: White Paper: Exchange 2007 Autodiscover Service http://support.microsoft.com/kb/940881/en-us A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service http://support.microsoft.com/kb/940881/en-us Mike
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2008 8:44am

Hi, I'm having a big problem.. I cant put autodiscover to work! If I configure outlook manually, it works. But, when I try to use autodiscover service, I receive a message: "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action ". So I cant configure any profile using autodiscover. I ran test-webservices cmdlet and the result is fine. Autodiscover service was tested successfully. I did "test email configurantion" using outlook (manually configured) and autodiscover is ok to. I don't know what could be. I've creatde a Host record in my dns "autodiscover" pointing to my CAS server. But one detail.. My smtp is different of my internal domain, I have " @a.com" and my internal domain is "b.com." The host record created was in my "b.com" zone. I dont have a "a.com" zone. This could be the cause of my problem? Tks!!
August 26th, 2008 5:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics