Forum Discussion
jdewing
Apr 05, 2011Cirrus
Exchange 2010 AutoDiscover issue
When I opened Outlook, it will prompt with username and password to logon to autodiscover.domain.com. I follow the steps from “Deploying F5 with MS Exchange Server 2010”.
If I changed the I...
Joel_Moses
Apr 05, 2011Nimbostratus
In my environment, whenever I use IP address in place of hostname I get prompted for authentication no matter whether I'm going direct to CAS or via the F5. This makes sense because the bare IP address in the URL wouldn't be considered an IE "Trusted Site" so it wouldn't attempt automatic NTLM authentication with it. It would prompt me to manually enter the authentication.
What happens if you set a host file entry for "autodiscover.site.com" pointed at the F5 IP address, then try the request in IE as "https://autodiscover.site.com/autodiscover/autodiscover.xml"? Make sure to remove the entry later after you test. :>
I've seen four main things go wrong with autodiscovery on Exchange 2010 -- the cert on the autodiscover site does not have the "autodiscover" name set as either a primary or SubjectAlternativeName, the cert for autodiscover is not able to be verified from a trust perspective (self-signed or unknown CA), the Outlook profile the wrong Authentication Type set for Outlook Anywhere connectivity, or the configured Redirect URL on the autodiscover site itself is incorrect. In your case, it sounds like when passing through the F5 VIP the system has some reason to believe that it can no longer do automatic windows integrated authentication -- this could occur as the result of a certificate mismatch or a failure to believe the site can be classified as trusted.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects