216217 - Even when permission is granted, doesn't work behind firewall

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Jeremiah]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718

After upgrading from 1.2 final release to the 1.5a, I attemped to access a
website.  Norton popped up and asked me to create a new rule.  I did, granting
full access to Mozilla to any site.  It went ahead and loaded the page that
explains the beta-testing rules on Mozilla's site.  After that, it wouldn't open
a single page.  "The Connection Was Refused" is the error I keep getting.  When
I drop the firewall...it works great.  It seems that Norton was unable to learn
that Mozilla was what the rule was being applied to in this case.

Reproducible: Always

Steps to Reproduce:
1.  Start Mozilla
2.  Open any webpage
3.  Curse at the "connection refused" error message.

Actual Results:  
Connection refused.

Expected Results:  
Loaded the webpage

Comment 1

[Matthias Versen [:Matti]]

>When I drop the firewall...it works great.

That means that your firewall still blocks Mozilla.

-> invalid

Comment 2

[Jeremiah]

Yes, but it was updating Mozilla that caused the initial problem.  One of the
files that the 1.5a overwrote or installed in the registry made it unable to get
through the firewall as the earlier version had.  

Comment 3

[Matthias Versen [:Matti]]

Mozilla write only a few keys in the registry and Mozilla also never overwrites
system files.

This is invalid because it works without norton and it also works for many other
people. (including me with Kerio )

I don't know Norton but a few firewalls checks the CRC of the .exe and this CRC
cahnged of course if you upgraded.

-> invalid (please only reopen why this should be a Mozilla bug)

Comment 4

[Jeremiah]

Okay...the CRC changed when I upgraded.  Yes.  THEN, the first time that Mozilla
ran afterwards, it tripped up the firewall.  A dialgogue opens...it askes you to
configure a rule.  I told it to allow Mozilla to access every time to any port.
 BUT something in Mozilla 1.5a overwrote a resource somewhere, a resource that
wasn't removed by uninstalling or reinstalling the earlier version (the one that
had worked the whole time).  

There is some sticky file in there that Mozilla 1.5a created that doesn't allow
Norton to "learn" that it is a valid program accessing the internet.  

Perhaps the problem is Norton's, but that doesn't change the fact that a system
resource was overwritten by 1.5a that uninstalling and reinstalling could not
fix.  Only doing a system restore to yesterday solved the problem, so something
that Mozilla 1.5a put into my OS messed with the firewall software.  

Comment 5

[Matthias Versen [:Matti]]

>There is some sticky file in there that Mozilla 1.5a created that doesn't allow
>Norton to "learn" that it is a valid program accessing the internet.  

That would be a norton problem an no mozilla problem.

FYI Mozilla installes files in c:\programs\Mozilla.org and c:\programs\Common
Files\Mozilla..

Mozilla doesn't install system drivers.

this is invalid because this is a norton problem and no mozilla problem.
There could be only one problem with mozilla : if Mozilla would change the
application name with every launch but that's not true.
I also called my co-worker: Mozilla1.5a and Norton works fine on his system.

Please only reopen if you attach a log from the firewall where we could see why
Mozilla is blocked by Norton.

You can also try the .zip build (which dfoesn't overwrite anything and also
don't write anything to the registry unless you set it as default browser)

http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.5a/mozilla-win32-1.5a-talkback.zip

(unzip it to a new directory and launch Mozilla.exe)