Thanks in advance for any response.

I am currently upgrading our entire network from NT 4.0 domain/Novell/multi .V. environment to 2000 running AD. Incorporated in this is a mirgration from IMS EMWACS to Exchange 2000 (native)/cluster/compaq/hp DL380. All branch offices will have DC's in same tree (no CD's) and sync via VPN WAN link. All bandwidth via ATM and DS3 lines w/bridge site link/site link. Here in lies the problem. I am upgrading DNS (all NT servers) from NT 4.0 to 2000 running AD but I think 2000 still sees the servers (done via clone) as legacy servers with 4.0 attributes, this is killing me. Can login to new domain using credentials that are NON-EXISTENT and actually manage ADS via this account, here is the stinker, can't login to local machine (no option on start-up) and paired with this oddity is the fact that I cannot manage anything locally. I have ran DSP and granted God rights to the Domain admin on local machine to no avail. I bumped it down to a Member server and reinstalled 2000 and ran DCPROMO again to no avail. I receive a multitude of errors while trying to incorporate the DNS host files onto server. Account identifier doesn't recognize any local account on the server. Pre-upgrade I made absolutely sure that the Domain admin doing the administering was also an administrator locally ( source SAM/Event ID - 16650) / source USERENV/eVENT id 1000/VALUE 1326 and on and on and on. If anyone has gone through this before and can provide any guidance regarding this matter I will GREATLY APPRECIATE IT. I have exactly 14 hours to have this done. :twisted: