Why is it that when I set the "Secure Server" IPSec policy for the domain controller policy, my secondary domain controller won't talk to the main one?
Basically I installed Windows 2000 on the big machine in the server room, as the first DC/rid/whatever machine ... then I brought up a second one. This one is sitting on my desk. When I set the default IPSec policy to "Secure Server" ... I can no longer access the group policy?
So far there are on ly these two DC servers in the domain ...
I wanna experiment with this IPSec thing.
I don't see how these two DC's wouldn't be trusting each other already ...? If thats the case how do I establish a kerberos trust between the two so they'll talk?
Thanks ...
Windows 2000 IPSec question ...
- W_I_Z_K_I_D
- Regular Member
- Posts: 363
- Joined: Sun Jun 10, 2001 9:33 am
- Location: !!!Your Computer-You Just Dont Know It YeT!!!
YeP What He Said.... 
!!!What Man Can Make
Man Can Brake!!!
Windows XP ( Service Pack 2 )
Pentium 4 (3) GHz
2.00 GB of RAM
** Zone Allarm Pro
** AVG Anti Virus
** Cookie Wall
** Pop Up Stopper
** Spy Bot
** Spy Ware Blasster
** Add Aware se Pro
** Ccleaner
** Clean Up
** Port Bloacker
** Tweek UI WIn XP
** Port Scanner
Dialup 56k
DialUp-Syd.IPrimus....56k(Motorola internal Modem)
Man Can Brake!!!
Windows XP ( Service Pack 2 )
Pentium 4 (3) GHz
2.00 GB of RAM
** Zone Allarm Pro
** AVG Anti Virus
** Cookie Wall
** Pop Up Stopper
** Spy Bot
** Spy Ware Blasster
** Add Aware se Pro
** Ccleaner
** Clean Up
** Port Bloacker
** Tweek UI WIn XP
** Port Scanner
Dialup 56k
DialUp-Syd.IPrimus....56k(Motorola internal Modem)