gaddam01
asked on
Unexplained Event Logs on Member Servers
Hi,
We are using Windows server 2003 domain controllers. We are having member servers which are running on Windows Server 2003.We are observed some events logged in our member servers with event id 540.
The users don't have any permission to login to the server but still some events are logging with those user id in event viewer.
Source: Security
Categeory: Logon/Logoff
EventID: 540
Type: Success A
Can any one suggest me why such types of events are logged in the event viewer. We need resolution for this.
Thanks in Advance.
We are using Windows server 2003 domain controllers. We are having member servers which are running on Windows Server 2003.We are observed some events logged in our member servers with event id 540.
The users don't have any permission to login to the server but still some events are logging with those user id in event viewer.
Source: Security
Categeory: Logon/Logoff
EventID: 540
Type: Success A
Can any one suggest me why such types of events are logged in the event viewer. We need resolution for this.
Thanks in Advance.
Lazarus
Event 540 gets logged when a user elsewhere on the network connects to a resource (e.g. shared folder) provided by the Server service on this computer. The Logon Type will always be 3 or 8, both of which indicate a network logon.
ASKER
Hello,
Thanks for the response. You mean to say that the user is having some permissions any any shared folder on the server?
What is the meaning of Network Logon?
If the user don't have any logon rights on the server then in the event viewer why it is showing as Logon/Logoff?
Thanks for the response. You mean to say that the user is having some permissions any any shared folder on the server?
What is the meaning of Network Logon?
If the user don't have any logon rights on the server then in the event viewer why it is showing as Logon/Logoff?
Yes, if a member of the Active Directory is accessing resources on the server from there client computer it will log that on teh server, since they have accessed the server through the network.
Do you have Shared Folders on this server? A DFS folder etc...?
Do you have Shared Folders on this server? A DFS folder etc...?
ASKER
We don't have any shared folders and DFS folders also.
Do you have any server resources availble to the network? is it an Active Directory Server? If so thats all it reall takes, if it is getting information from the server. It is not a real issue, but it should also be telling you who is accessing it. look at the details:
•User Name: %1
•Domain: %2
•Logon ID: %3
•Logon Type: %4
•Logon Process: %5
•Authentication Package: %6
•Workstation Name: %7
You can see from there what WKS is accessing the server and such.
•User Name: %1
•Domain: %2
•Logon ID: %3
•Logon Type: %4
•Logon Process: %5
•Authentication Package: %6
•Workstation Name: %7
You can see from there what WKS is accessing the server and such.
ASKER
I have attached the Event Viewer details for the issue. I need to stop these events from happening on the servers.
Even though the users don't have any access or permissions on the servers still it is happening. We don't have any shared or DFS folders on the servers.
This is very urgent, Please help me out on this. Event-viewr-details.doc
Even though the users don't have any access or permissions on the servers still it is happening. We don't have any shared or DFS folders on the servers.
This is very urgent, Please help me out on this. Event-viewr-details.doc
This is not a bad thing. It's normal:
For network connections (such as to a file server), it will appear that users log on and off many times a day. This phenomenon is caused by the way the Server service terminates idle connections.
If a user turns off his/her computer, Windows does not have an opportunity to log the logoff event until the system restarts. Therefore, some logoff events are logged much later than the time at which they actually occur.
ANONYMOUS LOGONs are routine events on Windows networks.
Microsoft's comments:
This event does not necessarily indicate the time that a user has stopped using a system. For example, if the computer is shut down or loses network connectivity it may not record a logoff event at all.
For network connections (such as to a file server), it will appear that users log on and off many times a day. This phenomenon is caused by the way the Server service terminates idle connections.
If a user turns off his/her computer, Windows does not have an opportunity to log the logoff event until the system restarts. Therefore, some logoff events are logged much later than the time at which they actually occur.
ANONYMOUS LOGONs are routine events on Windows networks.
Microsoft's comments:
This event does not necessarily indicate the time that a user has stopped using a system. For example, if the computer is shut down or loses network connectivity it may not record a logoff event at all.
ASKER
Hello,
Thanks for the reply. In the reply you had mentioned Microsoft comments can you please send me any Microsoft KB Article which is supporting your comments.
Thanks for the reply. In the reply you had mentioned Microsoft comments can you please send me any Microsoft KB Article which is supporting your comments.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
3 Network A user or computer logged on to this computer from the network.
From Microsoft KB Article it was written like the above one. What is the meaning of it?
User don't have any rights on the Member server then How can login to Member server from Network?
This is not clear to me.
Please send me your comments on this. Because we don't have shared any thing on this server.
From Microsoft KB Article it was written like the above one. What is the meaning of it?
User don't have any rights on the Member server then How can login to Member server from Network?
This is not clear to me.
Please send me your comments on this. Because we don't have shared any thing on this server.
He does not have to have login rights to it. His computer could be contacting it for many different reasons.
Perhaps it would help if you told me what the Server is, in conjunction to the network. Is it a DC? A file server SQL server etc. What is it's function?
Perhaps it would help if you told me what the Server is, in conjunction to the network. Is it a DC? A file server SQL server etc. What is it's function?