Logging on to a Win2k server as user

[mwingeier]

Okay, this one has probably been answered before, but I could not find the answer, and I am pulling my hair out because it's probably so simple.
I have a Win2k server running AD, which I want the ability to log onto as a regular user. I know that as default, this behavior is not allowed for security reasons. I get the message that local policies will not allow interactive logon.
I have changed everything I can find associated with this permission, the ability to log in locally, etc, but that hasn't helped. All it has done is succeed in changing the error message from the fact that the account can't log on at all, to the fact that the account can't log on interactively. Any clues?

 

[brontosaurus]

if it's a DC , you have to make that change on the Default Domain Controllers Policy.

 

[GlenJohnson]

Just curious as to why you would want to. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"A single stone can cause a building to collapse."
Francisco de Quevedo y Villegas (1580-1645); Spanish writer.

 

[mwingeier]

Why I would want to? Pretty simple, not enough computers in this network, and since it is a home network, having my wife log into the server poses no security risk. I'd log into it, but it is a lower powered system with a smaller hard drive than I can use, but it doesn't bother her. The other way to solve it is to give her admin rights, but then she can screw something up by accident.

 

[GlenJohnson]

Makes sense. I'm setting up a domain at home for more practice, (We don't use DHCP here at work, so that's one of the things I need more expertese in.) Figured setting up a home network would help me in passing the MS tests. Good luck. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com

"A single stone can cause a building to collapse."
Francisco de Quevedo y Villegas (1580-1645); Spanish writer.

 

[mwingeier]

Thanks. I'd like to play with the DHCP settings myself sometime, but my router is acting in that capacity, so why mess with a good thing? By the way, I found the setting. As it turns out, I had the log in locally policy defined, but nobody was in it, so it, in effect, restricted everybody. When I disabled the policy, it went like a charm.