Re: Windows Firewall on Domain Controllers
- From: "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx>
- Date: Sun, 22 Oct 2006 13:12:42 +0200
yes
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"sprucio" <sprucio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:39B26276-3B37-44CE-813B-145A1495E030@xxxxxxxxxxxxxxxx
Have any of you guys read this article?
http://support.microsoft.com/default.aspx?scid=kb;en-us;555381&sd=rss&spid=3198
I have tried this but had no success so far.
"Jorge de Almeida Pinto [MVP]" wrote:
the firewall on a fresh installed w2k3sp1 server is NOT on by default!
it is only on during the post-security updates section. as soon as you
update the server you need to click finish and read the message stating
it
will allow inbound connections
don't use the firewall on the DC
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Ron" <rhardin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:301A5C97-58EC-426D-B43E-4891BB4E10C0@xxxxxxxxxxxxxxxx
Need input on recommended best practices. Here's what I've figured
out:
* Server 2003 defaults to Windows Firewall active.
* Domain Controller doesn't work with firewally active unless it is
manually
confgured for all the AD ports and you do some voodoo with RPC ports.
* Making a 2003 Server a Domain Controller doesn't automatically
configure
the firewall
* Turning off the firewall only fixes the problem temporarily because
some
Windows Updates automatically turn it back on (without telling you).
Assuming the above points are correct on my part, what is the best
practice
for administering the firewall on domain controllers (I have about 30
of
them
scattered all over the country)?
--
Ron Hardin, CHTP
Director of Technology
Davidson Hotel Company
.
- Follow-Ups:
- Re: Windows Firewall on Domain Controllers
- From: Jorge Silva
- Re: Windows Firewall on Domain Controllers
- Prev by Date: Re: Re: AD Command Line Tools
- Next by Date: Add a Windows 2003 backup domain controller (BDC) to 2000 AD
- Previous by thread: Re: Supportet/ Unsupported Objects import
- Next by thread: Re: Windows Firewall on Domain Controllers
- Index(es):
Relevant Pages
|
