Avatar for Username

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

Cannot receive or send emails. Getting error ""NetworkError when attempting to fetch resource" in Thunderbird 102.5.0 email client

  • 2 vastausta
  • 1 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja mike.ayala

mike.ayala
mike.ayala
more options

One of our users, cannot receive or send emails. Getting error ""NetworkError when attempting to fetch resource" (this error shows at the bottom of the Thunderbird email client). Her Thunderbird email client was recently automatically updated to the latest version 102.5.0 via an update schedule in a package deployment software (PDQ). Since the version was updated, the user is receiving this error. The previous version that worked was 102.4.2(also installed via PDQ). Checked the server and account settings in user Thunderbird and everything settings wise are the same as before. Thinking the Thunderbird client could be blocked, I tried to allow the Thunderbird app in the user local Windows Firewall settings and tried turning off the local firewall but no difference. I tried to uninstall and reinstall ver 102.5.0 but no change. Tried to reinstall the last version that worked in 102.4.2 but same results. Even tried to install a much older version 78.1.1 just for grins but it gave me a message since her profile had been updated to use a newer version so installing older version would not work I since reinstalled 102.5.0 back on the user computer. Besides the Thunderbird auto updated to ver 102.5.0, the only other changes on the user computer were 3 new windows updates that installed on her computer on 11/18/22 (KB5019959, KB5020613, Servicing Stack 10.0.19041.2180). Tried to uninstall the KB5019959 but haven't try uninstalling the 2 other windows updates. Any advise would be greatly appreciated.

One of our users, cannot receive or send emails. Getting error ""NetworkError when attempting to fetch resource" (this error shows at the bottom of the Thunderbird email client). Her Thunderbird email client was recently automatically updated to the latest version 102.5.0 via an update schedule in a package deployment software (PDQ). Since the version was updated, the user is receiving this error. The previous version that worked was 102.4.2(also installed via PDQ). Checked the server and account settings in user Thunderbird and everything settings wise are the same as before. Thinking the Thunderbird client could be blocked, I tried to allow the Thunderbird app in the user local Windows Firewall settings and tried turning off the local firewall but no difference. I tried to uninstall and reinstall ver 102.5.0 but no change. Tried to reinstall the last version that worked in 102.4.2 but same results. Even tried to install a much older version 78.1.1 just for grins but it gave me a message since her profile had been updated to use a newer version so installing older version would not work I since reinstalled 102.5.0 back on the user computer. Besides the Thunderbird auto updated to ver 102.5.0, the only other changes on the user computer were 3 new windows updates that installed on her computer on 11/18/22 (KB5019959, KB5020613, Servicing Stack 10.0.19041.2180). Tried to uninstall the KB5019959 but haven't try uninstalling the 2 other windows updates. Any advise would be greatly appreciated.
Liitetyt ruutukaappaukset

Kaikki vastaukset (2)

gp
gp
more options

Hello

looks like the mail service is done by Microsoft; could it be because the account has not been migrated to OAuth2 (or switched to a account password) ?

To test that it's not a firewall problem, install Telnet from Windows features and run (replace smtp server name and imap server name by the value from the Thunderbird configuration):

telnet <smtp server name> 587 if it hangs, it's a firewall problem. and telnet <imap server name> 993 idem.

mike.ayala
mike.ayala Kysymyksen kysyjä
more options

Thanks for the reply but we resolved this. It was a Geo-IP issue on our firewall blocking.