Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 490
  • Last Modified:

Applying IPSec to Domain Controllers

I need to secure DOmain controllers 2003 by using IPSec. I have read in the following link:
http://support.microsoft.com/kb/254728
that Kerberos and some other traffic is not securing, I wonder if this applies only to windows 2000 domain controller.
I also need to exempt RDP from windowx XP to domain controllers 2000, so that I can remote to the domain controllers.
any idea on how to configure that?

Thanks
0
jskfan
Asked:
jskfan
  • 6
  • 5
1 Solution
 
bluntTonyCommented:
The problem you have provided a link to only applies to Windows 2000.
How would you like to secure the Domain Controllers? All comms to and from the server?
The simplest way for you would be to use the pre-set 'Secure Server (Require Security)' policy. This will demand that all clients have to use the 'Client (Respond Only)' policy. This setup will make the two machines negotiate the most secure mutually agreeable level of security.
Using these two pre-set policies will keep thing simple. As long as your clients are configured properly, then you will be able to RDP into the DC while it is secured with IPSEC.
0
 
jskfanAuthor Commented:
I have configured the IPSec through GPO and linked it to the Domain Controllers OU.
If I try to create another IPsec policy for servers OU, it won't let me assign both IPSec policies, it will assign just one.
SO how do I create 2 IPSec policies , one to Domain Controllers OU and one to Servers OU?
0
 
bluntTonyCommented:
I see no reason why you shouldn't be able to assign to IPSEC policies to separate OUs.

Are either of these OUs child/parent of each other? Where exactly did you link your GPO? Directly to the OUs in question?

I have previously applied different IPSEC policies to separate OUs with no conflicts.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
jskfanAuthor Commented:
if you create a GPO for another OU and go to computer configuration/ security settings/ IPSec....
on the right pane the IPsec policy you set up reviously will showup there, even though you are setting up a GPO to a  completeky different OU.
0
 
jskfanAuthor Commented:
bluntTony:I see no reason why you shouldn't be able to assign to IPSEC policies to separate OUs.

did you try it?
0
 
bluntTonyCommented:
Yes, I have tested this. I applied the 'Secure Server' policy to the Domain Controllers OU, and the 'Client' policy to a separate OU holding some computer accounts.

It is true that you can only have one IPSEC policy at the same level (i.e. policies will not merge, one will overrule the other), but as long as one OU isn't inheriting both GPOs you should be able to do this.
0
 
jskfanAuthor Commented:
I don't know how you did it. But even if I go to another OU /Right click /properties/Group policy and select new then create a new policy /edit /windows settings/security settings /IP Security Policies on Active Directory(Mydomainame.com)
on the right pane I will still see the previous policy I have created for the Different OU.
0
 
bluntTonyCommented:
Have you set up your own IPSEC policy? Are you saying that when you create a new GPO, the policy is listed AND it is ticked green (i.e. it's assigned)?

If it's just listed, it doesn't mean it's been assigned. You have to select the policy, and select 'Assign' for it to apply.
0
 
jskfanAuthor Commented:
I will take a llok at it later when I remote to the Network.

As of RDP I fixed it. I was unable to RDP to my DC because it's  a little bit tricky the IP filter List/Protocl.
I should have type 3389 in the From this port field To any port. Indtead I select from any port to this port 3389.
so I just swapped the settings and managed to RDP.
But the File Replication is not working either. For instance if you create a file under logon share in one DC it does not replicate to the Netlogon share in the other DC. I opened port TCP/UDP135 and TCP random port 50000 but still didn't work. I am not sure if I need to tweak a registery to make it know about the port 50000.
0
 
jskfanAuthor Commented:
sorry fir the typos
0
 
bluntTonyCommented:
I think that you'll need to open more ports than that.

I'll post a response about replication in your other post about the subject.

Tony
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now