Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Microsoft
[Top] [All Lists]

RE: Preventing multiple logins in 2003

Subject: RE: Preventing multiple logins in 2003
Date: Mon, 31 Jan 2005 21:43:25 -0800

We looked at this for a while and decided it was not worth the $.

That being said, a free solution is to set your users home drive (on a
network share obviously) to only allow one concurrent connection and add
logic at the end of the logon script (we use .vbs scripts) to check whether
or not that users home drive was mapped - if it was, then they are not
logged on elsewhere, if it is not mapped, then either the file server is not
available, or the user has that share locked on another workstation.
Obviously you should be using DFS or some other mechanism to limit your
exposure to a single point of failure and add logic to check that the file
server is available and is simply refusing the connection. We never got any
further than that, and in the preliminary testing, we needed more than one
concurrent session available to the users - no I don't remember why...

Anyway, with the advances in WMI, and the exposure of system objects through
Windows Scripting Host, you can accomplish a great deal with logon
scripts...

Just my 2cents...

Ken Howard


"Whoever fights monsters should see to it that in the process he does not
become a monster." Friedrich Wilhelm Nietzsche

-----Original Message-----
From: Miroslaw Slawek Chorazy [mailto:mchorazy@depaul.edu] 
Sent: Friday, January 28, 2005 3:50 PM
To: larobins@bellatlantic.net; ian.turnbull@mpsgi.com;
focus-ms@securityfocus.com
Subject: RE: Preventing multiple logins in 2003

cconnect exposes the password that is needed to connect to the SQL database
in clear in the registry!

slawek

"Laura A. Robinson" <larobins@bellatlantic.net> 1/27/2005 19:20

Have you tried cconnect?

Laura 

-----Original Message-----
From: Ian Turnbull [mailto:ian.turnbull@mpsgi.com]
Sent: Wednesday, January 26, 2005 12:22 PM
To: focus-ms@securityfocus.com
Subject: Preventing multiple logins in 2003



Folks,
 
It has been noted that some of our user base are allowing other 
members of staff to login using their user account. We are currently 
in the process of moving to a fully functional
2003 domain and I would like to disable concurrent logons via group 
policy. Any suggestions?
 
Regards
 
Ian

--------------------------------------------------------------
-------------
--------------------------------------------------------------
-------------



---------------------------------------------------------------------------
---------------------------------------------------------------------------



---------------------------------------------------------------------------
---------------------------------------------------------------------------

This communication may contain Heald College confidential and proprietary data.
Any questions should be directed to a Heald College IT administrator.

---------------------------------------------------------------------------
---------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>
  • RE: Preventing multiple logins in 2003, Howard, Ken <=