Re: Windows NT Account missing or deleted

What is your domain functional level? If has to be either Windows 2000
mixed (by default) or Windows Server 2003 interim.
What is your forest functional level? It has to be either Windows 2000 (by
default) or Windows 2003 interim.

If either level isn't at these levels then you will have to upgrade your NT
member server.

Are there any messages in the NT event logs on the member server?

--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.

"Steve Ireland" <Sandymount@xxxxxxxxxxx> wrote in message
news:u2Dl%23iqmGHA.3752@xxxxxxxxxxxxxxxxxxxxxxx
Windows Server 2003 Active Directory DCs (running in Windows Server 2003
Interim mode and, recently, SP1). One NT4 SP6a BDC.

Over the last few weeks, one by one, NT4 Workstations have not been able
to
logon to the domain. When you try to logon a domain user account you get
an
error that the computer account is missing or disabled.
Best as I can tell, seems that the computer account passwords have not
been
properly synchronised with the 2K3 DCs.
Looking at AD Users & Computers, the NT4 BDC is counted in the Domain
Controllers OU. However, DNS does not refer to the NT4 BDC as a DC and is
not included in the DNS Name Servers list of DNS servers. NT4 BDC Server
Manager shows that no computer accounts are active, i.e it thinks that
none
of the domain systems are running. Using NETDOM the security with NT4 BDC
seems faulty. The DCs cannot access its shares.
So after trying lots of things with NETDOM, I have finally removed all
necessary services from the NT4 BDC and temporarily (maybe permanently)
removed it from the network.

Disconnecting and reconnecting NT4 Workstation accounts to the domain has
not been working, so I have been upgrading them to XP. However, I have
another NT4 Member Server (apart from the NT4 BDC). This member server is
running a library management system and I do not think that it is
compatible
with 2003/2000. So, now that the disfunctional NT4 BDC is offline, I have
been trying to remove/readd the NT4 Meber Server to the domain. It adds OK
(in about 5 seconds, which seems a little fast). I have been deleting the
exisiting account and getting the NT4 Member Server to create a computer
account when it joins.
But I keep getting the "computer account is missing or disabled" error.

I am stuck. Should I not be able to add an NT4 system to my domain? Is
there
some sort of security on the 2K3 DCs that might be preventing the NT4
system
from communicating with them?

TIA

Steve.





.

Relevant Pages

  • Re: Getting access denied when sync between DCs - one is NT4
    ... It's okay now, I rebooted the NT4 ... If you don't have the tools installed, install them from your server ... We changed the domain Administrator today and one NT4 BDC complained ... Do I just need to reboot the BDC? ...
    (microsoft.public.windows.server.active_directory)
  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... For Windows 2000 and 2003 these settings may be applied/configured via ... Digitally sign communications (if server ... With NT4 the only way to verify the settings is with the Regedt32 tool. ... Failed to create a trust relationship between NT4 and 2003 AD ...
    (microsoft.public.windows.server.migration)
  • Windows NT Account missing or deleted
    ... Windows Server 2003 Active Directory DCs (running in Windows Server 2003 ... One NT4 SP6a BDC. ... seems that the computer account passwords have not been ... Looking at AD Users & Computers, the NT4 BDC is counted in the Domain ...
    (microsoft.public.windows.server.active_directory)
  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... Ping -a IP -- work and resolve the NT4 server name ... security policy in Administrative tools, go to local policies / security ... For Windows 2000 and 2003 these settings may be applied/configured via ...
    (microsoft.public.windows.server.migration)
  • RE: Failed to create a trust relationship between NT4 and 2003 AD
    ... is that a must to do for all setting when NT4 ... For Windows 2000 and 2003 these settings may be applied/configured via ... minutes in Windows 2003 Server ... Failed to create a trust relationship between NT4 and 2003 AD ...
    (microsoft.public.windows.server.migration)