Event 2510 appears every 12 minutes in Server 2003 DC system l
in [Windows Servers]
|
From: David B on 2 Oct 2007 15:21 Yes, we have a very simple domian with one DC and three domain member clients, all of which are running Windows XP. Only one client seems to cause the problem. "Meinolf Weber" wrote: > 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! > > > > >
From: Meinolf Weber on 2 Oct 2007 15:34 Hello David, And you have no MAC's or UNIX clients in the network? Because a lot of articles are mentioned for this error with them. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > Yes, we have a very simple domian with one DC and three domain member > clients, all of which are running Windows XP. Only one client seems to > cause the problem. > > "Meinolf Weber" wrote: > >> 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! >>>
From: David B on 2 Oct 2007 15:44 No, only Windows Server 2003 and Windows XP. nothing else! "Meinolf Weber" wrote: > Hello David, > > And you have no MAC's or UNIX clients in the network? Because a lot of articles > are mentioned for this error with them. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > Yes, we have a very simple domian with one DC and three domain member > > clients, all of which are running Windows XP. Only one client seems to > > cause the problem. > > > > "Meinolf Weber" wrote: > > > >> 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! > >>> > > >
From: Meinolf Weber on 3 Oct 2007 06:01 Hello David, Remove the workstation with the problem from the domain to workgroup, reboot and add it again to the domain. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. > No, only Windows Server 2003 and Windows XP. nothing else! > > "Meinolf Weber" wrote: > >> Hello David, >> >> And you have no MAC's or UNIX clients in the network? Because a lot >> of articles are mentioned for this error with them. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers >> no rights. >>> Yes, we have a very simple domian with one DC and three domain >>> member clients, all of which are running Windows XP. Only one client >>> seems to cause the problem. >>> >>> "Meinolf Weber" wrote: >>> >>>> 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!
From: David B on 3 Oct 2007 10:31 Thanks for the suggestion, but if I do that won't the workstation lose all it's configuration settings when it re-joins the domain? "Meinolf Weber" wrote: > Hello David, > > Remove the workstation with the problem from the domain to workgroup, reboot > and add it again to the domain. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and confers > no rights. > > > No, only Windows Server 2003 and Windows XP. nothing else! > > > > "Meinolf Weber" wrote: > > > >> Hello David, > >> > >> And you have no MAC's or UNIX clients in the network? Because a lot > >> of articles are mentioned for this error with them. > >> > >> Best regards > >> > >> Meinolf Weber > >> Disclaimer: This posting is provided "AS IS" with no warranties, and > >> confers > >> no rights. > >>> Yes, we have a very simple domian with one DC and three domain > >>> member clients, all of which are running Windows XP. Only one client > >>> seems to cause the problem. > >>> > >>> "Meinolf Weber" wrote: > >>> > >>>> 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! > > >
|
Next
|
Last
Pages: 1 2 Prev: Robocopy problem Next: Windows Small Business Server 2003 Preimum Edition -Startup Problem |