none
Changing AutoDiscover public server URL

    Question

  • We recently had the first time since moving to Exchange 2007 that someone tried to connect from outside the office.
    The autodiscovery file is served properly, but in the section Autodiscover\Response\Account\Protocol with TYPE:EXCH, the SERVER tag is set to EXCH01.office.local, which means it con not be resolved from outside the network.

    Is there a way to change the SERVER property to an externally resolvable DNS name?

    EDIT: to make it perfectly clear what I want, I am posting the relevant part of the AutoDiscover XML:
    <Protocol>
    	<Type>EXCH</Type>
    	<Server>EXCH01.office.local</Server>
    	<ServerDN>/o=First Organization/ou=Exchange Administrative Group /cn=Configuration/cn=Servers/cn=EXCH01</ServerDN>
    	<ServerVersion>720180F0</ServerVersion>
    	<MdbDN>/o=First Organization/ou=Exchange Administrative Group /cn=Configuration/cn=Servers/cn=EXCH01/cn=Microsoft Private MDB</MdbDN>
    	<ASUrl>https://remote.example.com/EWS/Exchange.asmx</ASUrl>
    	<OOFUrl>https://remote.example.com/EWS/Exchange.asmx</OOFUrl>
    	<OABUrl>https://remote.example.com/OAB/{guid}/</OABUrl>
    	<UMUrl>https://remote.example.com/UnifiedMessaging/Service.asmx</UMUrl>
    	<Port>0</Port>
    	<DirectoryPort>0</DirectoryPort>
    	<ReferralPort>0</ReferralPort>
    	<PublicFolderServer>EXCH01.office.local</PublicFolderServer>
    	<AD>EXCH01.office.local</AD>
    	<EwsUrl>https://remote.example.com/EWS/Exchange.asmx</EwsUrl>
    </Protocol>
    

    Wednesday, February 17, 2010 6:04 PM

All replies

  • Hi,

    Can you run the test-outlookwebservices or use www.testexchangeconnectivity and post the results here. I assume you try to use the Outlook anywhere feature when you say use it from outside ? This because when reading the following article http://technet.microsoft.com/en-us/library/dd439390(EXCHG.80).aspx will tell the <type>EXCH</type> are the url's used when connecting using RPC which in most cases internally. URL's which are located in the EXPR part are url's used by outlook anywhere. 

    But when posting the results we can further troubleshoot this issue.

    Regards,

    Johan
    Exchange-blog: www.johanveldhuis.nl
    Thursday, February 18, 2010 5:09 AM
  • May I ask why are you using this file in the first place?
    MVP | MCSE:M | MCITP: Enterprise Messaging Administrator | MCTS: OCS + Voice Specialization | http://www.shudnow.net
    Thursday, February 18, 2010 7:03 PM
  • Hi

    Type>EXCH</Type>
    	<Server>EXCH01.office.local</Server>

    The server part is valid here and u dont have to modify it, infact u cant modify it beacuse it is the FQDN of your Exchange server, which is dependant on the AD Domain name u used to install the Exchange server.

    R u having some issue connecting to your exchange server from outisde using Outlook Anywhere (RPC/HTTPS)? 

    Your outside URLs also seem perfect in ur posted XML. It looks like you have posted the result xml from "www.testexchangeconnectivity " test.

    Regards,




    Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com
    Saturday, February 20, 2010 11:52 AM

  • Sorry for not getting back to this. It seems that email notifications of thread replies are not working.

     

    I have not been able to replicate the issue since the computers that where having it were reformatted.

    The issue was computers trying to use outlook anywhere from outside our NAT were trying to get to EXCH01.office.local

    Thanks for your help.

    • Proposed as answer by Laeeq Qazi Friday, July 23, 2010 7:45 PM
    Friday, July 23, 2010 5:41 PM