Error source port

[leco]

I have a number of errors being reported by the 2008 server. Event ID 4625 these are logon audit failures. What I'd like to know - is it possible to discover what is using (or attempting to use) the reported source port?

 

I know which machine is failing the audit what I don't know is which service/app etc is trying to connect. Any help gratefully received.

[AIT]

I have a number of errors being reported by the 2008 server. Event ID 4625 these are logon audit failures. What I'd like to know - is it possible to discover what is using (or attempting to use) the reported source port?

 

I know which machine is failing the audit what I don't know is which service/app etc is trying to connect. Any help gratefully received.

 

There should be a bit more information after the 4625 error:

 

 

"

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: asdf

Account 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: WIN-R9H529RIO4Y

Source Network Address: 10.42.42.201

Source Port: 53176

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 "

 

If you could post the full event:

[leco]

Yes the error message says all of that. Is there a particular bit that's relevant? All I want to know is what is using the port.

[AIT]

Yes the error message says all of that. Is there a particular bit that's relevant? All I want to know is what is using the port.

 

Source Network Address: 10.42.42.201

Source Port: 53176

 

that part of the error should tell you the information. i would then suggest doing either a packet sniffer on that particular machine or on the identified machine do a cmd "netstat -a"

 

Hope this helps

[leco]

OK done that, The machine is using the port in question.

nstat reports listening and Local host Established which doesn't tell me a great deal.

[AIT]

OK done that, The machine is using the port in question.

nstat reports listening and Local host Established which doesn't tell me a great deal.

 

i was mearly hoping netstat would 100% identify that machine being the culpriate incase any spoofing was going on.

 

have you ever come across the command fuser. I am not sure if there is a in built windows command but a program like this would certainly give you the answer.

 

 

 

from the website:

 

"This is mostly for own use, but: If you've ever had a server which netstat showed was listening on one or more ports you weren't expecting, you can use this command to find out which process is listening there:

 

fuser -vn tcp 4444

 

Which in this case happens to be owned by JBoss, and not some linux version of a windows worm:)

 

For more info on fuser, check out the man page, or the simple help below:

 

Usage: fuser [ -a | -s | -c ] [ -n SPACE ] [ -SIGNAL ] [ -kimuv ] NAME...

[ - ] [ -n SPACE ] [ -SIGNAL ] [ -kimuv ] NAME...

etc website How to identify the process listening on a port | Devon Hillard Tech Blog "