Outlook disconnected on the Win10 client which have 2 NIC

Chong 871 Reputation points
2021-06-29T06:37:36.203+00:00

Hi Support,

We have win10 and win7 client using outlook 2016 to connect exchange 2016 server. All of the machine have 2 NIC, only one NIC (exchange network) have default gateway.

Sometime the Win 10 client outlook will disconnect suddenly. During problem occur, the machine can ping to exchange server, OWA also work. (The network icon in icon tray change to "No internet".) We need to disable the NIC and enable the NIC again, then the outlook resume. (the network icon show "connected")

This problem only happen on Win10 client, Win 7 client don't have issue. We tried to reinstall windows, outlook, and network driver, both can't solved the problem
Any idea?

Thanks
Chong

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Exchange | Exchange Server | Management
Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes

4 answers

Sort by: Most helpful
  1. Robert H 1 Reputation point
    2021-07-01T18:08:07.22+00:00

    Hi @Chong and @ChristyZhang-MSFT

    Some details from my environment where I'm facing the same issue...

    1. Outlook shows disconnected at random upon opening. Once it shows disconnected, it will not re-connect with a restart of the program or the PC.
    2. To fix, the user must close outlook, disable any NIC/network adapter other than the primary, then re-open Outlook - it will now connect to our exchange server correctly. The user can then re-enable the other NIC's they use (most of our workstations have at least one additional NIC)
    3. We are running Outlook 2016 on Windows 10 20H2. Exchange server 2010 on Window server 2008 R2 (soon to upgrade to exch2016 on server 2016/2019)
    4. We do not use VPN's, and the only type of machines I've seen the issue happen on thus far are physical workstations.
    5. We have IPV6 disabled entirely on our network via a GPO - I've seen some other articles stating that setting machines to prefer IPV4 r disabling IPV6 entirely will resolve this issue, but not in our case.
    6. For context, the environment this issue is occurring in is an air-gapped local network with no outside connection - just one Exchange server being used as Database and CAS.
    7. OWA works completely fine.
    8. No error popups at all, just the disconnected message in the bottom right Outlook tray. All other network-related functions of Windows work fine - shared network drives, printers, etc.

    A permanent fix/patch would be awesome for this, as it seems to re-occur for some users at random intervals. I've only really seen grumblings of this issue on the internet in the past few months, so perhaps it is something to do with 20H2?

    0 comments No comments

  2. HKBBK 1 Reputation point
    2021-11-05T02:43:42.86+00:00

    I have same porblem, It is appear on upgade to 20h2. We try to many soulution but can't really solve this problem. We only used the script to reset the network. The outlook connect will resume when reset the network.

    0 comments No comments

  3. Robert Hopman 1 Reputation point
    2021-12-02T18:29:08.947+00:00

    @Chong - @ChristyZhang-MSFT - any news on this?

    @HKBBK Thanks for the comment.

    To update everyone - this issue is still persisting on at least one of the machines in our environment. I tried setting the network adapter priority of the correct IPv4 adapter via the network configuration in control panel and also by setting the InterfaceMetric via powershell - no dice on this either.

    Really frustrating issue with no official solution still. I don't want to have to reimage or replace this user's PC but I'm thinking there is no other option at this point.

    Side note: The issue persists even after I've updated to Exchange server 2016 CU21.

    0 comments No comments

  4. Igor Valencic 1 Reputation point
    2022-01-17T14:18:58.703+00:00

    Any news on that issue?
    We are facing absolute the same thing. We had Windows 1809 and updated it to 21H2. Works on all Workstations where only one NIC is active...
    But this a no go, cause almost all developer have more then 2 NICS...
    Thanks for help!

    0 comments No comments

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.