Name: warings Date: May 4, 2004 at 06:16:18 Pacific Subject: Users and NT 4.0 OS: NT 4.0 SP6a CPU/Ram: 1024
Comment:
I have a computer lab that is made up of windows XP machines, and everyone that uses that lab has there own domain account, NT 4 domain, is there away that i can dis-allow another user, such as a generic student account, to log into those machines?
yes the guest account is disabled, but they are using a generic account that we use for all the student computers in the classrooms, and i do not want them to be able to use that account in this one lab.
I can't do that, I need that account to be active for others to use. that’s part of my problem. And yes they are all domain accounts. What I need is away to tell the generic user that if it tries to logon to a computer it shouldn't be logging in to then tell it somehow it would fail
I don't see the problem. You have a generic Domain User Account. (Not a good idea, but that's beside the point). You want the users to login using this account in certain labs, but not in one particular Lab. Is that correct?
If so, do as I suggested. On the machines that you DON'T want the generic account to have access, deny login capabilities.
UNLESS I have this wrong, and you're talking about one specific person who knows this generic login, and you want everyone else to be able to use it and not this particular user...
Can you not add the names of the pc's in the valid lab to the 'computers allowed to log in' in the User Manager on the NT Server.
The other way would be to move the IP range of this lab out of the usual range and 'hide' from the other parts of the LAN, you may need to set a router if that lab want's to access areas outside the local lan, but NT can manage that too.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE