Getting this in the Windows Security Log:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 6/15/2012 7:31:04 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: Apollo.XXX.local
Description:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: APOLLO$
Account Domain: XXX
Logon ID: 0x3e7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name:
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0x230
Caller Process Name: C:\Windows\System32\lsass.exe
Network Information:
Workstation Name: APOLLO
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Schannel
Authentication Package: Kerberos
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="
http://schemas.microsoft.com/win/2004/08/events/event">
;
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2012-06-16T00:31:04.104727600Z" />
<EventRecordID>631806</EventRecordID>
<Correlation />
<Execution ProcessID="560" ThreadID="16648" />
<Channel>Security</Channel>
<Computer>Apollo.BGMOffice.local</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">APOLLO$</Data>
<Data Name="SubjectDomainName">BGMOFFICE</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">
</Data>
<Data Name="TargetDomainName">
</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc0000064</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">Schannel</Data>
<Data Name="AuthenticationPackageName">Kerberos</Data>
<Data Name="WorkstationName">APOLLO</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x230</Data>
<Data Name="ProcessName">C:\Windows\System32\lsass.exe</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>
I know this is coming from the phone system which is part of the local network. We are trying to configure it to send emails that contain voicemail messages to the SMTP server that I activated on this SBS 2011 Essentials server (and then configured the SMTP
Email in IIS 7 ASP.NET section). It is supposed to be using Port 25 and relayiing the incoming emails from the phone system to Google Apps mail server. But it seems like those emails are being blocked on the SBS server.

The Logon Process refers to Schannel which I believe is part of the Samsung phone system - phone system is operated by another vendor who is also stumped.
One of the steps in configuring the SMTP Email app in IIS is to enter a username and pw. I used one of the basic usernames and associated pw, not an administrator level account.

Can someone point out the err of my ways?
Many thanks in advance.



Bill

Need to support users over the internet? click here try our remote control online beta