Vncserver who is logged on

Poll Console Windows Only - When this option is set, the only windows which will be ever be polled are Command Prompts. This works well in conjunction with Poll Window Under Cursor, to use polling only when the cursor is over a console window.

Poll On Event Received Only - When this option is set, the screen will only be polled for updates when a mouse or keyboard event is received from the remote client. This is provided for low bandwidth networks, where it may be useful to control how often the screen is polled and changes sent. The user's settings are saved into the user-specific section of the registry when WinVNC quits, meaning that they will be used next time you run WinVNC.

This allows you to connect to a machine which has nobody logged in to it, for example. On NT, you can also send Ctrl-Alt-Del to the server when it's running as a service, allowing you to unlock a locked workstation, for example.

Note that in 'service' mode, many features are changed on a per-machine rather than per-user basis. The following 'features' should also be pointed out: Windows NT 'features': WinVNC will attempt to correctly identify the user and locate their preferred settings in the registry unless AllowProperties has been used to disable this - see below.

To do this requires that a helper application be run when a user logs in, which will pass appropriate information to the main service portion of WinVNC. If the helper fails to run for some reason then WinVNC will continue to operate but it won't know who is logged in, so its settings will be based on the local-machine and default-user settings only. Windows 95 'features': Whether or not the VNC password is set per-machine or per-user depends on the settings in the Passwords section of the Control Panel.

If Win95 is set to use a different set of registry values for each user then when a user logs in, the password will change from the per-machine VNC password to that user's VNC password. If Win95 is set to use the same settings for all users then the per-machine VNC password will always be used. Close - Shutdown the server. Incoming Connections Accept Socket Connections - The server normally accepts direct, socket-based connections from the vncviewer program.

See ORL internal version info. For the public version, clearing this will disable any incoming connections. Display Number - This allows the user to specify the display number which the server will use.

There is normally no need to change this from the default of zero. Auto - This tick box indicates to WinVNC whether it should use the display number specified in the Display Number box, or whether it should use the first display number not already in use on the server machine.

Password - Incoming connections must be authenticated to verify that the person connecting is allowed to connect to this machine. This text box allows your password to be specified for authentication. Update Handling. Note that clicking in a window will generally cause it to be updated, so if you have certain applications which don't update very well, try this!

For this reason, it is sometimes useful to be able to poll the entire screen in order to check for changes, sacrificing performance for accuracy. Poll Foreground Window - Polling only the currently selected window for changes is less CPU intensive than full-screen polling and often gives similar results, for example when using the Command Prompt, which is not normally compatible with WinVNC.

Poll Window Under Cursor - A variation on Poll Foreground Window, this option causes the window under the mouse cursor to be polled for changes. Both options may be enabled simultaneously if required. Poll Console Windows Only - When this option is set, the only windows which will be ever be polled are Command Prompts.

This works well in conjunction with Poll Window Under Cursor, to use polling only when the cursor is over a console window. Poll On Event Received Only - When this option is set, the screen will only be polled for updates when a mouse or keyboard event is received from the remote client.

This is provided for low bandwidth networks, where it may be useful to control how often the screen is polled and changes sent. The user's settings are saved into the user-specific section of the registry when WinVNC quits, meaning that they will be used next time you run WinVNC. As of Version 3. AuthRequired By default, all WinVNC servers will not accept incoming connections unless the server has had it's password field set to a non-null value.

This restriction was placed to ensure that misconfigured servers would not open security loopholes without the user realising. If a server is only to be used on a secure LAN, however, it may be desirable to forego such checking and allow machines to have a null password.

At the moment, TightVNC 1. Our focus is on making next major version of TightVNC, 1. Our goals for TightVNC 1. It's not just a plan, we are actively working on this since summer And we expect that the first version of TightVNC 1. Besides that, we plan to resume development of TightVNC for Unix that was almost stalled for a long time.

Our Privacy Policy. Disabling file transfers completely if current user is unknown or nobody is logged in. A specially modified VNC server could currupt the heap of the connected viewer causing its crash or malfunction. Windows Server: Fixed rendering problems when multiple CopyRects were combined with normal updates. Is it in the event viewer? Where exactly? Is logging turned on by default? Improve this question. MAP 1 1 silver badge 9 9 bronze badges.

GuyC GuyC 1 1 silver badge 2 2 bronze badges. Add a comment. Active Oldest Votes. Improve this answer.