AutoDiscover failing to locate ActiveSync ExternalURL

I am experiencing an issue where ActiveSync w/ AutoDiscover fails to recognize or read the ExternalURL's that I have configured. When I run a test using ExRCA or attempt to configure an EAS device using Autodiscover I get the event log shown below. However, if I do Autodiscover from Outlook or using the Outlook Autodiscover test from ExRCA everything works fine. ActiveSync itself also works fine once you specify the server. In  order to get this error to show up I turned up diag logging on ActiveSync and AutoDiscover to Expert level. 

I have verified that all the Internal and External URL’s are set in the EAS virtual directories and have even removed and re-added them. I have also reset the ActiveSync and Autodiscover virtual directories. This all includes many iisresets and various reboots as well.

Log Name:      Application
Source:        MSExchange Autodiscover
Date:          1/13/2012 5:37:15 PM
Event ID:      1201
Task Category: Provider
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      CAS02.contoso.com
Description:
Time:17:37:13.5068820, Id:3107295499, Error Response with the ErrCode:"1", Message:"No external URL is available to
 access this mailbox with Exchange ActiveSync. Your Exchange server configuration needs to be adjusted to allow access.", 
DebugData:"UserMailbox" was generated for EMailAddress:"contoso.service@contoso.com", LegacyDN:"" by 
"Microsoft.Exchange.Autodiscover.Providers.MobileSync.MobileSyncProvider, Microsoft.Exchange.Autodiscover, Version=14.0.0.0, 
Culture=neutral, PublicKeyToken=31bf3856ad364e35".

 

 

I get the following error information when running Test-ActiveSyncConnectivity:

Test-ActiveSyncConnectivity -UseAutodiscoverForClientAccessServer:$true -MailboxCredential (get-credential domain\testuser02) -verbose |fl

 

UserName                    : testuser02
StartTime                   : 1/15/2012 11:41:48 AM
Latency                     : 00:00:00.0312516
EventType                   : Error
LatencyInMillisecondsString :
Identity                    :
IsValid                     : True

RunspaceId                  : 2e5834c8-7f08-4b71-b36a-ebea19b829b6
LocalSite                   :
SecureAccess                : True
VirtualDirectoryName        :
Url                         :
UrlType                     : Unknown
Port                        : 0
ConnectionType              : Plaintext
ClientAccessServerShortName : Autodiscover
LocalSiteShortName          :
ClientAccessServer          : Autodiscover.contoso.com
Scenario                    : Autodiscover Client Access server
ScenarioDescription         : An attempt was made to contact Autodiscover server Autodiscover.contoso.com from (testuser
                              02@contoso.com)  for Client Access server information using NTLM for authentication.
PerformanceCounterName      :
Result                      : Failure
Error                       : No valid URI could be found in server node in Autodiscover result /ad:Autodiscover/ms:Res
                              ponse/ms:Action/ms:Settings/ms:Server[child::ms:Type="MobileSync"]/ms:Url.

                               Response:
                               <?xml version="1.0" encoding="utf-8"?><Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/20
                              06"><Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/mobilesync/response
                              schema/2006"><Culture>en:us</Culture><User><DisplayName>contoso Test 2</DisplayName><EMailAddress>testuser02@contoso.com</EMailAddress></User><Action><Error><Status>1</Status><Message>No external URL is available to access this mailbox with Exchange Active
                              Sync. Your Exchange server configuration needs to be adjusted to allow access.</Message><DebugData>UserMailbox</DebugData></Error></Action></Response></Autodiscover>

                               Use the Set-ActiveSyncVirtualDirectory task to configure the ExternalURL.

Does anyone have any thoughts on why this might be happening? Im also trying to figure out if there might be some permissions issues keeping the attributes from being read but so far I'm having trouble figuring out where exactly to look.