Re: Chanigin IPs on DCs
- From: "Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx>
- Date: Thu, 31 Jan 2008 07:54:53 -0600
If your dc is hosting dns make sure that all of your clients are updated
otherwise they won't be able to gain access to AD resources that require the
dc (Like authenticating).
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim in Arizona" <tiltowait@xxxxxxxxxxx> wrote in message
news:eFuF2X3YIHA.5028@xxxxxxxxxxxxxxxxxxxxxxx
Is there anything I should know when it comes to reassigning an IP to a
domain controller?
I've come into an organization where their DCs (two of them) are not part
of the internal network (192.168.1.x) but have public facing IPs instead.
I have set up ISA 2006 (just today) and find that when I set the primary
rule to allow outbound web requests to authenticated users, no one can get
out. Once I set the rule to all users, everything is good to go but in
doing so I lose the functionality of ISA that I need. I have a feeling
that if I bring the DCs into the internal network (and get rid of their
external IPs), then authentication for clients should occur properly.
Can someone give me an idea of what it would take to reassign IPs to the
DCs?
TIA,
Jim
.
- References:
- Chanigin IPs on DCs
- From: Jim in Arizona
- Chanigin IPs on DCs
- Prev by Date: Re: 2003 SP2 to 2003 SP2 R2 on a forest root DC
- Next by Date: Re: How to add a container to an OU
- Previous by thread: Re: Chanigin IPs on DCs
- Next by thread: How to add a container to an OU
- Index(es):
Relevant Pages
|
Loading