Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Firefox 3.6 14 on Debian 6.0 takes almost 20-30 seconds to connect to a website. Other browsers operate normally fast.

  • 3 respostas
  • 6 têm este problema
  • 3 visualizações
  • Última resposta por tjm_dsl

more options

Just upgraded my DSL to 7 Mbps. I didn't notice the problem that much, if it actually occurred, on the slower line. When I start Firefox 3.6.14 (not Iceweasel) compiled for amd64, it takes almost 30 seconds to connect to any website or when I change to a different website. While waiting, the message in the status line says "Looking up" {website}. None of the other available browsers do this, nor does my windows machines using IE or Firefox. The Help>Troubleshooting paste was too large. I'll sent it if needed. Thanks.

Just upgraded my DSL to 7 Mbps. I didn't notice the problem that much, if it actually occurred, on the slower line. When I start Firefox 3.6.14 (not Iceweasel) compiled for amd64, it takes almost 30 seconds to connect to any website or when I change to a different website. While waiting, the message in the status line says "Looking up" {website}. None of the other available browsers do this, nor does my windows machines using IE or Firefox. The Help>Troubleshooting paste was too large. I'll sent it if needed. Thanks.

Todas as respostas (3)

more options

Solução escolhida

more options

Thanks cor-el, I think this solved the problem. I'll wait a day or so and report back as to whether this has without a doubt fixed the problem.

thanks, tjm

more options

Disabling IPv6 definitely fixed the problem. Thanks, again.