Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

HyperV Failed Logins from SBS Guest NTLM

$
0
0

Hello , i have noticed failed login attempts on our Hyper-V host from the SBS guest. The Hyper-V is in a work-group where as the SBS 2011 is the DC for the network. I have found that every minute there would be a failed login attempt made from the SBS to the Host. 

I have attempted to troubleshoot this issue by tracking down Process ID's and ports disclosed in the event logs. I found that the logins are over microsoft-ds Protocol on port 445. The process executing these logins is a system process so my guess a service is attempting to access something on the HV without the correct credentials but I am finding it difficult to determine what. Please could anyone shed some light on my issue. 

Event ID 4625 -General 

An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain:-
Logon ID: 0x0

Logon Type:3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: admin
Account Domain:DOMAIN

Failure Information:
Failure Reason:Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064

Process Information:
Caller Process ID:0x0
Caller Process Name:-

Network Information:
Workstation Name:SBS
Source Network Address:192.168.0.3
Source Port: 35074

Detailed Authentication Information:
Logon Process:NtLmSsp 
Authentication Package:NTLM
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.

Details

- System 

  - Provider 

   [ Name]  Microsoft-Windows-Security-Auditing 
   [ Guid]  {54849625-5478-4994-A5BA-3E3B0328C30D} 
 
   EventID 4625 
 
   Version 0 
 
   Level 0 
 
   Task 12544 
 
   Opcode 0 
 
   Keywords 0x8010000000000000 
 
  - TimeCreated 

   [ SystemTime]  2014-07-18T10:23:37.915496600Z 
 
   EventRecordID 362715 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  564 
   [ ThreadID]  3336 
 
   Channel Security 
 
   Computer H-V 
 
   Security 
 

- EventData 

  SubjectUserSid S-1-0-0 
  SubjectUserName - 
  SubjectDomainName - 
  SubjectLogonId 0x0 
  TargetUserSid S-1-0-0 
  TargetUserName admin 
  TargetDomainName DOMAIN
  Status 0xc000006d 
  FailureReason %%2313 
  SubStatus 0xc0000064 
  LogonType 3 
  LogonProcessName NtLmSsp  
  AuthenticationPackageName NTLM 
  WorkstationName SBS 
  TransmittedServices - 
  LmPackageName - 
  KeyLength 0 
  ProcessId 0x0 
  ProcessName - 
  IpAddress 192.168.0.3 
  IpPort 35074 

Names and IP's have been edited 

Thank you 

Regards

Jack 


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>