thin client - Terminal Services - can a user's physical location be identified? -



thin client - Terminal Services - can a user's physical location be identified? -

when using terminal services (maybe or maybe without citrix add-ons), can physical location of user identified?

the client workstation h/w mixture - windows pc, other times lean client unit (eg wyse, etc).

our app needs vary business functionality based, essentially, on location of user. instance, compliance different state laws, or cash handling (a cash drawer can used workstation @ branch or store, can't accessed other branches or stores).

also can't depend on user's logon identify location - while users working @ 1 location, users travel 1 location another. having different logons each location not option, security , audit reasons.

other asking user (a problematic solution, sure), there apis, systemic back upwards or techniques addressing type of need?

thanks!

on remote desktop server, can identify approximate physical location of user based on ip address. can obtain remote ip address associated session using win32 api function winstationqueryinformationw info class winstationremoteaddress. if using .net language, can utilize cassia library -- remote ip endpoint exposed iterminalservicessession.remoteendpoint. not confuse remote ip address client-reported ip address available rds api -- client-reported ip not homecoming client's public ip if client is, example, behind nat router -- homecoming private ip address instead.

once have client's ip address, can utilize api geoip physical location of client.

terminal-services thin-client

Comments

Popular posts from this blog

How do I check if an insert was successful with MySQLdb in Python? -

delphi - blogger via idHTTP : error 400 bad request -

postgresql - ERROR: operator is not unique: unknown + unknown -