Re: SBS 2003 Restore - NETLOGON errors - Unable to log client computers on to DC

From: Marina Roos [SBS-MVP] (marina_at_roos.nodontwantspam.nl.com)
Date: 06/29/04 

Date: Tue, 29 Jun 2004 02:07:45 +0200

Flip them to a workgroup, create the computeraccounts on the server (delete
the old ones), run servername/connectcomputer from the clients. 

-- 
Regards,
Marina
Microsoft SBS-MVP
<anonymous@discussions.microsoft.com> schreef in bericht
news:226df01c45d6a$920ba610$a301280a@phx.gbl...
> Thanks for your reply, can you suggest how to rejoin the
> clients to the domain?
>
> Michael
>
> >-----Original Message-----
> >You will have to rejoin the clients to the domain.
> >
> >-- 
> >Regards,
> >
> >Marina
> >Microsoft SBS-MVP
> >
> >"Michael" <michaelavw@hotmail.com> schreef in bericht
> >news:22c2501c45d63$16275b40$a001280a@phx.gbl...
> >> Hi,
> >> I am having difficulties after restoring Small Business
> >> Server 2003 onto a different computer using Ntbackup.
> The
> >> restore procedure succeeded but a number of services
> were
> >> unable to start automatically (DHCP, WINS, Message
> >> Queuing). To restart DHCP I uninstalled then
> reinstalled
> >> it, then I configured the DHCP options to match the
> >> configuration as it was. To restart WINS I deleted the
> >> contents of the c:\WINDOWS\System32\WINS directory. To
> >> restart Message Queuing I uninstalled and reinstalled
> it.
> >> I also had to manually reconfigure the IP settings for
> >> the network adapter. I now have a server which starts
> up
> >> cleanly and without errors in the Event Log.
> >>
> >> The problems that I am having involve logging on to the
> >> domain from an XP client. The client gives the
> >> message "Windows cannot connect to the domain, either
> >> because the domain controller is down or otherwise
> >> unavailable, or because your computer account was not
> >> found." The Event Log on the server has the following
> >> error message - NETLOGON - "The session setup from the
> >> computer <computername> failed to authenticate. The
> name
> >> (s) of the account(s) referenced in the security
> database
> >> is <computername>$. The following error occurred:
> Access
> >> is denied."
> >>
> >> All documentation that I have been able to locate
> >> regarding this suggests that it is a secure
> communication
> >> channel between the server and client computer that has
> >> been lost. I have tried to use Netdom, Nltest, and to
> >> Reset the account using Active Directory but none of
> >> these work. If I log on to the client without
> connecting
> >> to the domain, then plug in the network cable, I am
> able
> >> to view the server across the network.
> >>
> >> Any suggestions on how to resolve this problem would be
> >> appreciated.
> >>
> >> Michael
> >
> >
> >.
> >

Relevant Pages

  • Re: http://companyweb
    ... >> In Network Configuration of the W98, properties of Client for Microsoft ... >> Microsoft SBS-MVP ... On the SBS server I went to Server ...
    (microsoft.public.windows.server.sbs)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • This is going straight to the pool room
    ... or not the client has privilege to do what they're trying to do, ... The server environment is this: ... 3GL User action Routines that Tier3 will execute on your behalf during the ... Routine Name: USER_INIT ...
    (comp.os.vms)
  • PuTTY suddenly stopped working (WinXPsp2 to FreeBSD5.4)
    ... assumption is that the problem is on the Client machine. ... On the Server ... ... Open a PuTTY session and I am prompted for a username. ... Event Log: Writing new session log to file: ...
    (comp.security.ssh)
  • [Full-Disclosure] R: Full-Disclosure Digest, Vol 3, Issue 42
    ... Full-Disclosure Digest, Vol 3, Issue 42 ... SD Server 4.0.70 Directory Traversal Bug ... Arkeia Network Backup Client Remote Access ...
    (Full-Disclosure)