Re: Event 2510 appears every 12 minutes in Server 2003 DC system log



Hello David,

Is that client a domain member?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

The following warning event 2510 has suddenly starter appearing
exactly every
12 minutes in my Windows Server 2003 DC system log:
"The server service was unable to map error code 1355"
at the same time as this, four entries appear in the Security log:

(1) NT AUTHORITY / ANONYMOUS LOGON Sucess A Event ID: 540
Succesful Network Logon:
User Name:
Domain:
Logon ID: (0x0,0x63DDBDB)
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: OFFICE
Logon GUID: -
Caller User Name: -
Domain: -
Logon ID: -
Process ID: -
Transited Services: -
Source Network Address: 192.168.0.13
Source Port: 0
(2) NT AUTHORITY / ANONYMOUS LOGON Sucess A Event ID: 538
User logoff:
User name: ANONYMOUS LOGON
Domain: NT AUTHORITY
Logon ID: (0x0,0x63DDBDB)
Logon Type: 3
(3) and (4) are duplicates of (1) and (2), ecept with a different
logon ID
The client referred to in the event is running Windows XP. The events
stop as soon as this client computer is turned off.

If anyone has an idea what might be causing this, please get in touch!



.



Relevant Pages

  • RE: Event ID 529 on cleint workstation
    ... Security Event ID 529 is a failure audit for logon/logoff. ... "logon events" generate the events on domain controllers for domain account ... The Event 529 was caused by the machine account password not being ... I suggest that you re-join the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 529 on cleint workstation
    ... "logon events" generate the events on domain controllers for domain account ... The Event 529 was caused by the machine account password not being ... I suggest that you re-join the client to ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: NT4 -> Win2K3 question
    ... "not allow me logon to domain." ... I suspect you still unable to join the ... client into domain, right? ... Get Secure! ...
    (microsoft.public.windows.server.migration)
  • Re: windows client cant start completely...get blank desktop and no icons, start button, task bar, e
    ... Can you access the registry remotely from another workstation or the ... "Logon to the problematic client as a user who can logon to other ... Logon to a working client as the user who encountered the problem. ... not supported in newsgroup support. ...
    (microsoft.public.windows.server.sbs)
  • Re: windows client cant start completely...get blank desktop and no icons, start button, task bar, e
    ... "Logon to the problematic client as a user who can logon to other ... Logon to a working client as the user who encountered the problem. ... please check the following registry keys that define the ... not supported in newsgroup support. ...
    (microsoft.public.windows.server.sbs)