Exchange 2016 on prem - Outlook Client cannot connect

HK@BfW 0 Reputation points
2024-02-15T07:57:11.4566667+00:00

Hello community!

I'm asking for suggestions about Exchange in an AD environment (W2K16) and a non-working Outlook client.

Exchange Server 2016 Std runs on a Windows Server 2016.

Installation, configuration and commissioning without any problems so far.

Mail accounts set up in the EAC (from AD) can be used for the first time without any problems and the mail flow also works perfectly; but only in the Outlook Web Client.

Every previous attempt to persuade Outlook to connect to Exchange has failed with the terse message "Something didn't work."

What is striking in this context is the fact that a 1:1 modeled structure works flawlessly.

Outlook of a logged in AD user starts, sets up the connection and then opens without any problems.

The only difference between the productive and test environment is an Ubuntu LTS server with Squid proxy, which establishes the Internet connection for the employees. Maybe there is a problem with a missing whitelist entry or a TLS issue??

Maybe someone has a tip where I can start?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,599 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Yuki Sun-MSFT 41,046 Reputation points Microsoft Vendor
    2024-02-16T02:13:03.2966667+00:00

    Hi @HK@BfW ,

    Every previous attempt to persuade Outlook to connect to Exchange has failed with the terse message "Something didn't work."

    Does this issue occur to both domain-joined and non-domain joined Outlook clients?
    What's the detailed version of the Outlook clients? You can check the build number via File > Office Account > About Outlook, confirm if the version information is the same in product and test environment.

    Besides, to help narrow down the problem, I'd recommend trying to use the Test E-Mail Autoconfiguration service within Outlook and see if the affected client can connect to the AutoDiscover service:

    1. Launch Outlook using a profile with no email account, see Use Outlook without an email account.
    2. Use the Test E-mail AutoConfiguration tool to help determine if AutoDiscover can success.

    Additionally, as regards to your concern about the whitelist entry, sounds like a reasonable cause as well. You can go through the document below and make sure the exclusions are configured properly:
    Running Windows antivirus software on Exchange servers


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.