Security

Ask something
Discussion Locked

How to limit concurrent logins in NT??

0 helpful
12 replies

by vivek chudgar

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

For security reasons, I want to ensure that a username CANNOT be used to login to the Domain if someone is already logged in with that username.

If u think of it...it's a pretty basic need for beefing up security, however there's no way to do this with NT(Novell has a feature where u can limit the concurrent logins for a pertucular username).

So how can we do this? Think about it guys....it's really worth it if we could find a technique to do this.

Regards,
Vivek Chudgar

12 replies

by Member 18614994

To manage logon workstations

1 Click Logon From in the New User, Copy Of, or User Properties dialog box.

2 Select either User May Log On To All Workstations or User May Log On To These Workstations.
3 If you select User May Log On To These Workstations, type a computer name in at least one and up to eight of the numbered boxes.

Note

The default is to allow a user to log on from any workstation, but you can restrict a user to logging on from only specified workstations.

by tjohns

I am also very interested in learning how to do this. Is it really impossible? The solution posted by Christie doesn't fix the problem: I want a user to be able to log into any workstation in the domain, but only into one workstation at a time. I donot want to restrict which workstations a user can log in to. Any way to do this? Help!!

tjohns@integ.com

by lewisb

One way of doing this might be to write some code in your login/loggoff scripts to pick up the workstation ID on login, store it and delete when logging off. You can then compare the field on each login - if empty, user hasn't logged in, if a value,then user is already logged in and the script could then not allow additional logins to complete.

I do not have code (in case you are going to ask) but would think this shouldn't be hard for your script pros to do. No guarantees etc

by vivek chudgar

Christie,

U r rite..we can do this. But this will limit user's mobility...and also increase the Admin work. In my 4 yrs of experience with NT...i haven't come across any Admin who's using this feature of NT which limits login from a perticular PC...

So i'm tryin to think of a solution whereby a user can login only once...but from any PC.

Think about it from this angle...

It'll be great if we can think of something worthwhile...

by pablocaballero

I would like to tell you beforehand that my english is very poor.

1.- Create a share in which only the user
had permissions, limit to one (1) the concurrent conections to that share and assign it to the user as his/her home directory

2.- In the login script check if there is a conection to that share. If so, it's OK; on the contrary, it should indicate that the user is already connected from another workstation (as he/she couldn't connect again to the share because of the concurrent conection limitation) At this point, the user
should be disconnected by means of any tool (the resource kit "shutdown", API calls, etc)

3.- AVOID THE FIRST USER CONECTED USER FROM DISCONNECT FROM THE SHARE AND NOT LOGOFF!!!!!

4.- i await opinions

by pablocaballero

I would like to tell you beforehand that my english is very poor.

1.- Create a share in which only the user
had permissions, limit to one (1) the concurrent conections to that share and assign it to the user as his/her home directory

2.- In the login script check if there is a conection to that share. If so, it's OK; on the contrary, it should indicate that the user is already connected from another workstation (as he/she couldn't connect again to the share because of the concurrent conection limitation) At this point, the user
should be disconnected by means of any tool (the resource kit "shutdown", API calls, etc)

3.- AVOID THE FIRST USER CONECTED USER FROM DISCONNECT FROM THE SHARE AND NOT LOGOFF!!!!!

4.- i await opinions

by pablocaballero

I would like to tell you beforehand that my english is very poor.

1.- Create a share in which only the user
had permissions, limit to one (1) the concurrent conections to that share and assign it to the user as his/her home directory

2.- In the login script check if there is a conection to that share. If so, it's OK; on the contrary, it should indicate that the user is already connected from another workstation (as he/she couldn't connect again to the share because of the concurrent conection limitation) At this point, the user
should be disconnected by means of any tool (the resource kit "shutdown", API calls, etc)

3.- AVOID THE FIRST USER CONECTED USER FROM DISCONNECT FROM THE SHARE AND NOT LOGOFF!!!!!

4.- i await opinions

by ntoz

The Windows 2000 Resouce kit contains a utility to limit concurent logons, cconnect. It requires the use of a database but it does work.

by brianjp

This is piece of software produced for NT that will do what you have been talking about. After installation (and it is very simple - couple of mins of a job) you can allocate a user to be a member of a group that will allow only 1 login at a time, or 2, or even 3. Have a look at www.flocs.co.uk for further details. I only mention it as I use it at work - handling roaming users across 100+ workstations in 5 widespread geographical locations AND it works.

This discussion is closed to new replies.