Avatar for Username

Søg i Support

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.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

Updated from TBird 31.5.0 to 31.6.0. Now get unable to connect. Have stopped/started TBird and even rebooted Win7. Any suggestions?

  • 2 svar
  • 6 har dette problem
  • 2 visninger
  • Seneste svar af JoeatWC

JoeatWC
JoeatWC
more options

On second PC, was operating with Tbird 31.5.0. Received notice that needed to upgrade. Ran automatic upgrade to 31.6.0. Immediately upon restart of TBird, I received the message Unable to Connect to live.mozellamessaging.com instead of normal Welcome message on lower half of window. If I try to do a "Get Messages", the message at the bottom shows "Connecting to pop.earthlink.net as is should but it just hangs there. I have restarted TBird and even rebooted the Win7 system to no avail. I looked at the TBird Account Settings and they appear OK. Any suggestions on where to start?

On second PC, was operating with Tbird 31.5.0. Received notice that needed to upgrade. Ran automatic upgrade to 31.6.0. Immediately upon restart of TBird, I received the message Unable to Connect to live.mozellamessaging.com instead of normal Welcome message on lower half of window. If I try to do a "Get Messages", the message at the bottom shows "Connecting to pop.earthlink.net as is should but it just hangs there. I have restarted TBird and even rebooted the Win7 system to no avail. I looked at the TBird Account Settings and they appear OK. Any suggestions on where to start?

Valgt løsning

Thank you. I checked Norton AV and changed setting from Auto to Allow and that seemed to fix the problem.

Læs dette svar i sammenhæng 👍 1

Alle svar (2)

christ1
christ1
  • Top 25 Contributor
more options

If you run a personal firewall make sure Thunderbird is allowed.

JoeatWC
JoeatWC Spørgsmålsstiller
more options

Valgt løsning

Thank you. I checked Norton AV and changed setting from Auto to Allow and that seemed to fix the problem.