Should I and how do I, run Active Directory into my DMZ?


My level of knowledge on Firewalls and Active Directory is pretty basic and I would appreciate some expert advice please.

I am trying to allow my windows 2003 & 2000 servers in my DMZ to connect to the 2003 Domain Controller in the LAN but I am getting errors with regards to the secure connection failing and there being no logon servers available:

Event ID: 5719
This computer was not able to set up a secure session with a domain controller in domain <DOMAIN> due to the following:
There are currently no logon servers available to service the logon request.  

Event ID: 1053
Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

Firstly, is it good practice to allow Active Directory through into the DMZ?

I have opened up the following ports on the Firewall (Fortigate 60) as per KB 179442 (

Client Port(s)      Server Port      Service
137/UDP      137/UDP      NetBIOS Name
138/UDP      138/UDP      NetBIOS Netlogon and Browsing
1024-65535/TCP      139/TCP      NetBIOS Session
1024-65535/TCP      42/TCP      WINS Replication

Client Port(s)      Server Port      Service
1024-65535/TCP      135/TCP      RPC
1024-65535/TCP      1024-65535/TCP      LSA RPC Services (*)
1024-65535/TCP/UDP      389/TCP/UDP      LDAP
1024-65535/TCP      636/TCP      LDAP SSL
1024-65535/TCP      3268/TCP      LDAP GC
1024-65535/TCP      3269/TCP      LDAP GC SSL
53,1024-65535/TCP/UDP      53/TCP/UDP      DNS
1024-65535/TCP/UDP      88/TCP/UDP      Kerberos
1024-65535/TCP      445/TCP      SMB

As a test I set my Firewall to allow all through from the DMZ to the LAN and then ran a

dia sni pa dmz host' (the dmz servers IP address)

while performing an nltest /sc_reset:<DOMAIN NAME> and it passes with a success

All of the ports listed in the sniff were covered in my ports I have opened on the Firewall and I have attached this image to this question. So far so good.

Going back to the Firewall and switching off the allow all and re-running the nltest /sc_reset fails with:


and this is where I am stumped, as far as I can see I have the correct ports listed.

any advice appreciated,

LVL 14
Hedley PhillipsOwnerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The whole point of a DMZ is that it is essentially untrusted (okay SEMI trusted) and you should not allow domain traffic into it.
Saying that I can see straight off that you have missed DNS from the list of allowed ports and AD will not work without it.
What you should be doing is seeing why you need authentication traffic through the firewall and design a solution that does not require it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Hedley PhillipsOwnerAuthor Commented:

thanks for your reply.

DNS is listed there, 3rd from bottom on the 2nd list.

If domain traffic shouldn't be allowed in the DMZ then I will be happy with that and will lock all these ports back down again. I just thought that it was required and should work.

To be honest, I was looking at all the open ports and ranges and my DMZ was starting to look like a Swiss cheese with all those holes.
Whup! Yep you're right. Sorry :-)
I'm really really against allowing anything beyond the absolute basics through to a DMZ and certaibly not domain traffic. all it would take is a DMZ Server to be compromised and you've got a door into your (supposedly) secure Domain.
We had an issue where a Web Server needed domain authentication and rather than move the Server into the internal network and publish it through ISA, some bright spark thought it would be good to allow AD through to it. Suffice to say this caused nightmares AND was slated by the external Auditors
bluntTonyHead of ICTCommented:
I would definitely agree with Kieran that having a domain machine in a DMZ sort of negates the point of having the DMZ in the first place and leaves a gaping security hole. What are you trying to achieve?
Hedley PhillipsOwnerAuthor Commented:
Thanks for your help. We have followed your advice and not placed any domain members in the DMZ
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.