Tue Apr 24, 2007 6:49 pm
winxp2000 has the answer..
Things to do:
Use 2003 / 2000 server's DHCP and DNS servers (keep AD happy or else)
Set DHCP server to update DNS. (you also want the client to do this, but bootp devices wont)(Yes it does this)
Setup DHCP Proxys on the MT to forward the DHCP requests to NT servers.
USE NT as the domain time source.
USE MT as the timesource for the AD computer (use third party code to sync the global catalog server to the MT)
sync the MT to public NTP servers (Keep AD in timesync or it will fill your logs and boy will it...)
USE NT DHCP reservations for static address devices ie printers, secondary servers.
The above WILL save you alot of headachs... (I have had them for you !)
You will probalby want to use "SPLIT DNS" for any public DNS..
DO NOT... DO NOT... expose your internal DNS server for any reason to the outside world unless you want AD to get hacked / crashed...
(Your inside / outside address for published resources is probaly different anyway and would create a management issue)
This works for me.....
7 internal networks, 100 workstations, 20+ servers 20+ printers
2 remote sites. 7 wireless networks.
All in AD, All accessable by name..
I hope this helps.....