Discussion Locked

NT Security Auditing Problem

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Greetings!!
We are using Windows NT 4.0 and currently have 7 servers, a PDC, 2 BDCs
and the rest are member servers. We have a problem regarding security auditing.
We can only audit users who are accessing files from the PDC and BDC.
How come we couldnt audit users who are connecting to all members
servers??? There were already an incident before, two or more users
have accidentally deleted files from our member server which we couldnt
trace because the security log in the event viewer, where those two users
are connecting was empty or editing is not turned on while infact it already has.
DHCP is installed in the PDC. All servers have static IP. Auditing is already turned.
We are seeking for help and hoping that you could provide us a good solution for these matters.

RANDY(RED) SILVA

3 replies

by ntoz

One of the most often overlooked issues with member servers, the memeber servers have to have auditing turned on. With your domain controlers, auditing was turned on and its done across the board for all domain controlers because they all share the same SAM database. The member servers have their own SAM database for local resouces. In order to audit on these systems you need to logon to the member server with an account that has administrative priv. at the local level. In most cases by defaultthe domain admin group and everyone in it has this. You need to go into user manager for domains and change the computer your looking at, from the domain name to the local server name. Then you can set auditing for the local server. I would also suggest that you look at your security policy and the way your applying permissions as they will save you from these types of problems better then the weak information you can get from the audit trails.

Pete

This discussion is closed to new replies.