ZoneAlarm & KB951748 - My Fix Works!

ZoneAlarm & KB951748 - Where's my internet?

My solution that actually works after trying all those below and on
every other post, and you can keep all your other settings alone:

1. Open ZoneAlarm's 'Firewall' tab.
2. Click the 'Custom' button under 'Internet Zone Security'.
3. On the 'Internet Zone' section scroll down to 'Allow outgoing UDP
ports'.
4. Check it and enter "80-3000", click 'Apply' button.
5. Do the same for 'Allow outgoing TCP ports'.
6. Click OK.

* The range "80-3000" is just a guess on my part, if anyone knows a
better range please post it.

Please post success or failure, thank you.


ZoneAlarm is investigating the issue with Microsoft update KB951748:
http://forum.zonelabs.org/zonelabs/b...hread.id=52785

To solve this, just reset the ZA database and the ZA will be "fresh" as
when it was first installed:
http://forum.zonelabs.org/zonelabs/b...ssage.id=52727

ZoneAlarm Customer Care How to Perform a Clean Install:
http://www2.nohold.net/noHoldCust542...n_install.html

MS update KB951748 and ZoneAlarm:
http://www.dslreports.com/forum/r207...eAlarm-PROBLEM

*** Where the real blame lies!!!
Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
Patch Released:
http://securosis.com/2008/07/08/dan-...atch-released/

To find out if the DNS server you use is vulnerable:
http://doxpara.com/


ju.c

It'll be interesting to see how this works for other folks, ju.c.

I'm more prone to to go with ZoneAlarm's suggestion on this (link below) and
let the MS/ZoneAlarm people earn thier big bucks

http://forum.zonelabs.org/zonelabs/b...ssage.id=52863

===================================

"ju.c" wrote:

> ZoneAlarm & KB951748 - Where's my internet?
>
> My solution that actually works after trying all those below and on
> every other post, and you can keep all your other settings alone:
>
> 1. Open ZoneAlarm's 'Firewall' tab.
> 2. Click the 'Custom' button under 'Internet Zone Security'.
> 3. On the 'Internet Zone' section scroll down to 'Allow outgoing UDP
> ports'.
> 4. Check it and enter "80-3000", click 'Apply' button.
> 5. Do the same for 'Allow outgoing TCP ports'.
> 6. Click OK.
>
> * The range "80-3000" is just a guess on my part, if anyone knows a
> better range please post it.
>
> Please post success or failure, thank you.
>
>
> ZoneAlarm is investigating the issue with Microsoft update KB951748:
> http://forum.zonelabs.org/zonelabs/b...hread.id=52785
>
> To solve this, just reset the ZA database and the ZA will be "fresh" as
> when it was first installed:
> http://forum.zonelabs.org/zonelabs/b...ssage.id=52727
>
> ZoneAlarm Customer Care How to Perform a Clean Install:
> http://www2.nohold.net/noHoldCust542...n_install.html
>
> MS update KB951748 and ZoneAlarm:
> http://www.dslreports.com/forum/r207...eAlarm-PROBLEM
>
> *** Where the real blame lies!!!
> Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
> Patch Released:
> http://securosis.com/2008/07/08/dan-...atch-released/
>
> To find out if the DNS server you use is vulnerable:
> http://doxpara.com/
>
>
> ju.c
>
>
>
>

New link, official ZoneAlarm announcement thread:
http://forum.zonelabs.org/zonelabs/b...l&message.id=6

ju.c

> ZoneAlarm & KB951748 - Where's my internet?
>
> My solution that actually works after trying all those below and on
> every other post, and you can keep all your other settings alone:
>
> 1. Open ZoneAlarm's 'Firewall' tab.
> 2. Click the 'Custom' button under 'Internet Zone Security'.
> 3. On the 'Internet Zone' section scroll down to 'Allow outgoing UDP
> ports'.
> 4. Check it and enter "80-3000", click 'Apply' button.
> 5. Do the same for 'Allow outgoing TCP ports'.
> 6. Click OK.
>
> * The range "80-3000" is just a guess on my part, if anyone knows a
> better range please post it.
>
> Please post success or failure, thank you.
>
>
> ZoneAlarm is investigating the issue with Microsoft update KB951748:
> http://forum.zonelabs.org/zonelabs/b...hread.id=52785
>
> To solve this, just reset the ZA database and the ZA will be "fresh"
> as when it was first installed:
> http://forum.zonelabs.org/zonelabs/b...ssage.id=52727
>
> ZoneAlarm Customer Care How to Perform a Clean Install:
> http://www2.nohold.net/noHoldCust542...n_install.html
>
> MS update KB951748 and ZoneAlarm:
> http://www.dslreports.com/forum/r207...eAlarm-PROBLEM
>
> *** Where the real blame lies!!!
> Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
> Patch Released:
> http://securosis.com/2008/07/08/dan-...atch-released/
>
> To find out if the DNS server you use is vulnerable:
> http://doxpara.com/
>
>
> ju.c
>
>
>

