Thanks.

I have no problem to define ACL. The main question was about windows domain. I don't know if active directory requires anything special to allow on pix.

Or it is enough to allow standard windows ports - 138, 139, 445?

Vladislav

This document might help out with your configuration task.

http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806de37e.shtml#diag

Thanks.

I know this document, but it is about accessing VPN users. There is nothing about my question.

Vladislav

If you are concerned about domain controllers then you should look at microsoft site.

If you have member server in dmz and dc in inside network then you have to enable traffic for following ports:

• Kerberos ports (88/tcp, 88/udp) used to perform mutual authentication between the member server and the domain controller. Kerberos traffic needs to be allowed in addition to the possible application specific traffic.

• DNS ports (53/tcp, 53/udp) used for name lookups.

• LDAP ports (389/udp, 389/tcp or 636/tcp for SSL) used for locator pings.

• Microsoft-DS traffic (445/tcp, 445/udp).

All neccessery data can be found here:

Active Directory in Networks Segmented by Firewalls

http://www.microsoft.com/downloads/details.aspx?FamilyID=c2ef3846-43f0-4caf-9767-a9166368434e&displaylang=en

I hope that you can solve problem now. :)

Thanks, very helpful document. There is one very important information for me:

Note

Active Directory functionality is not supported over a router that has Network Address Translation (NAT) enabled. The configuration recommendations in this paper apply only to non-NAT environments.

So in my scenario I have to disable NAT between DMZ and INSIDE.

Vladislav

You can set NAT like this.

hostname(config)#static (inside,dmz) 10.1.1.2 10.1.1.2 netmask 255.255.255.0

This way you will NAT complete inside network to dmz but with same address range. I have seen scenarios that work this way.