HiI have Exchange 2007 set up with ISA2006 publishing the OWA and Outlook Anywhere sites - CAS servers have an internal URL which DNS points directly at them, and the externalURL points at a 'public' URL which resolves to the outside of the ISA servers.Autodiscover is working fine both internally and externally - all the URLs returned are correct (different for internal and external connections) and most things are working fine, however there is one strange thing happening - when Internal Outlook 2007 clients connect they are getting prompted for authentication for the external URL - some of the clients go via an HTTP proxy so I can see the CONNECT to the externalURL coming in.I have done the test autoconfig from outlook and that all looks fine, Get-WebServicesVirtualDirectory and Get-OABVirtualDirectory both return the correct internal and external URLs so where is outlook getting the external url from and why is it trying to contact it ?Thanks for your time reading this.

Hii have the same issue, did you resolve it?ThanksLourh

Hi, I have the same problem as well. I thought about removing the 'externalurl'-parameter from webservices as we don't use Outlook Anywhere yet, but I am not able to. Does anyone know how to fix this, or as a workaround remove the value entered into the 'externaurl'-property on the webservice? Thanks, Magne

Hi again, I was able to remove the 'externalurl' by using $Null like this: Set-WebServicesVirtualDirectory -Identity '[Servername]\EWS (Default Web Site)' -ExternalUrl $Null I hope this will stop the internal Outlook 2007-clients from trying to connec to the the external URL. As we may implement Outlook anywhere in the near future having to add the externaurl again, I would still like to find out why this happened in the first place. Thanks -Magne