U
Unhappy MacbbokOwner
Hello -
long ago we upgraded our only domain controller (AD, DHCP, WINS) from
NT4 to Windows 2000, but forgot to remove the domain suffix on the NIC
before we did.
That resulted in the DC under Network Identification has a name of
computername.onedomain.com, and the Domain: otherdomain.local.
This gives long logon-times, with Errors 1053 and 1054 Source Userenv
and Error 15 AutoEnrollment on our XP SP2 clients, and some clients
loose connctions to network drives (only some, which puzzles me a bit,
but that might be related to something else).
As we are no longer a part of onedomain.com, we are now looking for the
easiest way to get rid of it, and only use the otherdomain.local. Is it
possible without reinstalling the domain controller? It could
temporarily be possible to add another DC if that would make it easier,
or upgrade the existing DC to 2003 but I am not sure if it is possible
to rename DC's running that.
Any and all suggestions are very welcome
long ago we upgraded our only domain controller (AD, DHCP, WINS) from
NT4 to Windows 2000, but forgot to remove the domain suffix on the NIC
before we did.
That resulted in the DC under Network Identification has a name of
computername.onedomain.com, and the Domain: otherdomain.local.
This gives long logon-times, with Errors 1053 and 1054 Source Userenv
and Error 15 AutoEnrollment on our XP SP2 clients, and some clients
loose connctions to network drives (only some, which puzzles me a bit,
but that might be related to something else).
As we are no longer a part of onedomain.com, we are now looking for the
easiest way to get rid of it, and only use the otherdomain.local. Is it
possible without reinstalling the domain controller? It could
temporarily be possible to add another DC if that would make it easier,
or upgrade the existing DC to 2003 but I am not sure if it is possible
to rename DC's running that.
Any and all suggestions are very welcome