Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

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 відповіді
  • 6 мають цю проблему
  • 3 перегляди
  • Остання відповідь від 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?

Обране рішення

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

Читати цю відповідь у контексті 👍 1

Усі відповіді (2)

more options

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

more options

Вибране рішення

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