Solved

Child domain LDAP queries

Posted on 2009-07-08
6
874 Views
Last Modified: 2012-05-07
I'll get to the question first.  My server, which is part of a child domain is sending LDAP requests to the primary root domain/forest controllers.  Why?  I don't want this to happen.

Here is the setup
2 total domains
Root domain/forest = abc.com
Child domain = xyz.abc.com
DC in child domain = AD1.xyz.abc.com
Another server in the child domain has ad1.xyz.abc.com as the ONLY DNS and WINS server. Of course that server is part of xyz.abc.com domain. The firewall blocks all AD communication (DNS, WINS, LDAP, RPC, Kerberos, SAM/LSA, Netbios, NTP, etc.) EXCEPT traffic between primary and child domain DC's.

Logins to child domain with primary domain accounts is slow (but successful), most likely since LDAP-UDP commumications from server are purposefully blocked.  Is it asking to much for my child DC to do ALL the authentication work?  Why are my other servers even trying to contact the root domain?  The reason I am doing this is for security but I don't know if it is a good or best practice.
0
Comment
Question by:damien1234
  • 4
  • 2
6 Comments
 
LVL 70

Accepted Solution

by:
Chris Dent earned 500 total points
ID: 24811596

Global Catalog?

Chris
0
 
LVL 1

Author Comment

by:damien1234
ID: 24813274
The DC in the child domain is a Global Catalog too.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 24814220

Are they in the same site in AD?

Chris
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 1

Author Comment

by:damien1234
ID: 24818785
So I created a new site and put the child DC in it.  I then logged on and saw a LDAP-389-UDP and a SAM/LSA-445-TCP packet dropped.  Login was successful but slow.
0
 
LVL 1

Author Comment

by:damien1234
ID: 24827100
Well, I found a white-paper from Microsoft which was specifically about how to setup DC-DC communications through firewalls AND guarantee that the clients in each Site could only authenticate with the DC in their domain. It talked about setting up IPSEC but at the end of the day my method is exactly the same except my DC-DC traffic is not encrypted... and I don't need it to be encrypted.  My firewall guarantees that ONLY the DC's can talk to each other.  Anyway this has nothing to do with the behaviour of the other servers trying to contact DC's in the other site.  If Microsoft says I am doing everything right then maybe I'm just being anal.  After all authentication works.

Critical Points:
DC's need to be GC's
If Sites are used then replication and replication traffic is ALL that matters, nothing else.

It's beautiful, NONE of my other severs can browse an AD domain other than their own!  This is exactly what I wanted to have happen!  WooHoo!
0
 
LVL 1

Author Closing Comment

by:damien1234
ID: 31602276
See my final explanation.  It's critical that the DC is a GC.  It's not as critical for the child to be in a different AD site since that really is all about replication (at least in my scenario anyway)
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

[b]Ok so now I will show you how to add a user name to the description at login. [/b] First connect to your DC (Domain Controller / Active Directory Server) SET PERMISSIONS FOR SCRIPT TO UPDATE COMPUTER DESCRIPTION TO USERNAME 1. Open Active …
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question