We currently run 4 Windows 2003 domain controllers on our network(s), all 4 of which are on different public networks (we own several IP blocks as we are an ISP). We'd like to place one of the DCs behind our Sonicwall to serve as a DC/global catalog for al of the servers within NAT'ed environment, as we've run into odd issues mapping drives, etc. with the servers behind the firewall (obviously this is caused by DNS issues). Additionally, we'd like this DC to act as an "internal" DNS server for the NAT'ed network behind the firewall. The problem we've faced with DNS is that our NAT'ed servers publish their private IP addresses on the public DCs; we'd like to set up a configuration where our NAT'ed servers publish ONLY to the internal/NAT'ed DC, and the public addresses that have been set up for IP forwarding (behind the firewall) are published to the public DCs (running DNS).
I guess I'm just looking for tips/advice for how to best go about running a single Windows 2003 domain across both public and private networks with regards to the situation above. Thanks in advance for any input. - Chris ------------------------------------------ Chris Gauch Systems Administrator Digicon Communications, Inc. [EMAIL PROTECTED] List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
