Security Configuration Wizard kills remote DNS and DHCP management snap in's

Hi
We've just run the Security Configuration Wizard on our Windows Server 2003 DC's, and now the mmc snap in's no longer connect for DNS and DHCP.  Any ideas on what we need to turn back on?
bryorkjAsked:
Who is Participating?
 
MightySWCommented:
Yeah, turn that thing off.
0
 
MightySWCommented:
Hi, can you suggest to connect to a server and then point it to the DC?

Did it turn your firewall on?
0
 
MightySWCommented:
Also, did your MMC get updated to version 3.0?
0
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
MightySWCommented:
Oh, this is remote.  Try to reinstall the adminpak from the DC.
0
 
bryorkjAuthor Commented:
It did turn the firewall on.  I'm going to run through the SCW again and see if my tech left anything off when he configured it.
0
 
bryorkjAuthor Commented:
unfortunately we're subject to auditors, and they want them on.
0
 
MightySWCommented:
You can make exceptions on the FW right?
0
 
MightySWCommented:
As long as everything is documented with a purpose then you should be fine.
0
 
bryorkjAuthor Commented:
Found a selection in the SCW that allows the remote DHCP MMC to keep working.  Didn't find one for DNS, but it was definitely a firewall problem--turning off the firewall allowed the DNS MMC to work.  Can't leave the firewall off tho, so finally opted to control DNS through remote desktop to the server.
0
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.

All Courses

From novice to tech pro — start learning today.