Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Mozilla サポートの検索

サポート詐欺に注意してください。 私たちはあなたに通話やショートメッセージの送信、個人情報の共有を求めることはありません。疑わしい行為を見つけたら「迷惑行為を報告」からご報告ください。

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

User authenticated but not connected (outlook)

  • 26 件の返信
  • 27 人がこの問題に困っています
  • 5730 回表示
  • 最後の返信者: Dave
  • 解決済み

Lately I'm having trouble with my connection with outlook. I use a free outlook email address. Sometimes (not always) when starting Thunderbird, I get the "user authenticated but not connected" warning. After a while it's working again.

I have tried several settings but can't figure out what solves this issue.

I'm using port 993 / SSL/TLS and authentication method is set to normal password.

Most of the times this works.

When I switch to OAuth2, I get the Microsoft screen to login to my work / school account which I do not have.

I've search the web to find a solution for this but I can't find it. Hopefully someone can help me out because it drives me "nuts" ;)

Lately I'm having trouble with my connection with outlook. I use a free outlook email address. Sometimes (not always) when starting Thunderbird, I get the "user authenticated but not connected" warning. After a while it's working again. I have tried several settings but can't figure out what solves this issue. I'm using port 993 / SSL/TLS and authentication method is set to normal password. Most of the times this works. When I switch to OAuth2, I get the Microsoft screen to login to my work / school account which I do not have. I've search the web to find a solution for this but I can't find it. Hopefully someone can help me out because it drives me "nuts" ;)

この投稿は rasnijders により に変更されました

選ばれた解決策

david said

Just to share a thread. I do not use Outlook and cannot advise on a solution, but I noticed this similar thread that found a solution. That thread is at https://support.mozilla.org/en-US/questions/1400644 It's rather long, but interesting. They solved what appears to be the same issue by disabling ipv6 in config editor. I hope it may work for you. From their post, there seems to be a Microsoft problem with ipv6. Good luck.

That was the answer, I disabled IPv6 and can use Office 365 accounts again without issue. Thanks!! To do the same:

1. Menu > Settings 2. "Gear" tab > scroll to bottom > click "Config Editor" 3. Search for: IPv6 4. Toggle network.dns.disableIPv6 to true

Should start working immediately.

この回答をすべて読む 👍 2

すべての返信 (6)

選ばれた解決策

david said

Just to share a thread. I do not use Outlook and cannot advise on a solution, but I noticed this similar thread that found a solution. That thread is at https://support.mozilla.org/en-US/questions/1400644 It's rather long, but interesting. They solved what appears to be the same issue by disabling ipv6 in config editor. I hope it may work for you. From their post, there seems to be a Microsoft problem with ipv6. Good luck.

That was the answer, I disabled IPv6 and can use Office 365 accounts again without issue. Thanks!! To do the same:

1. Menu > Settings 2. "Gear" tab > scroll to bottom > click "Config Editor" 3. Search for: IPv6 4. Toggle network.dns.disableIPv6 to true

Should start working immediately.

この投稿は Qwidget により に変更されました

The following restored operation to my two systems. However, this may be a temporary fix, time will tell

Select: Tools -> Settings In FindSettings search for "Advanced Preferences" Click on "Config Editor" Click on "Show All" Scroll down to "network.dns.disableIPv6" Change setting to "True"

To set "network.dns.disableIPv6" to true works for me!

David's chosen solution is confirmed to work for Thunderbird 102.4.2 running on Ubuntu 18.04.6.

This had worked for me, but is no longer working. Forgot about it and accidentally just updated to TB 102.7.0 (on Ubuntu 22.04.1) and now the issue has returned. network.dns.disableIPv6 is still set to True but I'm still getting an authentication failure message even after the 2-factor authentication (with Duo).

paul.fogel said

This had worked for me, but is no longer working. Forgot about it and accidentally just updated to TB 102.7.0 (on Ubuntu 22.04.1) and now the issue has returned. network.dns.disableIPv6 is still set to True but I'm still getting an authentication failure message even after the 2-factor authentication (with Duo).

I mine broken again too. Changed network.dns.disableIPv6 to true, the other one with ipv4 also. Both solved it for awhile, only does it on some subfolder interestingly.

  1. 1
  2. 2