The ISA acts as a reverse proxy, for an outlook web access server sitting on the interal network. Lockout Gaurd needs to communicate with AD to do user accoung checking
Main Topics
Browse All TopicsGood day I have a ISA server in DMZ running Lockout Guard. The Lockout Guard need to check AD for user account status (I know this is bad !!!). Can anyone confirm the ports I need to open to the internal network . (believe it 2711-2712 and 135 for LDAP).?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The ISA is in a DMZ, and functions as a reverse proxy to the OWA server on the production network. LockoutGaurd protects OWA , in the sens that it prevents accounts in AD being lock-out when exsternal users (internet ) attemps to crack OWA passwords. It therefore needs to do LDAP query to AD to check a number account attributes for the user wanting to connect .
Does this help ?
No. The Network Relationship between the Internal Network and the DMZ Network is a specific thing,...it is either NAT'ed or it is routed. Since this is a probably a Single Nic ISA "in the DMZ" then this "relationship" is totally effected and controled by whatever firewall you have between the LAN and the Internet.
Since your ISA is "in the DMZ" it is probably a Single Nic ISA,...this means that you have another Firewall between the LAN and the Internet. This means that this is the Firewall that has to allow the LDAP to pass to the Internal LAN. I cannot help with that, my familiarity is only with ISA..
Then after this firewall "allows" it,...then the ISA itself has to allow it on top of that. For a Single Nic ISA the rule would be:
From: LocalHost
To: Internal (yes, internal)
Protocol: LDAP
Users: "All Users"
If the network relationship between DMZ and the Internal LAN is "routed",...then the ISA's Internal Network defintion will need to include the LAN's IP Range inspite of the fact that the ISA is in the DMZ.
If the network relationship between DMZ and the Internal LAN is "NAT'ed",...then the ISAs Internal Network defintion would not need altered. The Firewall would do the "publishing" and the ISA would treat the Firewall as if it was the "LDAP Service".
That probably sound really confusing, but that is the best I know how to lay it out.
Business Accounts
Answer for Membership
by: pwindellPosted on 2009-08-21 at 14:04:02ID: 25155819
What is the ISA Network Relationship between the Internal Network and the DMZ Network?