Discussion Locked

locked out of server

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

I was tunkering with the security settings on a 2k server box, I am not sure what bit i wrongly changed, but when i now try and log in even as administrator I get the root pass rejected with a message of " no interactive logins allowed".
Any pointers of how to get back in and what settings do i need to change to reverse this error.

5 replies

by joseph moore

Are you logging into the machine locally (using the keyboard that is plugged into the Win2K Server), or are you trying to connect over a network connection, like with Terminal Services?
Because it sounds like you modified a User right you should not have.
There are a few rights that if you change them, that you can lock yourself out of the machine.
"Access this computer from the network" - if you remove all groups/users from this right, then NO ONE can connect to the machine remotely. No TS logins; no mapping drives; no accessing shared resources. Normally, Everyone has this right. You can change this to Domain Users, but that is about as restrictive as I would go (unless it is a public web server).
"Deny access to this computer from the network" - any user/group you put in this right will NOT be able to connect remotely. This will OVERRIDE the other one I just mentioned. So, be careful using any DENY right.
"Log on locally" - This group tells you who can log into the machine using its own keyboard and mouse. This is the "I'm standing in front of the computer and I want to log in" user right. This should have your Domain Admins listed, and that is all.
There is also a Deny Log on Locally, that does what you would expect to do.

So, try and log on locally. If you aren't, then try and log on remotely. Hopefully, one way or the other will let you in, and you can then make the changes to put the Win2K server back to what it was.

And be careful next time!

by benwagg

If you have disabled all interactive logins, you must administer the box remotely. Log onto the network with Administrative credentials. Do this from a Win2k Pro workstation or from another server you are willing to risk.

1. Start > Run > MMC
2. Console > Add/Remove Snap-In > Add(button)
3. Select the Group Policy snap-in
4. Browse to
5. Finish > Close > OK
6. Find the setting you locked yourself out with
7. Fix it
8. Slice your finger, mix a drop of your blood with with some dirt and garlic, and swear to never again do something silly like that and cause yourself that much grief...

Okay, well step 8 isn't actually required. Never mention this to an end user or network client. They can't be permitted to understand that we network admins don't actually know _everything_...

If you're really into humiliating yourself in front of a user who already doesn't like you, try locking the local Administrator out of a laptop the day before you have to configuresomething before he takes it on a 3-week road trip...

This discussion is closed to new replies.