XP SP2 firewall blocked our DNS Suffix GPO

OK, here is the situtation.  We use a GPO to update client's DNS Suffix.  After installing XP SP2, the firewall enabled (by default) and would block the GPO from being applied.  After we realized what exactly was blocking the GPO, we opened the Firewall for the LAN connection (left the wireless completed enabled).

Now we're thinking about what will happen when SP2 is rolled out to our entire environment.  
Is there any way to apply a pre-emptive GPO that will not allow this firewall from being enabled.  OR better yet, is there any effective way to leave the firewall enabled and get around this mess?  Please keep in mind that we still have some Win2K workstations as well, so the solution can not have any ill-affects on them.

Thank you for any help!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris DentPowerShell DeveloperCommented:

There are policies shipped with Service Pack 2 that will allow you to disable (or control) the Firewall.

To access them load up Group Policy Management Console on a Windows XP SP2 computer.

You can get GPMC from:


Then create a new policy on that machine. It will load with the default files from xp, which include about 700 additional policies for you to set.

To disable the Firewall component in the Policy go to:

Computer Configuration
Administrative Templates
Network Connections

And select

Prohibit use of Internet Connection Firewall on your DNS Domain

This will be available for anyone on your network to use, as you see fit.

One restriction with this. Although you can create the policy to include everything else on the XP Workstation the ADM Files used don't seem to be available as a seperate download. As such, when you create a policy on a Windows 2003 Server (for example) it will not include the additional policies.

Finally, you may bump into a lot of String is too long type errors when you load the Policy elsewhere. This issue can be resolved with:


Or by loading on the current version of GPMC

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
KrowtenTechAuthor Commented:
I may add a few a comments after we've been through the testing phases.

Thank you for the help!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.