Sign in Sign out. Capabilities Summary Device access and instant support together cover every remote access use case Device access Access computers you own or manage at any time, from anywhere Instant support Quickly access anyone's computer without installing remote access software.
Provide a consolidated remote access strategy that evolves with your business Remote access tutorial New to remote access? Read our one-stop-shop tutorial Customer success stories Learn how our customers save time and money, increase efficiency and reduce risk Competitor comparisons See how we provide better value that TeamViewer, LogMeIn, Bomgar and more Marketing resources All our whitepapers, product brochures, ebooks and webinars in one place.
Our partners Resellers See a list of all our reseller partners around the world Distributors See a list of all our distributor partners around the world. For more information, please read our privacy policy.
Got it. Download VNC Server 6. Related downloads Policy template files Remotely configure and lock down programs using policy. Frequently asked questions. How do I license the software? Can I download an older version? How do I connect? Start with the FAQ. MSI installers. Vista and later. This is only normally used when connections are to tunnelled through a custom transport e. If VNC Server is configured to accept connections only via local loopback then the Hosts option is ignored.
VNC Server can filter incoming connection attempts based upon the apparent IP addresses of their originators. Which IP addresses are allowed to connect and which are not is determined by the Hosts pattern. The pattern consists of a comma-separated list of IP address specifications, prefixed by an action. Each specification starts with an action, gives an IP address, and a subnet-style mask. The first specification to match the address of the new connection determines the action that will performed.
The pattern given above allows the computer with address All other connections are rejected by the - term, which is actually redundant in this case - a connection will always be rejected if it doesn't match anything in the Hosts pattern. Note that IP addresses and masks are specified in Type-A xxx. The specification The Hosts pattern can be edited more easily through the Access Control interface, which allows IP address specifications to be edited individually and moved up to match first or down to match last the list.
The Authentication page allows you to configure the required mode of authentication and level of security of VNC connections. If your VNC Server is operating in a protected environment, such as a secure LAN or firewall-protected network, then you may wish to configure VNC Server to accept connections without requiring a username or password to be specified. We advise extreme caution when disabling authentication. Do not disable it unless you are absolutely sure that the host network is completely secure.
VNC Password Authentication allows a single password of up to 8 characters to be stored by VNC Server, which remote users must supply when prompted in order to authenticate. The password to use can be configured by selecting Configure and typing the new password twice. On platforms which support it, the password and all other configuration options are protected using native operating system security methods, so that the password cannot be read or tampered with by other users.
By default, VNC Server allows Viewers to connect as long as the correct username and password are supplied. QueryConnect allows an extra level of protection to be applied, requiring a local user to explicitly accept incoming connections. When QueryConnect is enabled, incoming connections are first authenticated in the normal way.
If the user authenticates successfully then a dialog is presented on the server's desktop, displaying the IP address and username of the incoming connection, and requiring a local user to accept the connection.
If the user does not accept the connection within a specified timeout then it is rejected. If an incoming connection requiring acceptance by the local user is received while an earlier connection is being queried then the second connection is automatically rejected, for security reasons. Connections from specific hosts or subnets can be configured to be queried via the Hosts configuration setting.
This option affects the behaviour of the QueryConnect option, if enabled. If this option is set then the local user will only be prompted to accept the incoming connection if they are logged in. If this option is not set then the local user will always be prompted, regardless of whether or not they are logged in.
Note that it is not possible to reliably detect whether or not a user is logged in on some older Windows platforms. On these platforms, this option will err on the side of security and always prompt the local user. If QueryConnect is enabled then the Query Connection dialog will be displayed by default for ten seconds before automatically rejecting the connection. The timeout value can be modified by setting QueryConnectTimeout accordingly. If this option is unticked then incoming pointer movements from all clients will be ignored, preventing any remote VNC Viewer from affecting the pointer of the VNC Server's desktop.
This can be used to configure a server to become effectively view-only. Note that a client will still be deemed active for the purposes of the IdleTimeout setting if it is sending pointer events to the server, whether or not they are accepted. If this option is unticked then incoming keystrokes from all clients will be ignored, preventing any remote VNC Viewer from typing into the VNC Server's desktop. Note that a client will still be deemed active for the purposes of the IdleTimeout setting if it is sending keyboard events to the server, whether or not they are accepted.
If this option is unticked then incoming clipboard updates will be ignored from all clients. This option should be used when making a VNC Server effectively view-only, but may also prove useful to prevent clipboard changes made by clients from overriding the VNC Server's local clipboard when this would be undesirable or confusing.
This option, if unticked, prevents the VNC Server from informing clients of changes to its local clipboard contents.
This can be useful when untrusted clients are to be allowed to connect to the VNC Server, since it prevents any private data being accidentally leaked via the clipboard. This option determines whether keyboard and mouse events received from VNC Viewers can cause the screen-saver to be hidden. This option is actually a system-wide setting and is not implemented by VNC Server itself, so there is no equivalent command-line option.
Some older Win32 platforms do not support this option. It is recommended that this check-box be ticked, so that the screen-saver can be disabled by VNC Viewer input. The mouse and keyboard physically attached to the server computer can be disabled for the duration of a remote connection, preventing local users from interacting with the computer.
If this option is set then all incoming connections will be treated as shared, and thus not disconnect any existing connections, regardless of whether the connecting VNC Viewer requested that the connection be shared. If this option is set then all incoming connections will be treated as non-shared. VNC Server will therefore either disconnect any existing connections, or refuse the incoming connection, depending on whether non-shared connections are configured to replace existing ones see below.
When connecting, VNC Viewer specifies whether the connection should be shared or non-shared. If this setting is configured then the VNC Viewer's preference will be respected. If an incoming connection is to be shared either by choice or because AlwaysShared is set then existing connections remain active.
If a connection is non-shared either by choice or because NeverShared is set then either the new connection must be rejected, or existing clients disconnected. If this setting is configured then existing clients will be disconnected when a new non-shared connection is made.
Otherwise, they will remain, and the new connection will fail. Decorations such as wallpaper or font smoothing effects can make it harder for VNC Server to compress graphical data for trasmission to viewers. For viewers connected over slower networks, this can significantly degrade the apparent performance of the server.
VNC Server can therefore simplify the desktop in several ways, to improve performance. This option causes VNC Server to remove any standard wallpaper bitmap that is set, as well as to disable Active Desktop components. This option causes VNC Server to set the desktop background to a plain pattern while conenctions are active. This option causes VNC Server to disable desktop decorations such as font smoothing, window titlebar shading, menu animation, and so on.
These options are used to ensure that if VNC connections to a server are closed because of a network error, idle timeout, or even deliberately, then the computer will be left in as secure a state as possible. On Windows and above, it is possible for VNC Server to lock the workstation, leaving the current user logged in but requiring that their password be re-entered in order to access their programs or data. Alternatively, VNC Server can completely logoff the current user when there are no more VNC viewers connected, closing any running programs and leaving the workstation ready for another user to log in.
VNC Server is designed to support a variety of techniques for tracking changes to the local desktop. This release supports basic polling of the screen for changes, as well as the classic VNC Hooks technique.
0コメント