If its a windows client, you could probably climb into their NetBIOS and
find out their logon ID, the name of the client, all sorts. Depends if
they've got it all turned on, and on a LAN its very likely. I've seen this
information appear at the server end of other client/server apps, but I
suspect its the client that sends the information. From a security
perspective, grabbing it server side has substantial benefits.
regards, Ben.
At 11:34 22/01/01 +0100, you wrote:
>Hi,
>
>is there any plan, to implement a feature that tells you WHO is already
>connected to some client? What I mean is, if you connect to a client, where
>someone already is connected, you can set "CennectPriority" to "2" to deny
>the new connection, which is good. But since we have quite a few
>administrators spread over some buildings, it would be good to see who is
>connected there (perhaps some reverse DNS lookup, or ARP cache readout?).
>
>Lars
>
>----------------------------------------------
>Lars Oeschey - Media Saturn GFI
>IT Security
>visit The C.O.R.E. @ http://www.the-core.net
>---------------------------------------------------------------------
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
