Re: Challenge for the great troubleshooters!

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Fots (postmaster_at_fots.nl)
Date: 12/15/04


Date: Wed, 15 Dec 2004 11:16:34 +0100

Other physical symptoms are not there at the moment. We want to try to get
it solved before any other symtops are rising.
We have added the computer in the domain succesfully now (suddenly it
worked?!), but when the computer restarts the user wasn't able to logon
using his domain account.

There are no errors in the DNS server event log (yet)

"mherchel" <n/a> wrote in message
news:uBVfrNh4EHA.3416@TK2MSFTNGP09.phx.gbl...
> Is there only one computer that you cannot add to the domain? What happens
> if you change the computer's name while you add it to the domain (instead
> of "workstation", call it "workstation1")... i've seen this fix a slightly
> similar problem in my AD network. As far as those event messages... I
> would lean toward it being caused by DNS issues. Are there any errors in
> the DNS server's DNS event log?
>
> What are the other physical symptoms of these errors (symptoms similar to
> not being able to add a PC to the domain).
>
>
>
>
> "Fots" <postmaster@fots.nl> wrote in message
> news:eEefQKg4EHA.3756@TK2MSFTNGP14.phx.gbl...
>> Allright, a major challenge. We have been working on this problem for 1,5
>> days and haven't found the cause (and solution) yet.
>>
>> Here is the environment (pretty simple):
>>
>> 1 Domain
>> Windows 2000 DC + Exchange
>> Dns AD-integrated (multiple zones for routing purposes)
>> Front-End Exchange server
>> Multiple member servers (2003)
>>
>> Now the issue:
>> We noticed that about 2 weeks ago some events started in the eventviewer,
>> but we also notice that there are coming more and more events.
>> We have on different servers, different errors in the eventviewer and
>> some strange problems. One of the problems is, there is a computer which
>> we can add to the domain. This all looks fine, but after a reboot of this
>> computer, it cannot find/logon to the domain, and cannot find/go to
>> shares (\\<servername> or \\ip_address). Sounds easy? Well, in our
>> eventviewers (on the servers, except the Domain Controller) we get the
>> following errors:
>> --------------------
>> Event Type: Warning
>> Event Source: LSASRV
>> Event Category: SPNEGO (Negotiator)
>> Event ID: 40960
>> Date: 14-12-2004
>> Time: 16:18:03
>> User: N/A
>> Computer: SERVEr
>> Description:
>> The Security System detected an authentication error for the server
>> ldap/domain_controller.domain.com/domain.com@domain.com. The failure
>> code from authentication protocol Kerberos was "The attempted logon is
>> invalid. This is either due to a bad username or authentication
>> information.
>> (0xc000006d)".
>> --------------------
>> Event Type: Warning
>> Event Source: LSASRV
>> Event Category: SPNEGO (Negotiator)
>> Event ID: 40961
>> Date: 14-12-2004
>> Time: 16:18:03
>> User: N/A
>> Computer: SERVER
>> Description:
>> The Security System could not establish a secured connection with the
>> server ldap/domain_controller.domain.com/domain.com@domain.com. No
>> authentication protocol was available.
>> --------------------
>> Event Type: Error
>> Event Source: Userenv
>> Event Category: None
>> Event ID: 1030
>> Date: 14-12-2004
>> Time: 16:18:03
>> User: DOMAIN\User
>> Computer: SERVER
>> Description:
>> Windows cannot query for the list of Group Policy objects. Check the
>> event log for possible messages previously logged by the policy engine
>> that describes the reason for this.
>> --------------------
>> Event Type: Error
>> Event Source: Userenv
>> Event Category: None
>> Event ID: 1006
>> Date: 14-12-2004
>> Time: 14:44:03
>> User: DOMAIN\User
>> Computer: SERVER
>> Description:
>> Windows cannot bind to <domain> domain. (Invalid Credentials). Group
>> Policy processing aborted.
>> --------------------
>> Event Type: Error
>> Event Source: Userenv
>> Event Category: None
>> Event ID: 1000
>> Date: 14-12-2004
>> Time: 15:45:50
>> User: NT AUTHORITY\SYSTEM
>> Computer: SERVER
>> Description:
>> Windows cannot determine the user or computer name. Return value (1326).
>> --------------------
>> Event Type: Failure Audit
>> Event Source: Security
>> Event Category: Account Logon
>> Event ID: 675
>> Date: 14-12-2004
>> Time: 13:36:12
>> User: NT AUTHORITY\SYSTEM
>> Computer: SERVER
>> Description:
>> Pre-authentication failed:
>> User Name: Username
>> User ID: DOMAIN\User
>> Service Name: krbtgt/DOMAIN.COM
>> Pre-Authentication Type: 0x2
>> Failure Code: 0x18
>> Client Address: 127.0.0.1
>>
>> --------------------
>>
>> What have we tried:
>> Checked DNS settings
>> AD settings
>> Server settings.
>> Checked with DNSDiag
>> Netdiag
>>
>> But we can't seem to pinpoint the exact origin of the problem. And where
>> do we start now??
>>
>> If you have any suggestions...please let us know!
>>
>> Greetings,
>> Hans
>>
>
>



Relevant Pages

  • Re: Added 2nd AD box, but when take 1st down to test, cant auth us
    ... change the dns configuration to point to 10.88.87.2 as the ... Directory Server Diagnosis ... The File Replication Service Event log test ... This event log message will appear once per connection, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Event ID: 4000
    ... Based on the text of your event log, it appears that DNS is working fine. ... The problem may happen when your server attempts to connect to the remote ...
    (microsoft.public.exchange2000.protocols)
  • Re: Event ID: 1053 logs roughly every 5 minutes
    ... I looked in the event log under apps and noticed that the server is ... I can remote into this server with no problem. ... This server is acting as the secondary DNS server for our domain as ... MVP Microsoft MVP - Directory Services ...
    (microsoft.public.windows.server.general)
  • Re: Problems with second DC (failover) when primary DC is offline. - A
    ... > I just ran DCDIAG again, and this time I noticed there is an error. ... from the Event log. ... >> My first instinct is DNS. ... >>> We have a Windows 2003 server as our DC. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Challenge for the great troubleshooters!
    ... Rename the computer while a member of the workgroup ... > Other physical symptoms are not there at the moment. ... I would lean toward it being caused by DNS issues. ... >> any errors in the DNS server's DNS event log? ...
    (microsoft.public.windows.server.general)