Discussion Locked

Can't login locally

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am trying to log on my windows2k professional PC as administrator. After entering the password I am getting an error message " The Local Policy of the system does not permit you to logon interactively". Will some one help me to overcome from this problem?

12 replies

by ithink2020

Well I have a question. Are you loging in to
a local computer or to a server or domain
controller?

If you are loging on to your local computer,
you may have chaged some of the
Administrators rights. Do you have a second
user name withAdministator rights? If so
you can login and check those rights.

Also, if you are trying to login, try using
"Administrator" rather than "administrator."
login is case sen

by a.shaikh

I am trying as administrator only. I dont have any other admin.. equiwalent account.

by stillatit

Note -- this solution works for NT 4, and probably works on Win2K, but the prompts will be different. On NT 4 you need to have User Manager for Domains, which is installed by default on a PDC or BDC, but can be installed on a workstation or 95 computer from the CD.

From another computer on your network where you have access to the administrator account, do the following:

Change the password on the administrator account on the second machine to be exactly the same as the password of the administrator account of the "bad" machine.

Start user manager for domains (NT), or the equivalent Win2K process.

In the File menu, click on Select Domain.

In the domain name box, type \\computername where computername is the netbios name ofthe "bad" machine. Click OK.

You are now editing the security information of the "bad" machine. Go to the Policies menu, select User Rights, and check the right called "Log on locally" and add users and groups as desired.

By the way, you really should have an admin equivalent account around somewhere. Also, put the explicit users, not just the groups in the Log on Locally right. Doing so means that more things have to be messed up before you are locked out.

Good luck.

by dragon emperor

It sounds like the policy got changed on the system so that all users and groups were removed from the Logon Locally access permission are. Is this system in a domain? If so then have the domain administrator check the policy to make sure that thelocal administrator can login locally. If it is not a member of a domain and the physical local policy has been changed to loc you out then try running the policy editor on another system and point it to that one (if logining in remotely is also disabled then you would need to boot through a disk to circumvent the security and modify things directly (unless there is something important on the system it would probably be best to rebuild the system rather than do that).

by nagazaki

try this :

log on as network admin on another machine of your network, start, run, type in mmc & enter. Than console, add-remove snap-in, add, choose group policy and connect the the "bad" computer.

Than go to computer config, windows setings,local policies, user rights assignment choose logon locally and modify the value to allow administrator to log on.

Don't forget to log in the remote controller pc with a user having enough rights on the target computer.

Well hope it helps

by james schroer

We had this exact same problem with all our W2K machines. What we did was logon to the domain. Join a workgroup. Go to the server and delete the computer from the active directory. Then recreate that computer in active directory. Go back to the computer and rejoin that domain. It worked for us for the time being, but don't know why it happend.

This discussion is closed to new replies.