Remove the computer from the domain. Set the Primary domain suffix to beQuote:> I can not access one of our domain computers "Candy" from
> the server, nor can I log onto the domain computer
> directly. The domain name is alongthewayside, all of the
> other computers on the domain have the dns
> computername/alongthewayside.com. "Candy's" dns is blank,
> and the error message on the server is "account name is
> bad." From the computer itself, the error I get upon
> logging in is..can not log onto domain, account password
> in invalid or missing...When trying from another domain
> computer to "Candy" message is parent trust relationship
Please direct all replies to the newsgroup so all can benefit.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
While doing an upgrade of our NT4 PDC (backed up) to a Win2K DC, I ran
into the bug as described in KB article 262376.
Unfortunately, the workarounds described don't work. The first time
around, I tried cancelling dcpromo and checking the "Change primary DNS
suffix when domain membership changes" check box. Unfortunately, that
check box is accessed through Computer->System Properties->Network
However, Network Identification is greyed out during the upgrade
processes with a "This computer is being upgraded to Active Directory"
The second workaround, which was to patch the system to the latest
Service Pack (SP3 in this case) did not work. After an hour of patching
and running Windows update, I still had the DNS name of the upgraded
Windows 2000 DC disjoint from our AD name.
I also looked at KB 257623, but neither workaround works for us. Method
1's registry hack explicitly doesn't work for an upgraded NT 4.0 PDC/BSD.
Method 2, demoting the DC, also doesn't work since you lose all of the
information from the old NT 4 domain, and the disjointed namespace
prevents us from promoting another DC to take over the information
before this happens.
Are there any other workarounds?