|
Posted by Roger Abell [MVP] on October 6, 2006, 7:01 pm
If you were Registered and logged in, you could reply and use other advanced thread options
Just what is it that you are asking?
The event log you show seems to simply record a failure
of that machine to log in with its machinename$ account,
which of course would not exist in the target W2k domain
unless you did mean to say that these "separate" domains
are either in the same forest of have trust(s) between them.
If they are in the same forest, then it is worth asking why
NTLM is being used, otherwise it is the remaining alternative
as W2k does not support Kerberos over an external trust.
--
Roger Abell
Microsoft MVP (Windows Server : Security)
> Ok, here is the situation. I have a plethora of these errors in my
> security
> log. These are my school lab computers. They are on a different windows
> 2000 domain separate from the win2k3 Domain in the building. I have a
> file
> server on my win2k3 domain that these computers connect to via a logon
> script
> that maps a drive to the file server via some win2k3 domain account
> credentials. The mapping occurs just fine, and i actually see the
> successful
> login of that account throughout the logs.
>
> However, and at writing time, I am not sure how far the errors below go
> back. I am trying to figure out why the errors below are popping up. Why
> would these computers be trying to talk to the filesserver using the
> NtLmSsp
> process
>
> I am not sure where to begin the troubleshooting process
>
> Event Type: Failure Audit
> Event Source: Security
> Event Category: Logon/Logoff
> Event ID: 529
> Date: 10/5/2006
> Time: 2:26:30 AM
> User: NT AUTHORITY\SYSTEM
> Computer: FILESHARE
> Description:
> Logon Failure:
> Reason: Unknown user name or bad password
> User Name: MGT-UGRDLAB-D04$
> Domain: AD
> Logon Type: 3
> Logon Process: NtLmSsp
> Authentication Package: NTLM
> Workstation Name: MGT-UGRDLAB-D04
>
>
| 
XML site map