Hi ju.c -

Thanks for the reply, but I think if you check, you'll find the message-link
you posted was from yesterday (June 8th in USA):

"07-08-2008 03:51 PM"

The message I linked to has today's date:

"Message Edited by Forum-Moderator on 07-09-2008 07:11 AM"

Folks can do whatever they're comfortable with and it'll be interesting to
see how your solution works for other people!
=================

"ju.c" wrote:

> New link, official ZoneAlarm announcement thread:
> http://forum.zonelabs.org/zonelabs/b...l&message.id=6
>
> ju.c
>
> > ZoneAlarm & KB951748 - Where's my internet?
> >
> > My solution that actually works after trying all those below and on
> > every other post, and you can keep all your other settings alone:
> >
> > 1. Open ZoneAlarm's 'Firewall' tab.
> > 2. Click the 'Custom' button under 'Internet Zone Security'.
> > 3. On the 'Internet Zone' section scroll down to 'Allow outgoing UDP
> > ports'.
> > 4. Check it and enter "80-3000", click 'Apply' button.
> > 5. Do the same for 'Allow outgoing TCP ports'.
> > 6. Click OK.
> >
> > * The range "80-3000" is just a guess on my part, if anyone knows a
> > better range please post it.
> >
> > Please post success or failure, thank you.
> >
> >
> > ZoneAlarm is investigating the issue with Microsoft update KB951748:
> > http://forum.zonelabs.org/zonelabs/b...hread.id=52785
> >
> > To solve this, just reset the ZA database and the ZA will be "fresh"
> > as when it was first installed:
> > http://forum.zonelabs.org/zonelabs/b...ssage.id=52727
> >
> > ZoneAlarm Customer Care How to Perform a Clean Install:
> > http://www2.nohold.net/noHoldCust542...n_install.html
> >
> > MS update KB951748 and ZoneAlarm:
> > http://www.dslreports.com/forum/r207...eAlarm-PROBLEM
> >
> > *** Where the real blame lies!!!
> > Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
> > Patch Released:
> > http://securosis.com/2008/07/08/dan-...atch-released/
> >
> > To find out if the DNS server you use is vulnerable:
> > http://doxpara.com/
> >
> >
> > ju.c
> >
> >
> >
>

In article <>,
says...
>
>
>ZoneAlarm & KB951748 - Where's my internet?
>
>My solution that actually works after trying all those below and on
>every other post, and you can keep all your other settings alone:
>
>1. Open ZoneAlarm's 'Firewall' tab.
>2. Click the 'Custom' button under 'Internet Zone Security'.
>3. On the 'Internet Zone' section scroll down to 'Allow outgoing UDP
>ports'.
>4. Check it and enter "80-3000", click 'Apply' button.
>5. Do the same for 'Allow outgoing TCP ports'.
>6. Click OK.
>
>* The range "80-3000" is just a guess on my part, if anyone knows a
>better range please post it.
>
>Please post success or failure, thank you.
>
>
>ZoneAlarm is investigating the issue with Microsoft update KB951748:
>http://forum.zonelabs.org/zonelabs/b...hread.id=52785
>
>To solve this, just reset the ZA database and the ZA will be "fresh" as
>when it was first installed:
>http://forum.zonelabs.org/zonelabs/b...ssage.id=52727
>
>ZoneAlarm Customer Care How to Perform a Clean Install:
>http://www2.nohold.net/noHoldCust542...n_install.html
>
>MS update KB951748 and ZoneAlarm:
>http://www.dslreports.com/forum/r207...eAlarm-PROBLEM
>
>*** Where the real blame lies!!!
>Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
>Patch Released:
>http://securosis.com/2008/07/08/dan-...n-dns-massive-
multivendor-patch-released/
>
>To find out if the DNS server you use is vulnerable:
>http://doxpara.com/
>
>
>ju.c
>
The official temp workarounds from ZA are here:

http://download.zonealarm.com/bin/fr...cessIssue.html

whosbest54
--
The flamewars are over...if you want it.

Unofficial rec.audio.opinion Usenet Group Brief User Guide:
http://www.geocities.com/whosbest54/

Unofficial rec.music.beatles Usenet Group Brief User Guide:
http://www.geocities.com/whosbest54/rmb.html

You don't want to open up ports as it opens up a can of worms. Your
suggestion opens around 2920 TCP and UDP ports.

Take ZoneAlarms section option. It is the most secure.

"ju.c" wrote:

