J
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/board/message?board.id=cfg&thread.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/board/message?board.id=cfg&message.id=52727
ZoneAlarm Customer Care How to Perform a Clean Install:
http://www2.nohold.net/noHoldCust542/Prod_1/Articles55646/clean_install.html
MS update KB951748 and ZoneAlarm:
http://www.dslreports.com/forum/r20759839-MS-update-KB951748-and-ZoneAlarm-PROBLEM
*** Where the real blame lies!!!
Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
Patch Released:
http://securosis.com/2008/07/08/dan...ue-in-dns-massive-multivendor-patch-released/
To find out if the DNS server you use is vulnerable:
http://doxpara.com/
ju.c
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/board/message?board.id=cfg&thread.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/board/message?board.id=cfg&message.id=52727
ZoneAlarm Customer Care How to Perform a Clean Install:
http://www2.nohold.net/noHoldCust542/Prod_1/Articles55646/clean_install.html
MS update KB951748 and ZoneAlarm:
http://www.dslreports.com/forum/r20759839-MS-update-KB951748-and-ZoneAlarm-PROBLEM
*** Where the real blame lies!!!
Dan Kaminsky Discovers Fundamental Issue In DNS: Massive Multivendor
Patch Released:
http://securosis.com/2008/07/08/dan...ue-in-dns-massive-multivendor-patch-released/
To find out if the DNS server you use is vulnerable:
http://doxpara.com/
ju.c