asked on

Multiple Outlook clients cant connect to servers.

Hi, starting about two days ago, or Sept 12th, 2018, I have had about 6 calls where users said their Outlook 2016 systems were unable to connect to get mail. Some are Exchange, and others POP accounts. They get a trying to connect, then failed to connect message.

This is different companies at different sites. Strange thing is it's only Outlook 2016, not 2013 or older.

Thanks all.

Mahesh

Basic trouble shooting needs to be done at client end, what troubleshooting steps you have conducted so far?

Dan

ASKER

Hi Mahesh, I can remote into any of these clients. I was able to ping the host name, uninstalled Office 2016 installed 2013, that worked, back to 2016 no worie. Also deleted profile made new one, same problem.

Mahesh

what is your exchange version ?

uninstalled Office 2016 installed 2013, that worked, back to 2016 no worie.

so reinstalling / repairing outlook 2016 resolves your issue?

Dan

ASKER

sorry "worie" is a a mistype of "NoWorke" I think it's an update in 2016, but I can't prove it. I read somewhere that there was an update to 2016 that won't let it connect to older email hardware, but there wasn't much else.

Mahesh

what is your exchange version ?

Dan

ASKER

Oh, it's the Exchange online, 365. Go Daddy and Network Solutions. The POP clients are the same, Go Daddy and Network Solutions.

ASKER CERTIFIED SOLUTION

Mahesh

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Dan

ASKER

but 99 percent of my clients are oK

I think I found the fix, but this isn't going to look good on me as an admin, but noone knows me here.

So when I take the primay dns and set it not to be the domain controller, but googles, it works fine.

I'll go ahead and accept you guys for the answer, thanks again for the help you two.

Dan

ASKER

Thanks a ton for the fast help

Dan

ASKER

thanks again

Mahesh

you simply need to forward internet traffic to google dns on domain controller under dns manager \ server properties \ forwarder tab and ensure that on machines preferred dns is pointing to domain controller / dns server IP only, else you will find other AD authentication issues