Closed Bug 299509 Opened 19 years ago Closed 17 years ago

Connection Failure Error

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: db1_1959, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702 Firefox/1.0+

Can't see ad graphics--get a Connection Failure Error Headline in Home Page

Removed AdBlock and removed sites in Block Remote images (Privacy)

Reproducible: Always

Steps to Reproduce:
1. go to http://home.bellsouth.net
2.
3.

Actual Results:  
No ads

Expected Results:  
Read home page and scripts for ads
WFM, get no errors. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050702 Firefox/1.0+ ID:2005070222
Component: Build Config → General
QA Contact: build.config → general
Still the SAME FOR DeerPark Alpha 1 (20050703)
Have the same problem for MSIE 6.x: "Connection Failure Error" wherein the Site
blocking and image loading options of MSIE are: No Site Blocking, Allow Image
Loading.

Mozilla Firefox DeerPark Alpha 1(20050703)

Any Reg file to force Network Registry Entry for WinXPro to NO "Connection
Failure Error in Windows XP Pro"??
The same problem occuring with WINDOWS XP Home edition. After updating to 2.0.0.7, the firefox is unable to connect to internet[ shows connection error ].

Even after un-installing and re-installing, it shows connection error.
Even if we try to install previous versions say 2.0, the problem persists.

Is there any solution for this problem??

This WFM with Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9a9pre) Gecko/2007100804 Minefield/3.0a9pre ID:2007100804.

I suggest you get support here http://www.mozilla.com/en-US/support/ . Probably in the mozillazine forums. This is not a bug in Firefox.

Thanks for the input.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.