MS Firewall

  • Thread starter Thread starter Guest
  • Start date Start date
-----Original Message-----
does anyone have a problem turning on the firewall after
this beta install
.
Click to expand...

try this "netsh Winsock reset"

if you find anything else, let me know (e-mail address removed)
 
Please send this link
http://support.microsoft.com/kb/892350

or

RESOLUTION
Windows XP SP2
To resolve this problem if you are running Microsoft Windows XP Service Pack 2
(SP2), follow these steps: 1. Rebuild the Winsock LSP chain. To do this, follow
these steps: a. Log on to the Microsoft Windows XP workstation as an
administrator.
b. Click Start, click Run, type cmd, and then click OK.
c. At the command prompt, type the following, and then press ENTER:
netsh Winsock reset
When the program is finished, you will receive the following
message:
Successfully reset the Winsock Catalog. You must restart the machine
in order to complete the reset.
If you receive this message, go to step 1d.

If you are not logged in as an administrator, you will receive the
following error message:
Unable to reset the Winsock Catalog. Access is denied.
If you receive this message, log off the computer, and then log back
on by using an account with Administrator access. Typically, the first user
account that was created has Administrator access. Then, repeat steps 1b and 1c.
d. Restart your computer.

2. Test each of your third-party programs that are known to use LSPs.
3. Reinstall any malfunctioning third-party programs that are known to use
LSPs.

Windows XP, Windows XP SP1, and Windows 2000
To resolve this problem if you are running the release version of Microsoft
Windows XP, Microsoft Windows XP Service Pack 1 (SP1), or Microsoft Windows
2000, follow these steps: 1. Rebuild the Winsock LSP chain. To do this, follow
the steps in the "Resolution" section of the following Microsoft Knowledge Base
article:
817571 You receive an "An operation was attempted on something that is not
a socket" error message when you try to connect to a network
2. Test each of your third-party programs that are known to use LSPs.
3. Reinstall any malfunctioning third-party programs that are known to use
LSPs.
 
Back
Top