Re: Local Policy

On Tue, 16 May 2006 04:27:32 GMT, Too Cool <Too.Cool@xxxxxxxxxxx> wrote:

I have a XP Pro SP2 machine that I am trying to see with a W2K machine.
Every time that I open local security policy and select access this
computer from the network and enter the W2K machines to add user or group
all is well untill I go to save. I get a splash screen telling me can't
save to local policy database. I am signed in as the administrator. (All of
this worked before the XP crash)

Maybe you could tell a bit about the crash - what caused it, and how did you
recover from it?

Is the W2K computer running as a domain controller? Is the WXP computer a
member of the domain?

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.

Relevant Pages

  • Re: Lock down sign to one user
    ... Open Local Security Policy - secpol.msc and go to local policies/user rights ... For instance you could have just administrators and the specified user ... > only login to that PC and set logon hour restrictions but I want to ...
    (microsoft.public.security)
  • Re: Login failed for user (null)
    ... > Not associated with a trusted SQL Server connection. ... > server or to impersonate users. ... > However, if you deal with the Domain controller, most of the controls there ... > then go to the Local security policy and add users there. ...
    (microsoft.public.sqlserver.connect)
  • Re: Login failed for user (null)
    ... > Not associated with a trusted SQL Server connection. ... > server or to impersonate users. ... > However, if you deal with the Domain controller, most of the controls there ... > then go to the Local security policy and add users there. ...
    (microsoft.public.sqlserver.security)
  • Re: Login failed for user (null)
    ... > Not associated with a trusted SQL Server connection. ... > server or to impersonate users. ... > However, if you deal with the Domain controller, most of the controls there ... > then go to the Local security policy and add users there. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Login failed for user (null)
    ... > Not associated with a trusted SQL Server connection. ... > server or to impersonate users. ... > However, if you deal with the Domain controller, most of the controls there ... > then go to the Local security policy and add users there. ...
    (microsoft.public.inetserver.asp.db)