Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Why does Firefox 37.0.1 on iMac running 10.10.3 takes almost one minute to connect to google.com?

  • 2 respostas
  • 1 tem este problema
  • 10 visualizações
  • Última resposta por acyaqub

more options

Safaria and Chrome are working fine on this iMac. But Firefox has serious problems connecting to google domain web sites. Other web sites work fine. But if trying to connect to gmail, google.com, google drive or google maps the firefox hangs for a long time saying "connecting". The problem is not deterministic, but appears to always happen at startup. I tried to debug this using firefoxDeveloperEdition using network monitoring. I could only get the problem to happen once and the network monitor did not reveal any long lasting requests. The request all completed in less then 500 msec but the total query took around 30 seconds.

Any ideas what is going on? I have done a reset and a safe start without any success.

Safaria and Chrome are working fine on this iMac. But Firefox has serious problems connecting to google domain web sites. Other web sites work fine. But if trying to connect to gmail, google.com, google drive or google maps the firefox hangs for a long time saying "connecting". The problem is not deterministic, but appears to always happen at startup. I tried to debug this using firefoxDeveloperEdition using network monitoring. I could only get the problem to happen once and the network monitor did not reveal any long lasting requests. The request all completed in less then 500 msec but the total query took around 30 seconds. Any ideas what is going on? I have done a reset and a safe start without any success.

Solução escolhida

Try to disable IPv6 (check for other possible causes as well).

Ler esta resposta no contexto 👍 1

Todas as respostas (2)

more options

Solução escolhida

Try to disable IPv6 (check for other possible causes as well).

more options

Thank you. Disabling IPv6 seems to have fixed the problem.