Win2000 Server authentication from DMZ

[BeanBoy22]

I've been having a great deal of difficulty getting a server in our DMZ to authenticate/jive with our domain that is housed on the internal network. I've researched out the ports and IOS methodology but I'm still getting packets denied from the server on the DMZ 192.168.2.5 to the internal domain controller 192.168.1.10. I was hoping one of you might be so kind as to review my config and let me know what I am doing wrong. Any help is greatly appreciated.

P.S. For several reasons I am not interested in putting the server internal or various other solutions, I am looking for help with this method only.

DMZ 192.1.2.0 255.255.255.0 (contains 1 Exchange Server)
Inside 192.1.1.0 255.255.255.0 (Network including DC)
Outside (extraneous here)

PIX Version 6.1
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 webdmz security50
enable password XXXXXXX
passwd XXXXXXX
hostname fexample(1)
domain-name example.org
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 1720
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
no names
access-list dmz_in permit tcp any host 204.100.100.1 eq www
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 135
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 139
access-list dmz_in permit udp host 192.1.2.5 host 192.168.1.10 eq netbios-n
s
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 137
access-list dmz_in permit udp host 192.1.2.5 host 192.168.1.10 eq netbios-d
gm
access-list dmz_in permit udp host 192.1.2.5 host 192.168.1.10 eq domain
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 88
access-list dmz_in permit udp host 192.1.2.5 host 192.168.1.10 eq 88
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq domain
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 389
access-list dmz_in permit udp host 192.1.2.5 host 192.168.1.10 eq 389
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 445
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 3268
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 1026
access-list dmz_in permit udp host 192.1.2.5 host 192.168.1.10 eq 1026
access-list dmz_in permit tcp host 192.1.2.5 host 192.168.1.10 eq 123
access-list smtp permit tcp any host 204.100.100.6 eq smtp
pager lines 24
logging on
logging buffered warnings
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
mtu outside 1500
mtu inside 1500
mtu webdmz 1500
ip address outside 204.100.100.245 255.255.255.240
ip address inside 192.1.1.7 255.255.255.0
ip address webdmz 192.1.2.20 255.255.255.0
ip verify reverse-path interface outside
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 204.100.100.150
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) 204.100.100.6 192.1.1.10 netmask 255.255.255.255 2
55 0
static (webdmz,outside) 204.100.100.1 192.1.2.5 netmask 255.255.255.255 0 0
static (inside,webdmz) 192.1.1.10 192.1.1.10 netmask 255.255.255.255 0 0
static (inside,webdmz) 192.1.2.5 192.1.2.5 netmask 255.255.255.255 0 0
access-group smtp in interface outside
conduit permit tcp host 204.100.100.6 eq smtp any
conduit permit tcp host 204.100.100.1 eq

http://www any

established tcp 135 0 permitto tcp 1024-65535 permitfrom tcp 0
route outside 0.0.0.0 0.0.0.0 204.100.100.2 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si
p 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
http server enable
http 192.1.1.135 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community XX
no snmp-server enable traps
floodguard enable
no sysopt route dnat
telnet 192.1.1.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
terminal width 80
Cryptochecksum:XXXXXXXXXXXXXXXXXXX
: end
[OK]

204s are external IP addresses, the rest are internal or DMZ

-Beanboy

 

[yizhar]

HI.

I suggest that you configure the Exchange server as a DC+GC in a different site, and then configure Active Directory replication over SMTP and setup SMTP connectivity between the sites.

Just remember that whatever method you use - if the Exchange server in DMZ is compromised and has access to Active Directory, this means that your whole internal network is compromised.
I mean - if an attacker will be able to play with your GPO or logon script...

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[fe0]

I am having the same problem as BeanBoy...I have 2 servers (1 email server and a reg. file server) in the DMZ of a PIX520, 1 NT and 1 2000. I did a AD/2000 migration of our domain controller from NT, and now the servers in the DMZ cannot authenicate to the DC. I put in all the conduit statements needed by 2000 but it still doesnt work. All machines on the inside work fine. Also, i can ping across to all the machines and also resolve domain names using ping -a etc, cleared arp cache and Xlate as well. When the DC was a NT machine everything worked. Any help is appreciated.

 

[yizhar]

HI fe0.

If the pix is blocking any traffic, you can see it in the syslog messages (levels3+4). This will give you important troubleshooting info and will help you find if the problem is more related to the pix or to the OS.

You can also temporarly connect the DMZ server to the internal network with internal ip address, make sure that you can connect to the domain without the pix in the way - making sure that OS issues are fixed, and then put it back in DMZ and work on pix and routing issues.
I'm not saying that this is the recommended nor only way to go for troubleshooting, but it is an option.

And of course - Event viewer on the machines. You did look there, right?

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[scarcjm]

bind access-list dmz_in to dmz interface.

ex: access-group dmz_in in interface webdmz