Web servers can only identify computers, not users. You will need something else to track which user started a specific application on a particular computer, probably a fingerprint scanner next to the keyboard. But that won't prevent someone else from replacing the entity between the keyboard and the chair after they log in. Plus, it is unlikely that will be useful in a true multi-user environment. There are simply too many possible ways to get around your restrictions. Bob McConnell -----Original Message----- From: Jagdeep Singh [mailto:jagsaini1982@xxxxxxxxx] Sent: Friday, May 14, 2010 4:26 AM To: Peter Lind Cc: Lester Caine; php-general@xxxxxxxxxxxxx >> "php-general@xxxxxxxxxxxxx" Subject: Re: Multiple Login in a single PC should not be possible Hi, yes, I can make a databse table to record LOGIN details, But I want that No other user can login on same machine on smae or another browser. E.g. If user1 has logged in from IE then user2 should not login from Firefox or Chrome etc.. I need ONLY ONE USER ACCESS AT SAME TIME ON SAME MACHINE (On Same or Other broswers) Regards Jagdeep Singh On Fri, May 14, 2010 at 1:26 PM, Peter Lind <peter.e.lind@xxxxxxxxx> wrote: > On 14 May 2010 09:29, Lester Caine <lester@xxxxxxxxxxx> wrote: > > Jagdeep Singh wrote: > >> > >> Hi All! > >> > >> I am looking for a solution, I want a user to do a single Login only on > a > >> PC > >> . > >> > >> E.g. If a User has logged on my website website.com in Internet > explorer, > >> then he cant login on same website in another browser like Firefox etc > >> with > >> same loginid or another. > >> > >> Can I trace MAC address of a single machine to solve this issue? > > > > The browser IP address works for us quite reliably. Once logged in, you > get > > a message saying already logged on ... and where ... but it does need a > > little help if the user closes the browser without logging out. One needs > a > > facility to 'bounce' a user now and again .... however some remote users > may > > well have 'floating' IP addresses :( > > > > Don't rely on IP addresses staying the same for a user, it's not safe > in any way and not needed anyway. Karls method is probably the best > bet - just remember to record "last accessed time" so anyone not > accessing for more than 15-20 minutes will succeed if trying to log in > again. > > Regards > Peter > > -- > <hype> > WWW: http://plphp.dk / http://plind.dk > LinkedIn: http://www.linkedin.com/in/plind > Flickr: http://www.flickr.com/photos/fake51 > BeWelcome: Fake51 > Couchsurfing: Fake51 > </hype> > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
