Re: Domain login Problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: "Marcin" <marcin@xxxxxxxxxxxxxxxx>
Date: Sat, 1 Mar 2008 07:19:09 -0500

Verify IP configuration of the client (in particular its DNS settings) and make sure that the computer account exists in AD. Test its secure channel to a target domain controller (using nltest). Try resetting its account in AD (you can do this using ADUC) if that channel is failing...

hth
Marcin

.

References:
- Domain login Problem
  - From: IDM

Prev by Date: Re: Script Request
Next by Date: Re: Sites container in AD 2003?
Previous by thread: Domain login Problem
Next by thread: Re: Script Request
Index(es):
- Date
- Thread

Relevant Pages

RE: dr testing but cannot logon
... This behavior may occur if the password for the computer account and the ... Reset the secure channel between the Windows XP-based client computer and ... Support\Tools folder of the Windows XP CD-ROM. ... Check the event logs on both the PDC and Windows XP client computer. ...
(microsoft.public.win2000.active_directory)
Re: Reset computer account
... > There are user account objects just like there are computer account objects. ... > The computer account objects have a secure channel with a Domain Controller. ... > Microsoft gives us the ability to reset that secure channel. ...
(microsoft.public.win2000.active_directory)
Re: Reset computer account
... There are user account objects just like there are computer account objects. ... The computer account objects have a secure channel with a Domain Controller. ...
(microsoft.public.win2000.active_directory)
Re: Secure Channel Password
... My understanding is ... controller will disable the computer account. ... run on a domain computer will detect if the secure channel to the domain is ... > Does the Secure Channel Password change whenever one restarts the server? ...
(microsoft.public.win2000.security)
Re: Event ID 566 - Failure Audit
... Client User Name: AUPTHD99-X6141$ ... sounds like you are using secure dynamic DNS and the computer AUPTHD99-X6141 was not the one writing his DNS-Record initially. ... If you use secure dynamic DNS you need to make sure that each computer is registering his own record initially because he will become the owner of that record and in future he will be the only one allowed to change the record. ... In your eventlog the computer account tries to change or update his record but is not sucessfull. ...
(microsoft.public.windows.server.active_directory)