Game Download

Installation

Using VNC Server in User Mode

Configuring VNC Server

Accept connections on port
PortNumber=(port number)

• If this option is ticked and the port number is non zero then VNC Server accepts incoming connection requests from clients on a particular TCP port. 
• The standard VNC Display numbers, 0-99, correspond to TCP ports 5900-5999. 
• VNC Server will accept connections on port number 5900 by default, which equates to VNC display number 0 (zero). 
• The port number for VNC Server to use can be set to any other available port number, even ones outside the 5900-5999 range.

Disconnect idle clients after
IdleTimeout=(seconds)

An idle client is one which has transmitted no keyboard or pointer events for more than a certain length of time. The VNC Server can be configured with a threshold, expressed in seconds, after which idle clients will be disconnected to conserve resources. If the threshold specified is zero seconds then connections will never timeout. The default idle timeout is one hour.

Serve Java viewer via HTTP on port

HTTPPortNumber=(port number)

If this option is ticked and the port number specified is non-zero then VNC Server will accept incoming HTTP requests, allowing the Java VNC Viewer to be downloaded by a Java-aware web browser. The Options... dialog will attempt to adjust the HTTP port to match changes made to the VNC port number.

Note that the HTTP port number cannot be set to the same value as that used for incoming VNC connections.

Only accept connections from the local machine
LocalHost=true|false

The LocalHost option tells VNC Server to only accept incoming connections from Viewers running on the local host computer. This is only normally used when connections are to tunnelled through a custom transport (e.g. serial line, custom wireless, etc) and will therefore appear to the TCP stack to originate from the local host. If VNC Server is configured to accept connections only via local loopback then the Hosts option is ignored.

Access Control
Hosts=(pattern)

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.

Available actions are:

• +: Accept the connection
• ?: Query the local user to accept the connection.
• See also the QueryConnect Authentication option.

Reject the connection.

e.g. Hosts=+192.168.0.1/255.255.255.255,+192.168.1.0/255.255.255.0,-

The pattern given above allows the computer with address 192.168.0.1 to connect, as well as any computer in the 192.168.0.1 subnet. All other connections are rejected by the term, which is actually redundant in this case , a connection will always be rejected if it doesnt match anything in the Hosts pattern.

Note that IP addresses and masks are specified in 

Type-A (xxx.yyyyyyyyy), 

Type-B (xxx.yyy.zzzzzz) or 

Type-C (xxx.yyy.zzz.www) form. 

The specification 192.168 will therefore be interpreted as 192.0.0.168 rather than 192.168.0.0 as one might expect.

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.

No Authentication
SecurityTypes=None

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
SecurityTypes=VncAuth

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.

NT Logon Authentication

• NT Logon Authentication is not available in VNC Open.
• Encryption: Always Off (Encryption is not available in VNC Open.)

Prompt local user to accept connections
QueryConnect=true|false

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 servers 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.

Only prompt when there is a user logged on
QueryOnlyIfLoggedOn=true|false

This option affects the behaviour of the Query Connect 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.

Query Connect Timeout=(seconds)

If Query Connect 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.

Accept pointer events from clients
AcceptPointerEvents=true/false

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 Servers 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.

Accept keyboard events from clients
AcceptKeyEvents=true/false

If this option is unticked then incoming keystrokes from all clients will be ignored, preventing any remote VNC Viewer from typing into the VNC Servers 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 keyboard events to the server, whether or not they are accepted.

Accept clipboard updates from clients
AcceptCutText=true/false

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 Servers local clipboard when this would be undesirable or confusing.

Send clipboard updates to clients
SendCutText=true/false

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.

Allow input events to affect the screen saver

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.

Disable local inputs while server is in use
DisableLocalInputs=true/false

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.

Always treat new connections as shared
AlwaysShared=t

visit link download

Related Post

Posted by Unknown at 7:19 PM

Email ThisBlogThis!Share to TwitterShare to Facebook