159141 - ZoneAlarm: [any URL] "could not be found" after upgrade to Moz 1.1b

Status: RESOLVED INVALID

(Plugins Graveyard :: Checkpoint Zonealarm, defect)

Description

[Glenn Randers-Pehrson]

After installing Moz 1.1b, it's unable to find any URL.  The window
"<URL> could not be found. Please check the name and try again." appears.
Other applications continue to be able to connect.  Downgrading to
Moz 1.1a cures the problem.  I reinstalled 1.1a and 1.1b three or four
times to be sure that 1.1a works and 1.1b doesn't.

FWIW, I'm connected to my ISP (comcast.net) through a cable modem and am
using a Netscape 4.78 profile.

Glenn

Comment 1

[Glenn Randers-Pehrson]

See also bug 151720 and bug 154490 which are similar.
I cannot confirm either because the circumstances seem to
be somewhat different.

Glenn

Comment 2

[Darin Fisher]

can you check the settings in Edit->Preferences->Advanced->Proxies to see if you
might have a proxy server configured somehow?  i'm guessing this isn't the
problem since moz 1.1a works for you, but maybe it's worth checking...

Comment 3

[Glenn Randers-Pehrson]

Both 1.1a and 1.1b are configured "direct connection to the Internet".
I get my IP number via DHCP.

Glenn

Comment 4

[Matthias Versen [:Matti]]

To be sure :
Have you installed Mozilla over an older build ?

If yes do this :
uninstall mozilla, delete all files in c:\programs\Mozilla.org\Mozilla\ (but
save your plugins) and reinstall mozilla.

If you still see the problem try "mozilla -profilemanager" and create an
additional test profile.

Comment 5

[Glenn Randers-Pehrson]

I have installed 1.1b over 1.1a, 1.1a over 1.1b, 1.1b after uninstalling 1.1a,
and 1.1a after uninstalling 1.1b.  Nothing changes the behavior.  Neither does
enabling/disabling quickstart.

I'll give the profilemanager a try now, but I have already tried with an alternate
profile created by Netscape 4.x.

Glenn

Comment 6

[Darin Fisher]

glenn: maybe the problem has to do with profile migration from 4.x to Mozilla. 
creating a new profile using Mozilla is probably a good way to eliminate some
variables.  thx!

Comment 7

[Glenn Randers-Pehrson]

Creating a new profile with Mozilla-1.1b's profile manager didn't change
anything.  Incidentally I cannot select the new profile from 1.1a -- probably
no surprise there.  Also I couldn't select it when I was done with the profile
manager; I had to select one of the older ones, then restart Mozilla, and then
was able to select the new one.

Glenn

Comment 8

[Darin Fisher]

hmm... are you running both moz1.1a and moz1.1b at the same time?  there is
profile locking that prevents you from using the same profile from more than one
browser instance at a time.  maybe that explains why you weren't able to select
your new profile from moz1.1a ??

Comment 9

[Glenn Randers-Pehrson]

Nope, only running one.  Uninstalled the other.  Cold rebooting my machine
doesn't help either.

Glenn

Comment 10

[Darin Fisher]

ok :(  hmm... windows 95, right?  i should look around for a windows 95 box... i
wonder if this has anything to do with the autodial code that recently landed.

cc'ing smeredith

Comment 11

[Steve Meredith (gone)]

I haven't been able to reproduce, but haven't tried 95 yet. The autodial stuff
should have no effect on Windows 95, but you never know.

Try turning off the autodial code using the pref in all.js:
pref("network.autodial-helper.enabled", false);

This bypasses *most* of the autodial changes.

Comment 12

[Darin Fisher]

Glenn: to follow smeredith's advice, you'll have to go to the directory into
which you installed mozilla and then edit defaults\pref\all.js

thx!!

Comment 13

[Glenn Randers-Pehrson]

I edited all.js, set autodial-helper to false and restarted Moz 1.1b.
No help.  Shut down the machine and did a cold restart, then started
Moz 1.1b with the new 1.1b profile.  No help.  Checked all.js to make
sure it's still set false; it is.

Glenn

Comment 14

[Darin Fisher]

Glenn: thx for taking the time to exhaust that possibility.  i'm not sure what
else to suggest at the moment.  i'll try to locate a win95 machine and see what
happens...

Comment 15

[Prashant Desale]

fwiw, this is working for me so far on win95 internally.  I also tried disabling
autodial and still could not duplicate.

Comment 16

[Tom Everingham]

oops, that last comment was actually from me working from prashants office. 
Darin, if there is anything you want me to try regarding this please tell me. 

Comment 17

[Steve Meredith (gone)]

I can't get Mozilla to run at all on a "fresh" copy of Windows 95. It just hangs
at the splash screen. Is there some trick to get it to run?

Comment 18

[Steve Meredith (gone)]

Scratch that. Reinstalled Mozilla 1.1b and it's working now. I'm not seeing the
problem described in this bug.

Comment 19

[Glenn Randers-Pehrson]

The culprit was the firewall (ZoneAlarm).  It wasn't recognizing
Mozilla 1.1b as being the same program as Mozilla 1.1a.  I think
this is actually proper behavior of ZoneAlarm.  Duh.

Changing bug to resolved, INVALID.

Glenn

Comment 20

[John Unruh]

Verified invalid.

Comment 21

[timeless]

We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.

Comment 22

[Glenn Randers-Pehrson]

It's still INVALID and was my mistake.  The vendor's action was OK.