Exchange and DNS settings for Outlook 2013 and 2016

Hi All Experts.

I've network with new Exchange 2013
Computers (Windows 10) with Outlook 2007 and 2010 (domain members or not) doesn't have any problem to connect to Exchange
Outlook 2013 and 2016 computers that are not part of domain (Windows 10 home edition) has problem to configure outlook.
For the first time when I try to connect new profile to Exchange Outlook is asking for Name, email and password, then is keep prompting for password all the time.

There is no way to connect.

I assume there is some problem with new way of authentication in new Outlook 2013 and 2016 but I can't figure out what I need to change in my network configuration to make this work.
LVL 29
Tom CieslikIT EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hello ThereSystem AdministratorCommented:
Have you checked Remember password? HERE

Close “Microsoft Outlook” >> Click on “Start” button >> type "Credential” in the search box >>you will then see ‘Credential Manager’ >> Click on “Credential Manager”.
Under “Generic Credentials”, you will most likely see an entry that has Outlook in the name.
Delete it. In fact, you can delete all the entries in Generic Credentials if you like.
Close Credential Manager Window and start “Microsoft Outlook”.
If it asks for a password, enter the password and check for it to remember the password.

More suggestion are HERE.
0
Tom CieslikIT EngineerAuthor Commented:
I'm testing it on new laptop and there is nothing about outlook in Credentials Manager since profile was never created. Because of this problem Windows did not saved any information. Profile was never finished, so there is no information under Mail 32-bit in control panel to.
0
Randy DownsOWNERCommented:
Your computers need to be on the domain or connected via VPN to use Exchange server. Since you have Home versions of Windows 10 that's not going to be an alternative.

As an alternative you may want to setup Outlook on the web.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Tom CieslikIT EngineerAuthor Commented:
Why ?
I have computer in home that is not part of domain and I can connect easily to our company Exchange server.
All I need to do is put password when I run Outlook, but this is Outlook 2010.
What Microsoft have changed in Outlook 2013 and 2016 with connection Exchange server ?
Why connection is not available for non-domain members ?
0
Randy DownsOWNERCommented:
Is your computer at home connected via a VPN? Is it Win 10 home version?
0
Randy DownsOWNERCommented:
Maybe this will help.

The key text being:

An option is set in the Domain Controller Group Policy to deny NTLM Authentication requests.  

The option is found in the  Domain Controller Group Policy under

  Policies

    Windows Settings

       Security Settings

         Local Policies

             Security Options

                 Network Security:Restrict NTLM:NTLM Authentication in this domain - Deny all

SOLUTION

Setting this Option to Disable will remove the restriction and things will begin to work normally.

Do not forget to run gpupdate on the servers if you want the change to be applied immediately.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tom CieslikIT EngineerAuthor Commented:
Randy Downs - VPN is not helping at all since computer can't connect from internal company network to.

I have changed settings for Computer configuration in GPO and updated policy on Domain Controller, then I've try to connect to Exchange from home without VPN and still no success
0
MaheshArchitectCommented:
do you have auto discover dns record published?
domain joined client find SCP in ad and can connect but workgroup machines not
publish auto discover record in dns, point machine to ad dns server and then try to configure outlook again
it's auto discover who provide server name to client to connect with
0
Randy DownsOWNERCommented:
Try pinging the Exchange server by its name. Try again with the ip.

You may also want to look at ipconfig /all to see what you are using for DNS.
0
Tom CieslikIT EngineerAuthor Commented:
I have autodiscover Forwar lookup zone

if I'll go to:  https://autodiscover.domain.com/autodiscove.xml, then OWA pops up
0
Tom CieslikIT EngineerAuthor Commented:
Randy Downs - Outlook 2007 and 2010 working OK with no issues
0
Tom CieslikIT EngineerAuthor Commented:
There is no address or autodiscover error, It must be something with authentication, If computer is not part of domain, there is no way to autheniticate using Outlook 2013 and above, but 2010 and lower versions working OK
0
Randy DownsOWNERCommented:
Can you downgrade one of the problem computers to Outlook 2007 and 2010 to see if they will work? How many computers have issues?
1
Randy DownsOWNERCommented:
proxy enabled that has your own domain listed as an exception?

proxy issue with Outlook 2013.

There are work arounds if you can't install the update.

