Closed Bug 287712 Opened 20 years ago Closed 20 years ago

update to 1.0.2

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mark, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 updated 1.0.1 to Firefox 1.0.2 for Windows now no webpages will come up. It looks like it is trying to pickup any additional updates but never finds anything then times out. Tried rebooting no progress. Uninstalled then clean install still same problem. Uninstalled and went back to 1.0.1 and browser works fine. Reproducible: Always
I uninstalled 1.0.2 and reinstalled 1.0.1 for the Mac and the problem still exists. Firefox has become virtually unusable. When looking for the 1.0.1 replacement and couldn't find one in the Firefox areas, I sent an eMail to support and got a reply of "we don't offer that kind of info". What? I have moved on to other browsers. Suggest you do the same.
Reporter: Do you have a software firewall installed and did you update the firefox configuration in your firewall after you upgraded ?
My friend has similar problem like yours. I was helping my friend to update from 1.0.1 to 1.0.2. It was opening OK but it will NOT browse anything outside at all. Then uninstalled back to 1.0.1 - it works fine. I update Firefox on my PC... from 1.0.1PR to 1.0.2 and it works fine. No change setting, firewall or anything else on both PCs.
There is one easy test for blocking via Firewall : open a Command-Window (Dos-Window) and start firefox. Now type "netstat -n" and you should see 2 localhost connections like this : TCP 127.0.0.1:1042 127.0.0.1:1043 HERGESTELLT TCP 127.0.0.1:1043 127.0.0.1:1042 HERGESTELLT
Your firewall is blocking Firefox. Adjust it to allow Firefox to browse the web and you should be fine.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
It working now after adjusting the firewall
You need to log in before you can comment on or make changes to this bug.