So, we seem to be having a problem with our OAB... every time an Outlook 2007 client attempts to connect and download the OAB, it fails with the error: 14:35:15 Microsoft Exchange offline address book 14:35:15 Not downloading Offline address book files. A server (URL) could not be located. 14:35:15 0X8004010F This was copied and pasted from a Sync Issue in my Outlook 2007 client... it is the same error that the client returns when doing a Send/Receive. I started my troubleshooting with every techie's greatest tool... the internet! Found a number of support threads on the issue, at least a dozen different solutions for each thread, none of them really making much sense to me (well okay some of them did). I have tried every solution I could find. Here is all the information I can think of, which may be relevant: Exchange 07 Shell command: Code Snippet [censored]= our domain EXCHANGE2 = our exchange 2007 server server2 = Our Active Directory server Code Snippet [PS] C:\Documents and Settings\Administrator.COUNTYGP>Get-AutodiscoverVirtualDirectory Name : Autodiscover (Default Web Site)InternalAuthenticationMethods : {Basic}ExternalAuthenticationMethods : {Basic}BasicAuthentication : TrueDigestAuthentication : FalseWindowsAuthentication : FalseMetabasePath : IIS://exchange2.[censored]/W3SVC/1/ROOT/Aut odiscoverPath : E:\Program Files\ExchangeServer\ClientAccess\Au todiscoverServer : EXCHANGE2InternalUrl : https://exchange2.[censored]/autodiscover/ExternalUrl :AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=P rotocols,CN=EXCHANGE2,CN=Servers,CN=Exchange Ad ministrative Group (FYDIBOHF23SPDLT),CN=Adminis trative Groups,CN=COUNTYGP,CN=Microsoft Exchang e,CN=Services,CN=Configuration,[censored] Identity : EXCHANGE2\Autodiscover (Default Web Site)Guid : c78b81e4-dc8f-40ba-b7de-9fae7aba0954ObjectCategory : /Configuration/Schema/ms-Exch-Aut o-Discover-Virtual-DirectoryObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscove rVirtualDirectory}WhenChanged : 27/07/2007 1:53:06 PMWhenCreated : 25/05/2007 11:54:25 AMOriginatingServer : server2.[censored] IsValid : True The "Test E-Mail Autoconfiguration" tool, from Outlook 2007. Set to Check autodiscover settings, but none of the Guessmart stuff... also truncated to the actual autodiscover URL: Code Snippet Attempting URL https://exchange2.[censored]/autodiscover/autodiscover.xml found through SCP Autodiscover to https://exchange2.[censored]/autodiscover/autodiscover.xml starting Autodiscover request completed with http status code 403 Autodiscover to https://exchange2.[censored]/autodiscover/autodiscover.xml FAILED (0x80004005) Powershell get-oabvirtualdirectory: Code Snippet [PS] C:\Documents and Settings\Administrator.COUNTYGP>Get-OabVirtualDirectory Server Name Internal Url External Url------ ---- ------------ ------------EXCHANGE2 OAB (Default Web... https://exchange... https://exchange... We have an SSL certificate issued to us by a trusted CA, which I actually just installed today. Made our client access run seamlessly. Please let me know if there is any other information you want... and please please please help if you can -our users are starting to get annoyed with 20-30 sync issues appearing every day. In the efforts of keeping everything clean, please assume I haven't tried anything... and we can re-do all the troubleshooting from step 1.

If the client's browser is configured with a proxy server there can be issues. Try to put the FQDN in the internal URL in the browser proxy exceptions ormodify the FQDN ininternal URLs to just NetBIOS names.

Hi Erik, Were you still receiving this error? The code snippet you have shown from the Email Autoconfiguration show a HTTP 403 error which is a HTTP forbidden error. Were there any permission changes on IIS or folder? Can you access the autodiscover.xml file by browsing to it? Cheers, Rhys

the internal and external URL of your autodiscover virtual directory are the same? kind : https://Mydomain.com/auotdiscover/autodiscover.xml Mydomain.com is your public domain! then donate this case if you use a proxy server ISA or TMG, you should published the autodiscover floder of your exchange organization! I suggest you using this config : the internal URL is: https://Mydomain.local / auotdiscover/autodiscover.xml the external URL is: https://Mydomain.com/auotdiscover/autodiscover.xml while adding the local domain in the proxy exception in your ISA or TMG to avoid the other during the discovery probélme auotmatique

Hi Use this link for troubleshooting the issue http://blogs.technet.com/b/exchange/archive/2007/04/19/3401966.aspx Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82