搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

after download of 33.0, all non-mozilla pages give unable to connect error, firewall exception did not help

  • 3 个回答
  • 38 人有此问题
  • 3 次查看
  • 最后回复者为 RoaSiD

more options

I am now getting this error: Unable to connect

Firefox can't establish a connection to the server at www.fanfiction.net. Firefox can't establish a connection to the server at www.gmail.com. Firefox can't establish a connection to the server at www.facebook.com. Firefox can't establish a connection to the server at www.youtube.com.

   The site could be temporarily unavailable or too busy. Try again in a few moments.
   If you are unable to load any pages, check your computer's network connection.


   If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

can connect to all About pages, firefox was not previously on my firewall list, added to list with no change

posting this from chrome, which I would rather not use if avoidable, any help or advice would be welcome.

被采纳的解决方案

Do a malware check with several malware scanning programs on the Windows computer. Please scan with all programs because each program detects different malware. All these programs have free versions.

Make sure that you update each program to get the latest version of their databases before doing a scan.

You can also do a check for a rootkit infection with TDSSKiller.

See also:

在上下文中阅读这个答案 👍 4

所有回复 (3)

more options

ah sorry, OS windows 8

more options

选择的解决方案

Do a malware check with several malware scanning programs on the Windows computer. Please scan with all programs because each program detects different malware. All these programs have free versions.

Make sure that you update each program to get the latest version of their databases before doing a scan.

You can also do a check for a rootkit infection with TDSSKiller.

See also:

more options

I did run Malwarebytes, and it did find 3 issues, but I think the answer was the oft overlooked restart that happened after the scan.