We have a small domain at the office running on a 32bit windows server 2003 (server1.domain.local). We have purchased a new server with windows 2008 R2 64bit (server2.domain.local) and plan to make it domain controller.
I followed one of many guides on the internet and executed all the necessary steps:
- On the old W2003 server:
ADPREP32 /Forestprep
,ADPREP32 /domainprep
andADPREP32 /domainprep /gpprep
- On the new server I ran DCPROMO and completed the task successfully (I only got the warning regarding DNS delegation)
- After completing DCPROMO and rebooting, I transferred FSMO roles to server2.domain.local, which appears to be working correctly:
C:\Users\gseadmin>netdom query fsmo
Schema master server2.domain.local
Domain naming master server2.domain.local
PDC server2.domain.local
RID pool manager server2.domain.local
Infrastructure master server2.domain.local
The command completed successfully.
Now I tried to cut network access from server1.domain.local and whenever I try to access the "Active Directory Users and Computers" utility on server2 I get an error saying the domain cannot be found. And this is the result from netdom:
C:\Users\gseadmin>netdom query fsmo
The specified domain either does not exist or could not be contacted.
The command failed to complete successfully.
I don't understand - shouldn't by now server2.domain.local be able to answer AD queries by itelf? Why does it keep looking for the old server?
dcdiag /s:server2
say?