![]() |
![]() |
|
|||
![]() | |||||
![]() |
On the other hand, WinVNC will run on Windows 95, Windows98, Windows NT 4.0, Windows 2000 and on any future Win32-based systems, without the need to replace any system files or run any OS-specific versions of the program. It is a standard application that can be run from the Start... menu and closed down just as easily.
WinVNC can also be run as a service, which means that you can log in remotely, do some work, and log out again. We recommend that you run it in this mode. See below for more details.
And, of course, WinVNC is free. We hope that making the source code available will enable others to suggest improvements to any and all aspects of WinVNC.
You can connect to the server from another machine using a VNC viewer, such as VNCViewer or PalmVNC.
Incoming Connections
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! The default update handling settings should be the right ones for most people, and in general you will slow things down by changing them, so don't do this unless you have applications which cause problems.
Windows NT 'features':
Select "Install WinVNC service" from the WinVNC Administrative Tools section of the Start menu.
Or:
Open a Command Prompt and run WinVNC with the -install option. eg:
D:\> C:
C:\> cd "\Program
Files\ORL\VNC"
C:\Program Files\ORL\VNC> winvnc
-install
Windows NT : The WinVNC service is installed and set up to run
whenever the machine is booted into Windows NT but IS NOT YET
RUNNING! It will run when the machine next reboots. If you want to
start it immediately, you can use the Services section of the Windows
control panel, or "net start" from the command prompt:
C:\>
net start winvnc
The service should now be running, but won't
know that you are logged in until you log out and back in again. It
won't yet appear on the taskbar. You can run the WinVNC Service Helper
from the start menu to tell it who you are!
NOTE : Windows 95 : If Win95 has been set to use different settings for each user then the settings used are those of the currently logged in user. If no user is logged in or Win95 is set to use the same settings for all users then the settings used are the Default user settings and are stored per-machine, rather than on a per-user basis as is done when running WinVNC normally. (Under Win95, pressing Cancel on the login dialog gives access to the Default user settings.)
NOTE : A message about failure to remove the service usually indicates that it was not installed in the first place!
The full command-line options available are as follows. You probably won't need anything other than those listed above unless you're a real VNC power-user!
If no options are given then WinVNC runs normally. Multiple options may
be given, so, for example, to upgrade a currently running WinVNC service
to a new version, you could use:
WinVNC_new -remove -install
which will stop & remove the old copy & install the new one as
a service, or
WinVNC_new -kill -run
which will stop the
running copy & run the new version as an application.
Versions 3.3.2 R5 and later use a more sophisticated organisation of these options to allow more flexibility. It also makes it rather complex, so we're thinking about alternative ways of doing this. WinVNC will currently look for settings in the following places:
AllowLoopback
By default,
WinVNC servers disallow any vncviewer connections from the same
machine. For testing purposes, or, potentially, when using
multiple instances of WinVNC on Windows Terminal Server, this behaviour
is undesirable. Setting this registry entry to 1 will cause
local-loopback connections to be allowed. Setting it to zero will
filter out such connections. Local machine-specific setting.
AllowProperties
If this is set
to zero, the user is not allowed to view the properties dialog and hence
cannot change any settings, including the password. Note that this
stops all global per-user settings. A valid password must therefore be
in force before using this setting, generally in the local default-user
setting. Local per-user setting.
AllowShutdown
If this is set to
zero, the user is not allowed to close down WinVNC. Local per-user
setting.
AuthHosts
The AuthHosts setting
is, unlike the other settings, a REG_SZ string. It is used to specify a
set of IP address templates which incoming connections must match in
order to be accepted. By default, the template is empty and connections
from all hosts are accepted. The template is of the form:
+[ip-address-template]
?[ip-address-template]
-[ip-address-template]
In the above, [ip-address-template]
represents the leftmost bytes of the desired stringified
IP-address. For example, +158.97 would match both 158.97.12.10 and
158.97.14.2. Multiple match terms may be specified, delimited by
the ":" character. Terms appearing later in the template take precedence
over earlier ones. e.g. -:+158.97: would filter out all incoming
connections except those beginning with 158.97. Terms beginning with the
"?" character are treated by default as indicating hosts from whom
connections must be accepted at the server side via a dialog box. The
QuerySetting option determines the precise behaviour of the three
AuthHosts options. Local machine-specific setting.
QuerySetting
The QuerySetting
allows individual users to tailor the degree of paranoia expressed by
the per-machine AuthHosts setting. It is a DWORD value ranging from zero
(maximum availability) to four (maximum security). The following table
indicates how the value affects the AuthHosts behaviour:
0 -
+:Accept, ?:Accept, -:Query
1 - +:Accept, ?:Accept, -:Reject
2 -
+:Accept, ?:Query, -:Reject [Default]
3 - +:Query, ?:Query, -:Reject
4 - +:Query, ?:Reject, -:Reject
By default, value 2 (Obey
AuthHosts) will be assumed. Local & global per-user setting.
QueryTimeout
The QueryTimeout
setting indicates the number of seconds for which the Accept Connection
dialog (see AuthHosts and QuerySetting options) will be displayed before
rejecting the incoming connection automatically. Local & global
per-user setting.
AutoPortSelect
Causes WinVNC to
select the first available display number automatically. Corresponds to
the 'Auto' checkbox in the Properties dialog. Local or Global
per-user setting
CORBAConnect
Only relevant in
internal AT&T version. Local or Global per-user setting
DebugLevel
DebugMode
Run-time logging of all internal
debug messages is now supported. Log data may be output to a file or a
console window (or the MSVC debugger if the program was compiled with
debugging active.) Two registry keys are used:
DebugMode indicates which logging methods to use,
[1 =
MSVC debugger]
2 = Output to log file Winvnc.log in the WinVNC
directory
4 = Output to a console window, displayed on-screen
Any combination of the above values may be used. e.g.
DebugMode=6 will cause output to be sent both to the WinVNC.log file and
to the a console window on the desktop.
DebugLevel indicates how much debug information to present. Any positive integer is valid. Zero indicates that no debugging information should be produced and is the default. A value of around 10-12 will cause full debugging output to be produced. Local machine-specific setting.
ConnectPriority
By default, all
WinVNC servers will disconnect any existing connections when an
incoming, non-shared connection is authenticated. This behaviour
is undesirable when the server machine is being used as a shared
workstation by several users or when remoting a single display to
multiple clients for vewing, as in a classroom situation.
ConnectPriority indicates what WinVNC should do when a
non-shared connection is received:
0 = Disconnect all existing
connections.
1 = Don't disconnect any existing connections.
2 =
Refuse the new connection.
This is a Local machine-specific setting.
InputsEnabled
Corresponds
(inversely) to the 'Disable Remote keyboard and pointer' option in the
Properties dialog box. Local or Global per-user setting
LockSetting
WinVNC can be made
to take actions when a viewer disconnectsby setting this value as
follows:
0 - none
1 - lock workstation on disconnect (not
currently implemented)
2 - logoff on disconnect
Local or
Global per-user setting
LoopbackOnly
By default, WinVNC
servers accept incoming connections on any network adapter address,
since this is the easiest way of coping with multihomed machines. In
some cases, it is preferable to listen only for connections originating
from the local machine and aimed at the "localhost" adapter - a
particular example is the use of VNC over SSH to provide secure
VNC. Setting this registry entry to 1 will cause WinVNC to only
accept local connections - this overrides the AllowLoopback and
AuthHosts settings. Setting this entry to zero causes WinVNC to
accept connections on any adapter and is the default setting.Local
machine-specific setting.
Password
Local or Global
per-user setting
PollUnderCursor, PollForeground,
PollFullScreen, OnlyPollConsole, OnlyPollOnEvent
These
correspond to the options in the Properties dialog box. Local or
Global per-user settings
PortNumber
specifies the port
number to be used for VNC. You will need to disable AutoPortSelect to
use this.
Local or Global per-user setting
SocketConnect
This corresponds
to the 'Accept Socket Connections' option in the properties dialog box
and is a Local or Global per-user setting.
HKEY_CURRENT_USER\Software\ORL\VNCHooks\Application_Prefs