LSA can't authenticate to itself? (LsaSrv event 6037)

[Ben Scott]

  Had a weird one show up in the logs of one of our stand-alone PCs.
I don't really expect anyone knows what this means (not even
Microsoft), but I thought it might be useful to report for the
archives if nothing else.  Anyway:

Log: System
Source: LsaSrv
Event ID: 6037
Level: Warning
Category: None
Description: The program lsass.exe, with the assigned process ID 652,
could not authenticate locally by using the target name
host/\\ABCDE20.  The target name used is not valid.  A target name
should refer to one of the local computer names, for example, the DNS
host name.  Try a different target name.

  As near as I can tell, that means that something running inside the
LSASS.EXE process failed to authenticate itself.  The neat thing is
that, as I understand it, LSASS is the process responsible for
authenticating things.  Local Security Authority Subsystem.  Yah?  So
it can't talk to itself?  :)

  ABCDE20 has been changed, of course, but the real name of the
system does appear in that position.  It's the short name of the
system -- there's no DNS domain name.  Indeed, the system has no
network connections at all.  The Microsoft Loopback Adapter is
installed - had to do that to work around some other bugs.

  Vista Biz SP1, if that matters.

  I suspect this will go in my ever-growing folder of goofy Vista bugs.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: LSA can't authenticate to itself? (LsaSrv event 6037)

[Brian Desmond]

There's a Loopback registry setting for LSA. 
http://support.microsoft.com/kb/926642

Thanks,
Brian Desmond
br...@briandesmond.com

c   - 312.731.3132

-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com] 
Sent: Tuesday, March 29, 2011 4:59 PM
To: NT System Admin Issues
Subject: LSA can't authenticate to itself? (LsaSrv event 6037)

  Had a weird one show up in the logs of one of our stand-alone PCs.
I don't really expect anyone knows what this means (not even Microsoft), but I 
thought it might be useful to report for the archives if nothing else.  Anyway:

Log: System
Source: LsaSrv
Event ID: 6037
Level: Warning
Category: None
Description: The program lsass.exe, with the assigned process ID 652, could not 
authenticate locally by using the target name host/\\ABCDE20.  The target name 
used is not valid.  A target name should refer to one of the local computer 
names, for example, the DNS host name.  Try a different target name.

  As near as I can tell, that means that something running inside the LSASS.EXE 
process failed to authenticate itself.  The neat thing is that, as I understand 
it, LSASS is the process responsible for authenticating things.  Local Security 
Authority Subsystem.  Yah?  So it can't talk to itself?  :)

  ABCDE20 has been changed, of course, but the real name of the system does 
appear in that position.  It's the short name of the system -- there's no DNS 
domain name.  Indeed, the system has no network connections at all.  The 
Microsoft Loopback Adapter is installed - had to do that to work around some 
other bugs.

  Vista Biz SP1, if that matters.

  I suspect this will go in my ever-growing folder of goofy Vista bugs.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin