OK, mabye not itslef, but for some reason one of my domain controllers has renamed itself.
Bit of background:
I am currently testing an inter-forest migration, and i ran the ADMT 3.0 tool on the DC yesterday. The process got stuck, so i rebooted the server
since then the server has renamed itself to NO.domain.name, DNS still sees the orginal name (i.e. i can ping the orginal name, and RDP)but no directory services are working, as AD cannot see the server
The problem is that the server is the PDC, and the domain master, plus the TS licesning server!
I have had to seize all of the roles from the server and transfer to a working server, and i now want to dcpromo to demote to a member server, but it is looking for the new name of NO instead of the original server name...
Any ideas? this is very strange, and i'm worried that i don't know how or what happened to rename a 2000 DC!
Cheers
E
Bit of background:
I am currently testing an inter-forest migration, and i ran the ADMT 3.0 tool on the DC yesterday. The process got stuck, so i rebooted the server
since then the server has renamed itself to NO.domain.name, DNS still sees the orginal name (i.e. i can ping the orginal name, and RDP)but no directory services are working, as AD cannot see the server
The problem is that the server is the PDC, and the domain master, plus the TS licesning server!
I have had to seize all of the roles from the server and transfer to a working server, and i now want to dcpromo to demote to a member server, but it is looking for the new name of NO instead of the original server name...
Any ideas? this is very strange, and i'm worried that i don't know how or what happened to rename a 2000 DC!
Cheers
E