I have a problem with Domain Controller when its on dmz and client of DC on inside,i ve configured an access-list to permit conversation between DC and Clients but they cant join to domain.
The DC ip address is 172.16.1.9 which i nat it to 10.9.0.15 ,and users subnet is 10.9.0.0/16 ,i also define dhcp server on DC and clients can take their ip address from dhcp but they can't join to domain.
I cannot see any acl entry for port 53 udp/tcp this port is for DNS and allow port 500 and 50 and u hav to allow ports 88 tcp/udp for kerberos for time being u can allow tcp/udp echo port check out if this works then rate my reply if not we will try somethinf else
If u have allowed any any in ur acl then it should work now i am suspecting ur DC for testing purpose u can take one client and assign IP of ur DMZ and place this client on DMZ and then u try to add this client to ur domain if this works fine then we hav to look at ur config again if this does not works then u can check ur DC
If you don't have an access-list applied to your inside interface, going to the DMZ should be allowed on all ports/protocols, so it shouldn't be an access list issue.
Make sure you've disabled nat unless you need it :
By default, you need nat from a high-->low interface unless you turn it off. The static doesn't really cover that (you have to tell the pix what the ip addresses on the inside will be when they are on the dmz).
Also, make sure when they are getting their DHCP address from the server that they are getting the *translated* address as the WINS server, not the real one. I don't know if this would be an issue - are you not routing the DMZ network internally?
Please rate this message if it answered some or all of your question/issue.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...