Strange screen saver problem

Brian Knotts bknotts "at"
Tue, 03 Mar 1998 14:25:31 +0000


On Tue, 3 Mar 1998 10:25:57 +0000 (GMT), James [Wez] Weatherall wrote:

>On Tue, 3 Mar 1998, Brian Knotts wrote:
>> This occurs whenever the Windows NT host is in screen saver mode ("Logon
>> Screen Saver") or when the logon screen is present. Only the normal
>> desktop view succeeds in displaying in vncviewer.
>It's a known limitation of WinVNC that it cannot handle non-user desktops.
>Desktops are a mechanism used by Windows NT (not Windows 95 or 98) to
>isolate tasks that need to be secure, such as the logon shell and
>locking/unlocking of workstations.  Included in this is the screen-saver.
>Unfortunately, this means that since WinVNC runs on the desktop of the
>logged-in user, it can't access the logon or screen-saver desktops.  The
>result is that you attempt to connect to the server and the connection
>fails in the manner you describe.  To avoid this, WinVNC always tries to
>close down the screen-saver if it is running, when a connection is made.
>This is partly why it isn't currently possible to use WinVNC to
>lock/unlock or logon/logoff NT boxes.
>I hope that answers your question.

Yes; thanks. I hadn't noticed that before. I guess I'm still a bit confused by VNC's concept of 

I assume it would need to become an NT service for this to be possible, then?

Currently, I've resorted to running the machine headless with no screen saver/lockup. But that's a 
little risky. It's nice to be able to have the machine inaccessible from the console.

- --
Brian Knotts          bknotts "at"

Version: 2.6.2