Outlook displays banner that says: Check your connection Open a browser to sign into ______.com and receive new emails

Anonymous
2020-08-06T16:24:56+00:00

When I click the button it opens a generic msn webpage. My company uses DSSO so everything is already signed in. Can't seem to find anyone else who has had this error. I have tried repairing office, recreating mail profile etc.

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

43 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-11-29T12:06:31+00:00

    Happens when internet has a blip.

    I'm currently living with it and just unplug the ethernet cable and plug it back in again to stop the error.

    Best solution is to get your ISP to sort out a stable connection for you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-06-15T18:07:16+00:00

    How do you remove this banner?

    thank you!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2021-06-11T07:00:15+00:00

    I found 2 different solutions that both reliably solve the problem:

    1. In HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkConnectivityStatusIndicator add/set the value NoActiveProbe to 0x00000001 and reboot, or alternatively
    2. Disable DNS over TLS (DoT) for the respective network (i.e. switch back to good old unsecure DNS), and reboot router and machine

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2021-05-16T10:28:05+00:00

    Disabling WiFi cleared it temporarily ( back on and so far so good)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-05-12T12:29:34+00:00

    yes - disconnect from the internet then reconnect - the issue disappeared for me doing that.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments