Closed Bug 347643 Opened 19 years ago Closed 19 years ago

Firefox can not find any urls outside our our LAN

Categories

(Core :: Networking, defect)

1.8 Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: william, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 After auto upgrade to 1.5.0.6 Firefox is dumb and blind to the internet. It can not find any url, whether it is given as a domain or as the IP address if it is beyond our NAT router/firewall (Netgear FVS318). After reinstalling 1.5.0.4 Firefox works just fine without any change in firewall/router configuraltion. From that computer nslookup and ping of outside addys work find as does (shudder) MSIE. I downloaded the 1.5.0.6 version twice to check for corruption - no difference Reproducible: Always Steps to Reproduce: 1.install 1.5.0.6 downloaded from http://www.mozilla.com/products/download.html?product=firefox-1.5.0.6&os=win&lang=en-US 2. 3. Actual Results: when it opens, it can not even find the "you've upgraded" page
This looks like a router/firewall problem. Perhaps FF 1.5.0.6 is blocked because of some CRC check? -> Core / Networking -> WORKSFORME?
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
Version: unspecified → 1.8 Branch
*** Bug 347663 has been marked as a duplicate of this bug. ***
Looks like you submitted your bug twice! :P Anyway, here's my two cents: Perhaps your Firewall has not been configured to allow Firefox 1.5.0.6 (the new version) to access the internet? Please check your Firewall settings, and if it was a problem in your Firewall, this bug is not appropriate for Bugzilla and should be marked INVALID.
What special access could FF 1.5.0.6 require of the firewall that 1.5.0.4 does not ? In any case, the firewall if configured to permit all inside->outside access, while blocking almost all outside->inside access.
The culprit is a combination of Symantec Internet Protection and Mozilla's failure to get on the Symantec "known safe" list. Ubeknownst to be me the user had Symantec Internet Protection (SIP) installed. Apparently Symantec maintains a list of known safe programs and Mozilla is either not on it and/or the digital signature is incorrect. Apparently, usually, SIP asks the user for permission, but after an automatic FF upgrade SIP considered this a new program, but did not ask for internet access permission.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.