To resolve this issue, install the February 10, 2015, update for Outlook 2013. For information about this update, click the following article number to view the article in the Microsoft Knowledge Base:
2956087  February 10, 2015, update for Outlook 2013 (KB2956087)
0
MaheshArchitectCommented:
check authentication method with outlook anywhere on CAS server, it should be NTLM for external and internal both and same at client end as well
https://community.spiceworks.com/topic/1162161-exchange-2013-outlook-prompt-for-login
1
Tom CieslikIT EngineerAuthor Commented:
[PS] C:\Windows\system32>Get-OutlookAnywhere -Server email | fl *Internal*


InternalHostname                   : email.domain.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl          : True

[PS] C:\Windows\system32>

[PS] C:\Windows\system32>Get-OutlookAnywhere -Server email | fl *External*


InternalHostname                   : email.domain.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl          : True

[PS] C:\Windows\system32>

Same authentication methods for Internal and External

I have 20 new out of the box laptops, all with Windows 10, and Office 2013. One has Office 2016. Fully patched.

It must be something with new Office, because If I'll uninstall Office 2013 and install Office 2010 on one laptop, then Outlook is connecting with no problem.

If I will upgrade Windows 10 home to Windows 10 Pro (I did it last night on one laptop) then Office 2013 is prompting for password and never finishing profile setup, but if I'll add computer to domain, there is no problem to configure Outlook 2013
0
Tom CieslikIT EngineerAuthor Commented:
Get-OutlookAnywhere | FL Identity,*host*,*auth*


Identity                           : EMAIL\Rpc (Default Web Site)
ExternalHostname                   : email.domain.com
InternalHostname                   : email.domain.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
0
Randy DownsOWNERCommented:
Maybe this tool will provide some insight.

Support and Recovery Assistant is a new tool that helps users troubleshoot and fix issues with various Office 365 apps and services. The app diagnoses common Outlook issues like account setup, connectivity issues, password issues, or Outlook stops responding or crashes. To identify the root cause of these issues, the app runs checks such as:
Checks licenses
Verifying users’ credentials and that Office 365 servers are reachable
Checks for updates to Outlook clients
Checks authentication
Network checks
Protocol checks
Depending on the test results, the tool can offer to automatically fix problems for users or provide instruction on recommended solutions. All the diagnostics results are saved in a log file for users to share with their Office 365 admin or support engineers for further investigation.

Because we are constantly improving it, we recommend running Support and Recovery Assistant whenever you have issues with Outlook or Office 365 for business.
0
Tom CieslikIT EngineerAuthor Commented:
Randy Downs - thank you for link to Microsoft connectivity analyzer.
I know this website and did test many times.

Like I said again, there is no issue with Outlook 2010.
Outlook 2013 prompting for password again and again  from INSIDE company and OUTSIDE company if computer is not part of domain.
0
Craig BeckCommented:
You don't NEED to be on a domain to authenticate to any version of Exchange. If you put the exchange server details in manually it should work fine.
0
Randy DownsOWNERCommented:
Craig Beck brings up a good point. I assume you have tried entering credentials manually. Perhaps the user name needs to be entered in the format \domain\username
0
Tom CieslikIT EngineerAuthor Commented:
It doesn't matter guys if I put server information manually. In auto mode it is finding server with no problem, then is attempting to log in, and is comming back asking for password.
It must be something wrong od different in authentication protocol in Outlook 2013
0
Randy DownsOWNERCommented:
Does it make any difference if you turn off Outlook Anywhere?

Connection Tab - uncheck "Connect to Microsoft Exchange using HTTP"
0
Craig BeckCommented:
Check the time/date on the failing clients.
0
Tom CieslikIT EngineerAuthor Commented:
Randy Downs - I can't because many people using OWA from home.

Craig Beck - New computers out of the box, new patched windows, all settings are correct. I did updated one windows to pro and add it to domain and, no problem with Outlook.

So only Home Edition Windows can't set outlook correctly. It must be something with authentication
0
Craig BeckCommented:
How are you entering the username?
0
Tom CieslikIT EngineerAuthor Commented:
Thank you guys.
Finally I was able to resolve issue. The problem was with authentication.
I had to make changes in GPO for whole domain and after restarting IIS I was able to configure Outlook.
Is not prompting for login and password anymore. Only once after first profile setup.

User name in Outlook wizard is in First and Last Name format and login popup in domain\username format, then outlook is replacing it as username@domain.com in login field.

It was a pain and I don't understand why Microsoft did not hard coded  any note for Exchange configuration in Outlook 2013 setup if they've changed authentication requirements.

Experience is a power :)
0
MaheshArchitectCommented:
what setting you altered in GPO, if you could please explain for information
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.