Discussion Locked

Locked Out

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I wasn't paying close attention and accidentally locked myself out of a Windows 2000 Server. It is giving me a dialog box "The local policy of this system does not permit you to log on interactively". This happened once before on a workstation andas a result of fixing the workstation, I believe I accidentally copied the security settings of the workstation policy to the server but did not realize it until after I rebooted the server a month later. I used the ntrights.exe from the resource kit as recommended by technet to try and remove any users/groups from the SeDenyInteractiveLogonRight but it isn't working. When I tried to analyze the security database (secedit.db) using the mmc, it reported that the database was corrupt. Does anyone have any ideas of what steps to take next or should I just spend a weekend rebuilding the server? Thanks!

5 replies

by beermonster

Hi,
I haven'ttried this but it might work....assuming this is a member server - go to a workstation \ server in the same domain, log in as domain admin, and select start \ run \ mmc

select console \ add remove snap in
on the standalone tab, select add, in the list that appears select group policy, click add, then browse, select the computers tab and select or type in the name of your server. This will open up the group policy object on the server you have problems with. right click on the root, and select properties. In the window that appears select to disable machine settings. The machine settings is the policy file that contains the deny \ allow log on locally right. Reboot, and see if that makes any difference. If not, you could try setting the default domain policy on the dc's to specifically allow you access. Anything set here will overide local policies. Hope it goes ok.....

by vh_s

Though you have yourself locked out to 'Log On Locally', you would still have the permission to access the server through network, right ??

What I would do in NT 4.0 is to install the Server Management Tools in one of the workstation. It contains2 directories for different OS, this is: Win9X and Windows NT. You would have program like: User Manager, Server Manager and Policy Editor.

Install in workstation, run User Manager from the workstation (for your workstation OS), and voila ..., choose Account Policy.

Hope it helps.

by sygnatech

One thing I failed to mention is that this is a W2k box on a NT 4.0 domain. Therefore I don't think running user manager is going to help me out on that particular box. And besides that, it is the local policies that are screwed up, not the domainpolicies. For some reason the local policy is overriding the domain policy, probably because th server is W2k on a NT 4.0 domain. I decided I'm just going to wipe out the server this weekend and rebuild it. Thanks for taking the time to respond!

This discussion is closed to new replies.