(Windows) Is there a way to prevent a user to login into 2 different computers on a local network at the same time ?
-
(Simple question) Is there a way to prevent a user to login into 2 different computers on a local network at the same time? Thanks. Max.
I'd rather be phishing!
-
(Simple question) Is there a way to prevent a user to login into 2 different computers on a local network at the same time? Thanks. Max.
I'd rather be phishing!
Good question. I've seen WTFy hacks for that purpose only. Looks like there is not a good solution available.
-
(Simple question) Is there a way to prevent a user to login into 2 different computers on a local network at the same time? Thanks. Max.
I'd rather be phishing!
There used to be a couple of hacks from Microsoft called CConnect and LimitLogin[^] that came with Windows 2000 resource kit. I have some doubts that it works on Server 2008. Another solution is of course to use Remote Desktop. :sigh:
Wrong is evil and must be defeated. - Jeff Ello[^]
-
(Simple question) Is there a way to prevent a user to login into 2 different computers on a local network at the same time? Thanks. Max.
I'd rather be phishing!
-
This is related to software licenses (without a license server (*)) bound to a user name (i.e. only user "Joe" can use the software); this means that "Joe" could log in on different machines and use the software. Currently, we generate licenses bound to some hardware keys (NIC/HardDisk); so if the machine dies we have to generate a new license (and that bugs a potential client that we really want to have) and they have to get back to use to generate a new license. (*) We already use hardware USB license key; and will probably look into a proper license server (like flexlm). Thanks.
I'd rather be phishing!
-
This is related to software licenses (without a license server (*)) bound to a user name (i.e. only user "Joe" can use the software); this means that "Joe" could log in on different machines and use the software. Currently, we generate licenses bound to some hardware keys (NIC/HardDisk); so if the machine dies we have to generate a new license (and that bugs a potential client that we really want to have) and they have to get back to use to generate a new license. (*) We already use hardware USB license key; and will probably look into a proper license server (like flexlm). Thanks.
I'd rather be phishing!
In that case you want to lock your software, and not the entire terminal. Unless the PC is yours, it's not yours to lock. How is the software structured? Do they use their licensed client to contact a server that runs your software? If yes, then that would be a nice place to block access.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
In that case you want to lock your software, and not the entire terminal. Unless the PC is yours, it's not yours to lock. How is the software structured? Do they use their licensed client to contact a server that runs your software? If yes, then that would be a nice place to block access.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
We do not change the client systems (other than what we install via the installer) and do want to. If it were possible, then we could have discuss the possibility with our clients as an interim solution before setting up a proper license server. There is no server (yet). I was looking for a confirmation if that was allowed on Windows or not. Thanks.
I'd rather be phishing!
-
We do not change the client systems (other than what we install via the installer) and do want to. If it were possible, then we could have discuss the possibility with our clients as an interim solution before setting up a proper license server. There is no server (yet). I was looking for a confirmation if that was allowed on Windows or not. Thanks.
I'd rather be phishing!
Maximilien wrote:
I was looking for a confirmation if that was allowed on Windows or not.
Depends on what the local admin allows on his network. You'll need a server (under your administration), it's that simple. Either one that's online, or on-site. Could be a cheap Raspberri Pi in a lockable box. Then you could have each client tell that server when it is online, and under which user. If a user is already online, simply tell the second instance (over TCP/IP e.g.) that it should shut down. Encrypt your connection and include a timestamp to prevent people from recording and playing back sessions. Also be sure to implement a heart-beat to your server; that's the easiest way to detect when a connection is dropped, or a process died. See, access to your application can be blocked; but blocking the machine would be considered a hostile act :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]