> ZoneAlarm & KB951748 - Where's my internet?
>
> My solution that actually works after trying all those below and on
> every other post, and you can keep all your other settings alone:
>
> 1. Open ZoneAlarm's 'Firewall' tab.
> 2. Click the 'Custom' button under 'Internet Zone Security'.
> 3. On the 'Internet Zone' section scroll down to 'Allow outgoing UDP
> ports'.
> 4. Check it and enter "80-3000", click 'Apply' button.
> 5. Do the same for 'Allow outgoing TCP ports'.
> 6. Click OK.
>
> * The range "80-3000" is just a guess on my part, if anyone knows a
> better range please post it.
>
> Please post success or failure, thank you.
>
>
> ZoneAlarm is investigating the issue with Microsoft update KB951748:
> http://forum.zonelabs.org/zonelabs/b...hread.id=52785
>
> To solve this, just reset the ZA database and the ZA will be "fresh" as
> when it was first installed:
> http://forum.zonelabs.org/zonelabs/b...ssage.id=52727
>
> ZoneAlarm Customer Care How to Perform a Clean Install:
> http://www2.nohold.net/noHoldCust542...n_install.html
>
> MS update KB951748 and ZoneAlarm:
> http://www.dslreports.com/forum/r207...eAlarm-PROBLEM
>
> *** Where the real blame lies!!!
> Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
> Patch Released:
> http://securosis.com/2008/07/08/dan-...atch-released/
>
> To find out if the DNS server you use is vulnerable:
> http://doxpara.com/
>
>
> ju.c
>
>
>
>

That's one reason I wasn't too keen on doing it myself, Gis.

"Gis Bun" wrote:
> You don't want to open up ports as it opens up a can of worms. Your
> suggestion opens around 2920 TCP and UDP ports.

See related conversations in this forum:
http://forum.zonelabs.org/zonelabs/board?board.id=cfg

Keep an eye on this thread:
http://forum.zonelabs.org/zonelabs/b...ssage.id=52785

Although the fix here should work:
http://forum.zonelabs.org/zonelabs/b...ssage.id=52727

I strongly disagree with this advice:
http://download.zonealarm.com/bin/fr...cessIssue.html

Perhaps a better firewall is what's needed?
http://www.matousec.com/projects/fir...ge/results.php
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


ju.c wrote:
> ZoneAlarm & KB951748 - Where's my internet?
<snip>

I've asked this question a few times before, how is it possible to be so
dumb?

What ports are opened?


"Gis Bun" <> wrote in message
news:E7686D89-322C-4807-AE48-...
>
> You don't want to open up ports as it opens up a can of worms. Your
> suggestion opens around 2920 TCP and UDP ports.
>
> Take ZoneAlarms section option. It is the most secure.
>
> "ju.c" wrote:
>
>> ZoneAlarm & KB951748 - Where's my internet?
>>
>> My solution that actually works after trying all those below and on
>> every other post, and you can keep all your other settings alone:
>>
>> 1. Open ZoneAlarm's 'Firewall' tab.
>> 2. Click the 'Custom' button under 'Internet Zone Security'.
>> 3. On the 'Internet Zone' section scroll down to 'Allow outgoing UDP
>> ports'.
>> 4. Check it and enter "80-3000", click 'Apply' button.
>> 5. Do the same for 'Allow outgoing TCP ports'.
>> 6. Click OK.
>>
>> * The range "80-3000" is just a guess on my part, if anyone knows a
>> better range please post it.
>>
>> Please post success or failure, thank you.
>>
>>
>> ZoneAlarm is investigating the issue with Microsoft update KB951748:
>> http://forum.zonelabs.org/zonelabs/b...hread.id=52785
>>
>> To solve this, just reset the ZA database and the ZA will be "fresh"
>> as
>> when it was first installed:
>> http://forum.zonelabs.org/zonelabs/b...ssage.id=52727
>>
>> ZoneAlarm Customer Care How to Perform a Clean Install:
>> http://www2.nohold.net/noHoldCust542...n_install.html
>>
>> MS update KB951748 and ZoneAlarm:
>> http://www.dslreports.com/forum/r207...eAlarm-PROBLEM
>>
>> *** Where the real blame lies!!!
>> Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
>> Patch Released:
>> http://securosis.com/2008/07/08/dan-...atch-released/
>>
>> To find out if the DNS server you use is vulnerable:
>> http://doxpara.com/
>>
>>
>> ju.c
>>
>>
>>
>>

Not too bright, are we?

"Roger Overunder" <> wrote in
message news:086259E7-4CC5-47FF-8C3C-...
> That's one reason I wasn't too keen on doing it myself, Gis.
>
> "Gis Bun" wrote:
>> You don't want to open up ports as it opens up a can of worms. Your
>> suggestion opens around 2920 TCP and UDP ports.
>