- OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 HOW TO
- OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 UPDATE
- OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 WINDOWS 10
- OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 PASSWORD
There may be a way to tighten security by turning off NTLM, but still supporting Exchange->Outlook connections, but that's beyond my current level of expertise. In short, it appears that Outlook Autodiscovery needs NTLM, so don't turn that off if you need it, even on servers that are not hosting Exchange.
OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 UPDATE
May run into a similar problem - be sure to update the policy for ALL SERVERS, not just the Exchange servers. In any case, that was a red herring and only distracted me from finding the actual solution. When I forced it to update too, everything started working again, both internal and external connectionsĮven with the benefit of hindsight, I'm not sure why it worked internally, but only when one particular DAG server was disabled. Apparently, there was one additional Domain Controller that still had the old value for blocking NTLM connections. I was about to abandon that approach, when I figured just to be thorough I should run gpupdate on all servers, not just However, even after I had set that in Group Policy and run gpupdate on all the servers with Exchange on them, the problem still occurred. Setting this Option to Disable will remove the restriction and things will begin to work normally.ĭo not forget to run gpupdate on the servers if you want the change to be applied immediately. Network Security:Restrict NTLM:NTLM Authentication in this domain - Deny all The option is found in the Domain Controller Group Policy under It led me to this page:Īn option is set in the Domain Controller Group Policy to deny NTLM Authentication requests. Wow, this was a pain, but the error above was indeed the key. To enter users we are (and always have) entering ourcompanydomain\user. marketingname), and where our AD domain would be ourcompanydomain.local (same name as the OWA domain, but ending in. I don't think this is related, but one possible unusual aspect to our system is that our OWA domain name is and mail addresses Note that they are different domains (ourcompanydomain vs. Restarted all servers and the test clients since making that change back, just in case. The closet to changing anything that I can think of is that yesterday (mail was still working until this morning) I had disabled NTLM connectivity on the AD via Group Policy, but as part of debugging, I've since reverted that to the prior setting.
OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 HOW TO
Unlike previous versions of Outlook, Outlook 2016 doesn't seem to allow me to manually enter the server name, AD domain name, and other information, so if it's not getting it right via autodiscover, I'm not sure how to troubleshoot or work around that. What could it be? Something to do with Autodiscover? I also tried connecting Outlook to Exchange off the LAN, and they suffer the same exact problem, so it's not just the LAN side of the Exchange-Outlook connection that's failing.īased on the symptoms, and that it affected all copies of Outlook at the same time, I assume this must be an Exchange setting.
OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 PASSWORD
The mail profile, I can't recreate it to even launch Outlook, because it gets stuck on the username password window. Everything works fine everywhere except Outlook.
OUTLOOK 2016 UNABLE TO CONNECT TO EXCHANGE 2010 WINDOWS 10
Passwords, rebooted the AD servers, deleted and tried creating a whole new mail profile on one of the client computers, and deleted and recreated the connection to the server on Windows 10 Mail. To test, I have restarted client and server computers, reset user
For example, I can get e-mail on my Windows Phone, in Windows 10 Mail, and via OWA. Users have no problem connecting to Exchange and logging in and getting mail via other paths. I'm the ExchangeĪdmin, so this is my responsibility to fix.
All are being told to enter a username and password, which are never accepted. I'm not aware of any changes that would explain this, though obviously something has changed, because none of our users can connect to Exchange (2013, Version 15.0īuild 1156.6, in a 2-server DAG) via Outlook 2016 (don't have any older versions of Outlook to test - all users are updated automatically via Office 365). I'm utterly baffled by this, largely because until this morning, everything was working fine.
0 kommentar(er)
