Re: Q329873, problems with DC's machine account, need help!

From: Tim Springston [MS] (tspring_at_online.microsoft.com)
Date: 07/27/04 

Date: Tue, 27 Jul 2004 16:45:01 -0500

Hi Jeremy-

Your best path is to disjoin and then rejoin the workstations to the domain.
The NETDOM command would do most of the same functions and you may as well
use the user interface.

Please repost if this does not help. 

-- 
Tim Springston
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jeremy Lang" <plskeep@inthenewsgroup.com> wrote in message
news:ewrXCf0cEHA.2544@TK2MSFTNGP10.phx.gbl...
> So a DC's machine account was corrupted by a misguided attempt to get a
> couple Mac OSX 10.3 machines to participate in AD.  The (cr)Apples have
been
> taken off the network (almost with a hammer).
>
> I found a couple MS knowledge base articles that seemed to help,
especially
> Q329873 which told me to run nltest /sc_change_pwd:%domain name% and
reboot.
> This had worked like a charm (eventually... there's some kind of caching
> mechanism that delays it's working on some systems), but over the weekend
> many machines started having the same problem again, though the DC wasn't
> having trouble running 'Active Directory users and computers' or dcdiag
> today like it did Friday evening.  (DCdiag passes every test.)
>
> It manifests with workstations access to this server (even by
> \\%servername% ) getting the result:
> Logon Failure: The target account name is incorrect.  It doesn't happen if
> they access it by \\%serverIPaddr% but this is our main fileserver and
print
> server, so that's obviously not good enough.  Doing the nltest thing again
> today seems to have fixed it (except on one or two that are still having
> problems... caching?) but I need a permanent way to fix this problem.
>
> With further searching today I found Q216393.  Looks like exactly what I
> need, but netdom will not work as it's supposed to.  I don't know if it's
> being caused by the real problem or just that it doesn't recognize our
> domain name (it's unfortunately single-level, i.e. no .com ending, but had
> been working fine).  Here's what I get:
> >netdom reset %server% /domain:%domain%
> The secure channel from %server% to %domain% was not reset.
> The specified domain either does not exist or could not be contacted.
>
> The specified domain either does not exist or could not be contacted.
>
> The command failed to complete successfully.
>
> I tried adding the trailing period to the domain name, \\%domainname%, and
a
> couple other things.  Anybody have any ideas??
>
>

Relevant Pages

  • Re: Clustering
    ... You mentioned WS's above and I assume that means WorkStations. ... Every fifth machine is a boot server. ... Each boot server serves four other machines. ... files were stored on the disk server. ...
    (comp.os.vms)
  • RE: Windows Universal Storage Server 2003 quits working
    ... day) stops communicating with the domain controllers. ... but no other machines are affected (either servers or ... Local workstations can access files, ... The Server is a Dell NX1950 with a MD3000 Raid Enclosure. ...
    (microsoft.public.windows.server.general)
  • Re: Access 97 placing info in wrong field when record is edited or upd
    ... If all machines claim to be SR-2, ... > of the workstations contained the dap350.dll, nor did the server. ... >> The table (called workorder table) that this form originates ...
    (microsoft.public.access.forms)
  • SMS Advanced Clients
    ... 2nd server has SQL, SMS and is the sole MP. ... I am able to locate my network machines that I wish to make clients and even ... Viewing the workstations ... they appear to have installed the client software. ...
    (microsoft.public.sms.setup)
  • Re: how to join again a workstation for a new domain instalation with the same name?
    ... but the problem are that i don´t have the local administrator password of the workstations. ... I don´t know if with NETDOM command, from the server i can do this? ...
    (microsoft.public.win2000.active_directory)
Loading