Try the TightVNC implementation (as others have recommended).
If you also need it available for desktop maintenance (without requiring to
prompt the user), you might be able to schedule it (using the task
scheduler) to shutdown and then re-start it up in a mode that does not
require a response to the prompt during certain hours. Don't forget to then
repeat the shutdown/restart process again enabling the prompt.
Michael
At 01:04 PM 2001-11-01, you wrote:
>We are currently looking at VNC as a remote control software. It looks
>awesome in every respect except it does not appear to request a
>confirmation of connection. In our industry this is a must because of
>confidential information. Is there an add on or registry changes for NT or
>Windows 2000 that would allow a challened response or confirmation of
>connection. Any help would be greatly appreciated.
>Thanks
>---------------------------------------------------------------------
>To unsubscribe, mail [EMAIL PROTECTED] with the line:
>'unsubscribe vnc-list' in the message BODY
>See also: http://www.uk.research.att.com/vnc/intouch.html
>---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
