Re: Update KB951748 causes no connect to internet, anyone have thi

Malke, thanks for the effort to reproduce this here. However, it does not
work for all users. There is more detailed conversation going on at
http://forums.zonealarm.org/zonelabs/board/message?board.id=win_za_msgs&message.id=18667

All in all, a major snafu from MS to not let firewall makers in on the plan.
SOME paranoid people might wonder about MS's efforts to takeover the
firewall market ....


Here's a workaround from one of the users ("Oldsod") on the ZA forums:

*****
If the windows update changed the usual needed files for
networking/internet, then the ZA will not see the changes and continue to
use the previously known files and ignore the newer files. Even though the
file names and locations are still the same from before, now the file size
and checksums no longer match.

To solve this, just reset the ZA database and the ZA will be "fresh" as when
it was first installed:

# Boot your computer into the Safe Mode
# Navigate to the c:\windows\internet logs folder
# Delete the backup.rdb, iamdb.rdb, *.ldb and the tvDebug files in the
folder
# Clean the Recycle Bin
# Reboot into the normal mode
# ZA will be just like new with no previous settings or data

Once this is finished, reboot back into the normal mode and in the new
network found windows, set the new network to Trusted.
Then do this to ensure the ZA is setup properly:

Make sure your DNS and DHCP server IP's are in your Firewall's Trusted zone.
Finding DNS and DCHP servers, etc

1. Go to Run and type in command and hit 'ok', and in the command then type
in ipconfig /all then press the enter key. In the returned data list will
be a line DNS and DHCP Servers with the IP address(s) listed out to the
side. Make sure there is a space between the ipconfig and the /all, and the
font is the same (no capitals).
2. In ZA on your machine on the Firewall, open the Zones tab, click Add and
then select IP Address. Make sure the Zone is set to Trusted. Add the DNS
IP(s) .
3. Click OK and Apply. Then do the same for the DHCP server.
4. The localhost (127.0.0.1) must be listed as Trusted.
5. The Generic Host Process (svchost.exe) as seen in the Zone Alarm's
Program's list must have server rights for the Trusted Zone.
Plus it must have both Trusted and Internet Access.
*****

Or you could uninstall Zone Alarm and use something better since ZA has
gotten quite bloated and invasive over the years, regularly causing issues.
The Windows Firewall built into XP and Vista is adequate for most people.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
FAQ - http://www.elephantboycomputers.com/#FAQ


.

Relevant Pages

  • Re: W2k3 server and DNS
    ... I do not have a Firewall on any of the machines, ... The DNS domain name of AD ... Do the SRV records exist under your zone name? ...
    (microsoft.public.windows.server.dns)
  • For those using Zome Alarm having problems since windows update
    ... If you use ZoneAlarm you will lose your Internet connection after installing the latest security updates from MS - KB951748 in particular. ... Make sure your DNS and DHCP server IP's are in your Firewall's Trusted zone. ...
    (uk.people.silversurfers)
  • Re: Resolving internal and external DNS records
    ... > Our firewall will not allow our internal computers to resolve our external ... > So if my internal users type in www.aaa.com, ... If you don't actually have a Shadow DNS setup then ... you need to add a NEW version of your zone externally. ...
    (microsoft.public.win2000.dns)
  • Re: KB951748/Zone Alarm - Loss of connectivity
    ... Have you tried rebuilding the winsock from a Command Prompt with ZA *completely* disabled and the native XP firewall enabled or, just disconnect from the net while doing the following? ... As is the decision to install Zone Alarm and continue using it when other free alternatives are available that are not toxic to the OS. ... Make sure your DNS and DHCP server IP's are in your Firewall's Trusted zone. ...
    (microsoft.public.windowsxp.general)
  • Re: PIX 501 Firewall and DNS
    ... internet without hardcoding the ISP's DNS on the workstation. ... I think it is something very simple that was overlooked when the firewall ... the technician that installed it set it as the DHCP server. ... >> hard code our ISP's DNS address on all our workstations and our Domain ...
    (comp.security.firewalls)
Loading