Home > Unable To > Autoconfiguration Was Unable To Determine Your Settings Outlook 2007

Autoconfiguration Was Unable To Determine Your Settings Outlook 2007


Join Now  On Feb 14, 2016 our hosted exchange company made some changes to their system which resulted on all of our employees receiving the Autodiscover popup when they opened Outlook. I'm not using SNAT. I have also removed "Negotiate" as a provider as Michael pointed out. The certificates are also for "company-int.com". navigate here

Results, find the OOF URL which Outlook client trying to access.OOF URL in IE and see whether it can be accessed successfully. I do have a Certificate in place and that is how we can use owa and email for smart phones. 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 What version are you running on your F5 gear? 0 ​ USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER Updated 05-Apr-2011•Originally posted on 05-Apr-2011 by jdewing 131 hoolio - Yes, I have http://blogs.msmvps.com/andersonpatrico/2012/07/05/autoconfiguration-was-unable-to-determine-your-settings/

Autoconfiguration Was Unable To Determine Your Settings Outlook 2007

The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate. Unfollow » Follow this Posthaven » Enter your email address to get email alerts about new posts on this site. NotBefore = 7/23/2013 8:38:25 PM, NotAfter = 7/23/2018 8:38:25 PM Checking the IIS configuration for client certificate authentication. What version of BigIP are you running and which template did you use? 0 ​ USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER Updated 05-Apr-2012•Originally posted on 05-Apr-2012 by Mathew 194 Hi

anyone found a fix for this? 0 Jalapeno OP Shawn1123 Apr 19, 2016 at 12:34 UTC mikesomers wrote: I am also having the issue of no OOO or I'd check your local DNS for autodiscover.yourdomain.com and make sure it resolves properly.  Also, try pinging autodiscover... anyone found a fix for this?Hey mikesomers, I really wish I had a fix for this.  I had a total of three hosted exchange accounts with this issue out of the Outlook 2016 Autoconfiguration Was Unable To Determine Your Settings What did they do to fix it? 0 Featured Post 2016 Annual Membership Survey Promoted by Experts Exchange Want to help improve the Experts Exchange community and be entered to win

All DNS and pings resolve correctly so I can't say it's that.  Only after altering different registry keys in the first two computers with this issue it was fixed.  Each has Autoconfiguration Was Unable To Determine Your Settings 2016 Are they on the LAN or trying to use RPC over HTTP? 0 Pure Capsaicin OP Rod-IT Mar 29, 2016 at 6:51 UTC Do you have an internal Outlook first looks for in-site SCPs as they should be the fastest experience for the client, and if none exist in-site it will look for all SCPs in the org and https://www.experts-exchange.com/questions/26194527/Autoconfiguration-was-unable-to-determine-your-settings.html The only differences is the OS (Server 2008 R2 vs Windows 7), my laptop has 32 bit office and the server has 64 bit, and the terminal server group policies that

As with DNS and pinging autodiscover it works fine.  I think it has something to do with the registry entries for autodiscover.  But I can't compare a working computer to a No Free/busy Information Could Be Retrieved Outlook 2010 Close About DevCentral We are a community of 250,000+ technical peers who solve problems together. Question is, why are they different? The certificate is trusted and all certificates are present in the chain.

Autoconfiguration Was Unable To Determine Your Settings 2016

The port was opened successfully. If this is not the case, please contact [email protected] Autoconfiguration Was Unable To Determine Your Settings Outlook 2007 the answer was Yes. Autoconfiguration Was Unable To Determine Your Settings Office 365 Help Desk » Inventory » Monitor » Community » Manage Edit Post Comments Logout Login BrianDagan.com Bio Links Résumé Contact «Back to blog Fix: Outlook 2007/2010 Out-Of-Office and Free/Busy Data Not

Now none of our users can connect to the Out of Office assistant as well as they cannot download the offline address book. check over here Any other ideas? 0 ​ USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER Updated 13-Jan-2012•Originally posted on 13-Jan-2012 by Adam Miceli 0 Josh, are you doing SSL offload? Email address is invalid. Where is that pulled from? Outlook 2010 Autoconfiguration Was Unable

thanks, Verus. Test Steps The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.dialmfg.com on port 443. Filter by: Solution Application Delivery Cloud DevOps Security Technology AAM AFM APM ASM AWS Azure BIG-IP BIG-IP DNS BIG-IQ Enterprise Manager iApps iCall iControl iControlREST IP Intelligence Services iRules iRulesLX http://popupjammer.com/unable-to/unable-to-read-file-excel-2007.html If the link I provided tests ok then the settings are good and its a local issue.

Test Steps The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=dialmfg.com, OU=Domain Control Validated. No Free/busy Information Could Be Retrieved Your Server Location Could Not Be Determined You're following this blog. Headers received: Connection: Keep-Alive Content-Length: 58 Content-Type: text/html Date: Wed, 28 Aug 2013 17:04:25 GMT Server: Microsoft-IIS/7.5 WWW-Authenticate: Negotiate,NTLM,Basic realm="autodiscover.dialmfg.com" X-Powered-By: ASP.NET Wednesday, August 28, 2013 5:23 PM Reply |

I can't determine what is causing it.

Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We There are some iRules you need to add to deal with Autodiscover issues in 10.2.x. antiwraith Ars Tribunus Militum Registered: Nov 5, 2008Posts: 1903 Posted: Thu Oct 25, 2012 2:44 pm DNS Suffixes are the same on both machines.The autodiscovertext.exe reports the following:for trying '[email protected]' it Your Automatic Reply Settings Cannot Be Displayed Because The Server Is Currently Unavailable 2010 Please Help!

When i add autodiscover.company.com to DNS the "test e-mail configuration" works fine but i get a window with security alert "autodiscover.company-group.com" when i start outlook with the error "the name on PreferLocalXML ExcludeHttpRedirect ExcludeHttpsAutodiscoverDomain ExcludeHttpsRootDomain ExcludeScpLookup ExcludeSrvLookup ExcludeSrvRecord Thank you Reply Leave a Reply Cancel reply Your email address will not be published. and I am sure you will want more info on config, so let me know what you need. weblink Office 365 Active Directory Exchange Azure How to downgrade Outlook 2016 to Outlook 2013 Article by: Lisa If you don't know how to downgrade, my instructions below should be helpful.

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 reg delete HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover /v PreferLocalXML /f reg delete HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover /v ExcludeHttpRedirect /f reg delete HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover /v ExcludeHttpsAutodiscoverDomain /f reg delete HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover /v ExcludeHttpsRootDomain /f reg delete HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover /v ExcludeScpLookup /f reg Additional Details The certificate is valid. Creating your account only takes a few minutes.

Lets get some comparisons from these and working ones. Additional Details Remote Certificate Subject: CN=dialmfg.com, OU=Domain Control Validated, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US. This was upgraded from exhange 2003, but should be running just fine as Microsoft helped our admin finalize the switchover.