Re: View an security log on an Windows XP Pro client

Yeah that is the setting, Non-admins need to be included in this group. I
thought you could deny access as well but after looking through it I was
mistaken.

Have you tried the admin account or a different user account in the local
admins group? Have you verified the machine is able to talk to the domain?

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message
news:OL%23h8h7UIHA.2000@xxxxxxxxxxxxxxxxxxxxxxx
Are you talking about "manage auditing and security logs" this is under
user right assignment.

No groups are in there so it isn't define.


"Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx> wrote in message
news:e98gvI5UIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
There is a group policy setting that controls who can and can't access
the security log, I don't recall the setting name though and my link to
the location of all the settings has gone 404.

I would make sure that this machine is actually in the domain. It sounds
like there could be an issue with domain connectivity, since it sounds
like you are attempting to access the logs as a local administrator. You
could also try other accounts that are local admins on the box to see if
there is some specific issue with the group membership.

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message
news:%233j9ONzUIHA.4696@xxxxxxxxxxxxxxxxxxxxxxx
We are getting "access denied" when trying to view an security log
remotely on a Windows XP Pro Service Pack 2. Our domain contains all
Windows 2003 domain controllers. We have a global security group
that is in the local administrator group on the Windows XP Pro Service
Pack 2 client.

Is there any tool that we could use to find out why we are getting
access denied when trying to view the security log of the remote client.

If this post shouldn't go in this group, please direct on where to post
this.

Thanks in Advance,
Eric Sabo






.

Relevant Pages

  • Re: Event Viewer Security log Access denied
    ... 2004 Windows MVP "Winny" Award ... > computer regarding the Security log in Event Viewer. ... > This occurred even if I logged on with the local administrator account. ...
    (microsoft.public.windowsxp.general)
  • Re: Event Viewer Security log Access denied
    ... 2004 Windows MVP "Winny" Award ... > computer regarding the Security log in Event Viewer. ... > This occurred even if I logged on with the local administrator account. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: View an security log on an Windows XP Pro client
    ... like you are attempting to access the logs as a local administrator. ... Windows 2003 domain controllers. ... is in the local administrator group on the Windows XP Pro Service Pack 2 ... denied when trying to view the security log of the remote client. ...
    (microsoft.public.windows.server.active_directory)
  • Re: GetOwner and IdentityNotMappedException
    ... Our domain (Windows 2003) is trusted by the other domain. ... just to be clear on this - the Windows Explorer also only displays the SID ... Co-author of "The .NET Developer's Guide to Directory Services ... especially when deleted security principals are involved. ...
    (microsoft.public.dotnet.security)
  • Re: Kerberos authentication NOT in AD
    ... I'm not sure where the piece of code is that gives you a high level Kerberos ... Windows to do it yourself, but I'm not an expert at this. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ... so I'm not doing any authentication as of yet (I've ...
    (microsoft.public.dotnet.security)