ActiveSync Autodiscovery process?

[ADB100]

I have read how Windows Mobile ActiveSync Autodiscovery is supposed to work and I am attempting to test this in a lab but the client behaviour doesn't seem correct. I am simulating the environment with a firewall/router where the AD components are on the 'inside' and the Clients are on the 'outside'. Only HTTPS is allowed to the Exchange server from outside-to-inside. DNS is handled externally which I have configured up correctly (I think?) - I have the 'autodiscover.domain.com' entry pointing to the Exchange server as well as a SRV record of '_autodiscover._tcp.domain.com' again pointing to the Exchange server. Testing directly for the URL

https://autodiscover.domain.com/autodiscover/autodoscovery.xml

works from a PC.
When I attempt the autodiscovery on a Windows Mobile 6.1 device I can see a DNS lookup for 'domain.com' and the correct reply of the AD servers, the device then attempts a HTTPS connection to one of the DC's but this doesn't work as the traffic isn't allowed by the firewall. I was expecting the device to then try a DNS lookup for 'autodiscover.domain.com' however it doesn't. If I allow HTTPS access to the AD server then it works however the AD server isn't running any HTTP/HTTPS services. I can see on a sniffer trace when the traffic isn't allowed the HTTPS traffic to the AD server go unreplied, but when the restriction is removed the AD server replies but I assume the responses are wrong as after three attempts the device then does a DNS lookup for 'autodiscover.domain.local' and the discovery completes correctly.

I think I may have misunderstood something, but I can't allow HTTPS access to a DC from an unsecured network?

Andy

 

[58sniper]

Try Microsoft's tool for this:

https://testexchangeconnectivity.com/

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[ADB100]

Try Microsoft's tool for this:

https://testexchangeconnectivity.com/

This only works if your Exchange server is visible on the Internet as it is a series of automated tests to check the URLs out. In my case this is all in a lab with no external connections so I can't use it. However I don't think it would help anyway as I have explained the issue and it appears to be a Client behaviour issue where it doesn't try to lookup the hostname 'autodiscover.domain.com' if the HTTPS reqests to 'domain.com' go unanswered.

Andy

 

[theravager]

Get outlook autodiscover working externally first as its pretty easy to troubleshoot. If it works 'and' the active sync device you are using supports autodiscover you will be away