Netsh Winsock Reset command fixes Windows Firewall error

There are times admins will want to run the command Netsh WinSock Reset from the command line. This command will rebuild network settings from scratch.

When a major networking error occurs in Windows XP, often the user gets nothing more than a generic warning message. A more detailed error message is usually written to the system log, which can then be used for detailed troubleshooting.

I saw one such error when a user was trying to debug a problem with a connection that had the Windows Firewall turned off. (Don't laugh. For some people, the Windows Firewall is all they have, or can afford.) When the user tried to turn the firewall back on, a generic error came up: "Windows cannot start the Windows Firewall/Internet Connection Sharing Service."

A more detailed error of Event ID 7023 was logged as: The Windows Firewall/Internet Connection Sharing (ICS) service terminated with the following error: An address incompatible with the requested protocol was used.

The MSDN database doesn't provide many details about this

    Requires Free Membership to View

error message. But user feedback shows that the error is essentially spurious, the result of a corrupted network-stack setup.

Sometimes this corruption comes about as the aftermath of a spyware cleanup, after the spyware has already done its damage and rendered the Windows Firewall useless. The error is the result of attempting to initialize the appropriate services after their setup information has been ruined, and so it doesn't generate any really useful information.

The most basic way to fix this is to run the command Netsh WinSock Reset from the command line, which will rebuild the network settings from scratch. However, if that command produces the error "Unable to reset the Winsock Catalog," you'll probably need a third-party tool like the Winsock XP Fix tool to repair everything. (Note: The original author of this tool appears to have gone offline, so the only links available are for third-party distributors.)

About the author: Serdar Yegulalp is editor of the  Windows Insight, (formerly the Windows Power Users Newsletter), a blog site devoted to hints, tips, tricks and news for users and administrators of Windows NT, Windows 2000, Windows XP, Windows Server 2003 and Vista. He has more than 12 years of Windows experience under his belt, and contributes regularly to SearchWinComputing.com and SearchSQLServer.com.

More information on this topic:

This was first published in September 2006

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.