How to create my own version?

1) Download custom.zip

2) Replace the icons ,bmp and rc4.key file with your own version
++Bmp need to be a windows bitmap, max colors 256, size 196x181 (16colors --> smaller size)
icons, standard window icons only 32x32 standard is needed
The bigger the icons and bmp are, the bigger the final result, the final result is 166k + compressed zip file
SAME NAMES MUST BE USED.....logo.bmp icon1.ico icon2.ico

3) Replace the rc4.key with your own version or remove the rc4.key if you don't wish to use encryption
To create your own key you need the normal UltraVnc version and dsmplugin.
The config button of the dsmplugin allow you to create another key.
SAME NAMES MUST BE USED..... rc4.key

4)  Helpdesk.txt info, see below

5)Color background:
You can add a color background by adding a file background.bmp to the zip file
Size 1x283, this bmp is stretch as background
Sample 1, Sample 2, Sample 3, Sample 4

6) Create a zip File from the files you want to customize
minimum: helpdesk.txt
maximum helpdesk.txt rc4.key icon1.ico icon2.ico logo.bmp background.bmp

MYCOMPANY.zip or jsdgf654324f.zip
Use something unique, else 2 custom versions could get mixed
DON'T use .(dot) in the name: sample WWW.XXX.zip

7) Click Creator in left panel
login: foo
password:foobar

PcHelpware Customisation

PCHelpware server layout customization

Text customization

The customization file looks like this:

[TITLE]
TITLE

[HOST]
Internet support (Encrypted Direct Connection)
-connect 192.168.1.102:5500

[HOST]
Internet support (Encrypted Repeater Connection)
-connect uvnc.com:5500 -id 543

[HOST]
Internet support (Autorecon Encrypted Repeater Connection)
-connect uvnc.com:5500 -id 543 -autoreconnect

[HOST]
Internet support (Proxy Encrypted Repeater Connection)
-connect uvnc.com:5500 -id 543 -proxy

[TEXTTOP]
TextTop

[TEXTMIDDLE]
TextMiddle

[TEXTBOTTOM]
TextBottom

[TEXTRBOTTOM]
TextRBottom

[TEXTRMIDDLE]
TextRmiddle

[TEXTRTOP]
TextRtop

[TEXTCONNECTBUTTON]
TextConnectbutton

[TEXTERROR]
Texterror

[TEXTBUTTON]
Textbutton

[WEBPAGE]
http://www.uvnc.com

[TEXTCLOSEBUTTON]
TextClosebutton

[BALLOON1TITLE]
Balloon1title

[BALLOON1A]
balloon1A

[BALLOON1B]
balloon1B

[BALLOON2TITLE]
Balloon2title

[BALLOON2A]
ballon2a

[BALLOON2B]
balloon2b

> Most of the entries speak for themselves and are represented on the picture above

> Other entries are explained below:

[TEXTERROR]
This is the message that is displayed when users press the [TEXTCONNECTBUTTON]
without selecting one of the [HOST] entry's.

[TEXTBUTTON] and [WEBPAGE]
When textbutton is defined, it allow you to define a web page.
Pressing the button open the web page.

[BALLOON1TITLE]
[BALLOON1A]
[BALLOON1B]
This are the messages that are shown when the server is making or waiting for a connection.
It shown at the position of TEXTTOP,TEXTMIDDLE and TEXTBOTTOM (see image)

[BALLOON2TITLE]
[BALLOON2A]
[BALLOON2B]
Same as for BALLOON1, but when connection is made.

Customizable Graphics

> logo.bmp: See the picture at the top of this page
> background.bmp: See the picture at the top of this page, the bmp is stretched over the full dialog window
> icon1.icon: This icon is shown in the systray and as the icon of the compressed (generated) exe.
> enter.bmp: See further, this is the graphic used with the special [ENTERCODE] directive.

Special values

[DIRECT]
When you have only one [HOST] entry, you can avoid that the user need to select the only [HOST].
Using [DIRECT] you skip the dialog.

[ENTERCODE]
Enter your ID

One [HOST] only, for a repeater connection. The -id number (-id 543) from the [HOST] line is ignored.
When you add entercode, the normal dialog is skipped, and a special enter ID dialog is displayed.

This allows the user to manually define an ID number

UltraVNC Viewer Commandline Parameters

-help, -? or -h
Print a help message.
-listen [port]
Start the VNCviewer in listen mode. If port is specified, the viewer listens on that port instead of 5900 default port.
example vncviewer listen non standard port 80
vncviewer.exe -listen 80
-dsmplugin filename.dsm
example1: vncviewer.exe host -dsmplugin msrc4plugin.dsm
example2: vncviewer.exe host -dsmplugin securevncplugin.dsm

-proxy host:port
the proxy is not your office proxy, is ultravnc repeater proxy.

the proxy/repeater mode I (distributor) repeater must be on your lan
"%:\programfiles%\UltraVNC\vncviewer.exe" -proxy host:5901 -connect hostname
"%programfiles%\UltraVNC\vncviewer.exe" -proxy distributor:5901 -connect host -dsmplugin filename.dsm

proxy/repeater mode II (with ID number)
"%:\programfiles%\UltraVNC\vncviewer.exe" -proxy host:5901 ID:1234
"%programfiles%\UltraVNC\vncviewer.exe" -proxy host:5901 ID:1234 -dsmplugin filename.dsm"

-autoacceptincoming
Auto  Accept Incoming connection (no SC server info)
-autoacceptnodsm
server connection set without encryption, there no message is NOT encrypted while vncviewer listen with dsmplugin
-autoreconnect [DelayInSeconds]
-autoreconnect (default value 3 seconds)
example: autoreconnect after 15 seconds
vncviewer.exe -autoreconnect 15 -connect hostname
commandline autoreconnect
default=3
value is number of seconds between reconnects This allow to set a bigger timeout between reconnect intervals this function is blocked by repeater for viewer."
%programfiles%\ultravnc\vncviewer.exe" -autoreconnect 30 -connect hostname::5900 -quickoption 3 -dsmplugin SecureVNCPlugin.dsm
-reconnect x (warning) not yet available by command line) only gui
This is the number of times a reconnect is made before the viewer
close the connection.
-disablesponsor
remove the sponsor of vncviewer message error
-fttimeout sec
Filetransfer timeout sec [1-60]
-keepalive sec
Interval to send a keepalive message
-askexit
Open a dialogbox on exit " do you realy want to quit"
-restricted
remove options from system menu ( Filetransfer, chat ....)
-viewonly
Do not send local keyboard or mouse events to the remote computer.
-nostatus
Don't show the status window while connecting.
-nohotkeys
Do not enable hot keys (like CTRL+ALT+F9 for full screen mode etc.). Can be useful in case of conflict with other installed software hotkeys.
-notoolbar
Do not display the toolbar.
-autoscaling
Automatically scale the viewer window so that the remote screen fits at best your local screen size.
-fullscreen
Display viewer in full screen mode.
-noauto
Disable auto mode. Required for using the color options below or saving a custom configuration (otherwise the settings from quick options always override).
-8bit, -256colors, -64colors, -8colors, -8greycolors, -4greycolors, -2greycolors
Set the color depth. Fewer colors can significantly reduce the required bandwidth.
Note: Grey colors only work with 32 bits color screen resolution. 16 or 24 bits color resolutions just don't work with grey colors.
-shared
Share the server with other viewers, i.e. allow several viewers to connect simultaneously to the server.
-swapmouse
Swap left and right button of the mouse.
-nocursor
Do not display any local dot mouse cursor.
-dotcursor
Display the local dot mouse cursor.
-normalcursor
Display the normal local mouse cursor.
-belldeiconify
not used
-emulate3
Emulate a 3-button mouse.
-noemulate3
Do not emulate a 3-button mouse.
-nocursorshape
don't change cursor chapes
-noremotecursor
"." is used as remote cursor
-scale A/B
Scale the display by the factor A/B.
-emulate3timeout Timeout
emulate 3 button mouse with 2 buttons
-emulate3fuzz Emul3Fuzz
emulate 3 button mouse with 2 buttons
-disableclipboard
Do not transfer clipboard content.
-delay delay
debug option
-loglevel loglevel
Set the loglevel. This can range from 0 (minimal) to 10 (maximum logging).
-console
Open a console window for log output.
-logfile filename
Log to the file specified by filename.
-config filename
Read the configuration from filename.
-register
Record the path to the VNC viewer and the type of the .vnc files in the registry
-encoding encoding
Encoding is either raw, rre, corre, hextile, zlib, zlibhex, tight or ultra. Encodings are described here.
-compresslevel level
Use specified compression level (0..9) for "tight" and "zlib" encodings (Tight encoding specific). Level 1 uses minimum of CPU time and achieves weak compression ratios, while level 9 offers best compression but is slow in terms of CPU time consumption on the server side. Use high levels with very slow network connections, and low levels when working over high-speed LANs. It's not recommended to use compression level 0, reasonable choices start from the level 1.
-quality quality
Use the specified JPEG quality (0..9) for the "tight" encoding (Tight encoding specific). Quality level 0 denotes bad image quality but very impressive compression ratios, while level 9 offers very good image quality at lower compression ratios. Note that the "tight" encoder uses JPEG to encode only those screen areas that look suitable for lossy compression, so quality level 0 does not always mean unacceptable image quality.
-user msuser
ms logon (NTLM1) username set at server (not viewer side)

-password password
Use the specified password for "classic" VNC authentication.
-serverscale scale
Scale the display on the server side by 1/scale. For instance scale = 2 means that the remote screen dimensions are reduced by 2 ("half screen size"), reducing at the same time the amount of graphical data received by a factor 4 (2^2).
-quickoption n
Select a quickoption. Modem option is default
1 = AUTO (auto select best settings, this never use ultra experimental maybe "forever")
2 = LAN (> 1Mbit/s) Max Colors
3 = MEDIUM (> 128Kbit/s )- 256 Colors
4 = MODEM (19K - 128Kbit/s) - 64 Colors
5 = SLOW (< 19Kbit/s) 8 Colors
6 = (custom ?) N/A (not available and fail)
7 = ULTRA (> 2Mbit/s) - Experimental (still experimental after 2 years)

REMARK
Commandline options are Merged with the default saved settings.
Sample:
if you save viewonly as default -> a viewer started with a commandline option will always be "viewonly".

Installation

Mirror driver only get downloaded, NOT installed.  This need to be done manual.

For first time install you best don't register it as service, this can always be done later from the
winvnc systray.  First test if it works, and then register as service when needed.

Automate Installation

 If you need to install UltraVNC on a large number of computers, you might consider automating the installation.
The following command line parameters can be passed to the setup:
/dir="Dirname"
Sets installation directory to Dirname.
/no restart
Suppresses a reboot at the end of the installation.
Not required since the installation no longer requires are boot.
/silent or /very silent
Suppresses either pop-up of dialog boxes or any GUI at all.
/loadinf="Filename"
Loads the configuration file Filenamefor the installation.
This configuration file can be generated by going through setup with UltraVNC-xxxx-Setup.exe /saveinf="Filename".
Filename should be fully qualified.
/log
Writes a log file to the Temp directory.
Could be used for debugging.

Translated from
http://www.marcozanon.com/documenti/assistenza-remota-multipiattaforma-open-source

Remote Assistance multiplatform open source
Introduction

In this white paper we see how you can configure an entire system of remote support platform exclusively with open source tools. For convenience are taken into account only the operating systems Windows and Linux, but with small changes you can adapt the instructions to other platforms (Mac OS, Solaris, BSD, etc.)..

The ultimate goal is to make sure that a client (server) by running a simple connection software (called single-click because it should not present major difficulties) can put in a technical condition (viewer) to provide assistance even if both are in private networks are not publicly accessible and can not open specific ports on the respective firewall (for limits imposed by the system administrator, for scarce capacity of the remote customer or simply for convenience).

Of course, that is only one of the proposed solutions, which are mainly due to a lot of different techniques and existing security implementations sometimes "custom" of the RFB protocol at the base of all VNC.

Configuring the Repeater

One of the first components we are going to configure is the so-called repeater. This is a software that can be connected to the server and the viewer when they are in a private network so that each of the two parties make a connection only "exit" from its network and is (hopefully) blocked by the firewall.
Of course, because of its role, the repeater must be reachable from the public network. Can then for example be conveniently installed on a VPS.

I chose to entrust to ultravnc_repeater.pl, excellent Perl script by Karl J. Runge allowing us to use a Linux server and still be able to connect in either simple encrypted.
More precisely, I derived a custom version called mz_ultravnc_repeater we are going to download from my SVN repository and the original adds the ability to filter the server and viewer based on certain connection ID.

First type:

$. / Mz_ultravnc_repeater.pl-h

for a complete list of options and explanations.

To run just type the command:

$. / Mz_ultravnc_repeater.pl-r-i-i ID_CONNESSIONE_1 ID_CONNESSIONE_2 ID_CONNESSIONE_3-i-l LOGFILE PORTA_VIEWER PORTA_SERVER

that launches the software and accepting connections from certain ID PORTA_VIEWER (which connects the technician) and PORTA_SERVER (which connects the customer), refusing, however, consecutive two connections with the same ID (not to disconnect a previous server) and logging in the 'activity LOGFILE.

For example, a configuration that provides for the use by 3 technicians (ID respectively 1000, 1001 and 1002) could be the following:

$. / Mz_ultravnc_repeater.pl-r-s 1000-s 1001-s 1002-l / var / log / mz_ultravnc_repeater.log 5901 5501

It goes without saying that you must open the corresponding ports on the firewall of the network that hosts the repeater.

To avoid unpleasant surprises in the event of some flaw in the repeater, or simply to not allow the use of the same by third parties not customers, recommend the following safety measures.

• Do not run the repeater as root, since it is not necessary to do so.
• Better yet, run it only when it is needed (ie, when a customer calls asking for assistance) and with the-i and-r to assign specific channels Connection ID and immediately take them to a server session-viewer. The script also includes the ability to be run as a CGI (so for example on the web), but in this case I recommend that you read the instructions carefully because there may be potential security risks.
• Always use the log file, which of course must be configured to allow writing even non-root user that runs the repeater.
It is not particularly useful for filtering MAC address connections viewer, given that the repeater would read address as the router from which the technician connects and not that of his specific computer.
Even configure the repeater to accept connections on non-standard ports (which by default are 5900 and 5500) is a guarantee of safety, and that is because you could easily "peek" in the connection software to read these parameters. However, it can be a help to prevent attacks by automated software, and therefore it is advisable to go this route.

Configuring the Windows server

For Windows the choice "forced" to the server is UltraVNC version Single-Click (SC), a special service that allows you to upload a file on the appropriate creator online and get the program version already compiled.
Theoretically it is all documented on the website, which, however, is very confusing and often contradictory information presented or exceeded.

Let us go to the page containing the documentation, download and unpack the file basis custom.zip and look at the rest of the information on the page to understand what kind of customizations we need.

Then we set the file helpdesk.txt in a manner similar to the following:

[TITLE]
Remote Assistance

[HOST]
Simple connection (double-click)
Id-12345678-connect IP_DEL_REPEATER: PORTA_SERVER-noregistry

[TEXTTOP]
Warn phone before connecting.

[TEXTMIDDLE]
The service 'available exclusively

[TEXTBOTTOM]
for customers with special contract.

[TEXTRTOP]
__NOME_AZIENDA__

[TEXTRMIDDLE]
__EMAIL_AZIENDA__

[TEXTRBOTTOM]
__TEL_AZIENDA__

[TEXTBUTTON]
Website

[WEBPAGE]
__SITO_WEB_AZIENDA__

[TEXTCLOSEBUTTON]
Close

[BALLOON1TITLE]
Connection in progress

[BALLOON1A]
Please wait a moment ...

[BALLOON2TITLE]
Connection is active

[BALLOON2A]
Your desktop may 'now be viewed and controlled by the Advisor.

[BALLOON2B]
And 'possible to disconnect the connection at any time by right-clicking and selecting "Close".

Clearly the connection string and the messages must be configured as desired, as well as icons, the logo and the background image in the file custom.zip original.

At the end ricompattiamo all in a file NomeDiNostroGradimento.zip, carichiamolo online and wait a few seconds. The resulting file is NomeDiNostroGradimento.exe our server to Windows clients.

When compiling the content of helpdesk.txt be given to the following.

• Do not use accented or non-ASCII characters.
• It is possible for a bug in the compiler, the TITLE section is in fact irrelevant because in the end the program window does not appear no title (not bad).
• It is essential that, in the HOST, the option-id is put before-connect, otherwise the ID is not passed to the connection.
• In testing can be useful to add to the foot of the directive file (it is not even a section) DEBUG to follow step-by-step evolution of the connection.
The steps allow to obtain an executable that opens a connection simple.
If you want to add an encrypted connection, you need to add another section HOST:

[HOST]

Encrypted connection (double-click)
-Plugin-id 12345678-connect IP_DEL_REPEATER: PORTA_SERVER-noregistry

The option-plugin, to be at the beginning of the string, is to use the plug-in encryption. UltraVNC-SC officially supports a plugin called MSRC4Plugin.dsm very weak and flawed, so you should instead download SecureVNCPlugin that works perfectly as long as you rename MSRC4Plugin.dsm.
Inglobiamo that file in our package and NomeDiNostroGradimento.zip ricarichiamolo online to get the upgraded server.

Please note that as you will be able to say later, this specific connection currently works only with the UltraVNC client (ie Windows only, or emulation under Linux via Wine) version 1.0.9.6.2 or higher. We must also use the same client-side plugin SecureVNCPlugin.

If the encrypted connection does not work, try reconfiguring UltraVNC-SC using precisely that SecureVNCPlugin file as distributed together with UltraVNC version 1.0.9.6.2 or higher (rather than downloaded from the official website), of course, always renaming MSRC4Plugin.dsm.

Configuring the Linux server

For Linux there is a similar solution to UltraVNC-SC. So, inspired by an article in the Linux Journal and studying the excellent x11vnc, I made a tool to configure and create a script called autorun single_click_remote_help, which can be downloaded from my SVN repository.

To configure simply open the file and change the skeleton section 1 (constant) with strings of messages and connections you want, the symbol "|" splits the label parameters to be passed to x11vnc server to the list of which refer to the specific page.

For example, to obtain a simple connection and an encrypted we will use:

CONNECTIONS [0] = "encrypted connection (double-click) |-connect_or_exit repeater :/ / IP_DEL_REPEATER: PORTA_SERVER + ID: ID_TECNICO-ssl TMP-env X11VNC_DISABLE_SSL_CLIENT_MODE = 1-SSLOnly"
CONNECTIONS [1] = "Simple connection (double-click) |-connect_or_exit repeater :/ / IP_DEL_REPEATER: PORTA_SERVER + ID: ID_TECNICO"

The syntax repeater :/ / IP: PORT + ID: NNNNNNNN allows precisely to make connections through a repeater and pass a specific ID.

Then simply run:

$. / Build.sh

to obtain the server (single_click_remote_help.sh).

You can now load the server on its website, warning the user before execution must necessarily to manually assign attribute executability downloaded the script (Linux, thankfully, does not allow to directly execute any file downloaded from the network ).

Is currently only supported version for i686 processors and above, in addition, since the script uses zenity or (in the absence) of kdialog, you need these tools installed. In fact, however, most of the distributions should have no trouble to run the software.

Configuring the Windows viewer

In the Windows environment should rely on UltraVNC (full version, not SC of course) as generic viewer, as it allows to connect to any standard VNC server and UltraVNC-SC (which instead uses a protocol RFB modified and therefore not standard).

Please note that this plugin SecureVNCPlugin.dsm executable UltraVNC-SC must be present in the same directory as the UltraVNC viewer.

The connection parameters are ID: ID_TECNICO as Host: Port and IP_DEL_REPEATER: PORTA_VIEWER as Proxy / Repeater, possibly by activating and selecting Use DSMPlugin SecureVNCPlugin.dsm.

The only problem is the connection to the Linux server single_click_remote_help encrypted. Only for this type of connections and unload SSVNC use of Karl J. Runge, which, unfortunately, although very valid can not be used as a "viewer unique" because the Windows version (unlike that Linux) does not connect well to UltraVNC server-SC.

In this case, the connection parameters are: 0 for VNC Host: Display, repeater :/ / IP_DEL_REPEATER: PORTA_VIEWER + ID: ID_TECNICO as Proxy / Gateway, such as Use SSL encryption, Verify All Certs disabled and Do not Probe for VeNCrypt enabled.

Configuring the Linux viewer

On Linux, the situation is reversed from Windows. Should download (but it may already exist in your distribution) SSVNC the already named, which is a wrapper of TightVNC but with customizations of the latter and encryption tools that extend far use possible is made of a kind of "Swiss boxcutter" VNC connections, albeit with an (intentionally) spartan.

With SSVNC we connect to any server except to UltraVNC-SC in encrypted version, to be honest, in the latest versions is also provided for this possibility, but right now I am not quite working. For now, then, only in these cases fall back on UltraVNC launched in emulation through Wine.

For the connection parameters of both viewer reuse information already studied in the previous paragraph, of course with the appropriate setting on the type of encryption used (none, SSL, SecureVNCPlugin) and leaving the option VeNCrypt Server uses SSL encryption disabled.

Summary table of server connections-viewer

In light of the above, can be summarized in a report which the viewer, depending on the type of connection and the server operating system, it is advisable to use.

Viewer Viewer Windows Linux
Windows Server, simple connection: UltraVNC UltraVNC SC-SSVNC
Windows server, encrypted connection: UltraVNC UltraVNC-SC SecureVNCPlugin + + + SecureVNCPlugin SSVNC SecureVNCPlugin, or (via Wine) UltraVNC + SecureVNCPlugin
Linux servers, simple connection: single_click_remote_help UltraVNC SSVNC
Linux servers, encrypted connection: single_click_remote_help SSVNC SSVNC

Alternative and Future Prospects

Practical alternatives (we omit the experimental projects) for the choice of the repeater now seem to be the following:

• UltraVNC Repeater: UltraVNC part of the project, is a good solution but it requires a Windows server;
• UltraVNC Repeater SSL variant of the first that supports only a particular mode SCIII (which also means the reconfiguration of server and viewer), this requires a Windows server;
• vncssld: written in Perl, is analogous to the previous Unix systems.
A little help could arrive from the accommodation of some bugs in SSVNC (and TightVNC) in such a way that it can be exploited as the "viewer only" under Windows and Linux, regardless of the server used and also in the presence of encrypted connections.

More generally, as regards the choice of the server and the viewer, in my view, a project that deserves to be kept an eye on is TigerVNC (evolution of TightVNC), in a single product that provides easy interface (minimal) and encryption integrated, in addition to being cross-platform: in fact, all that is needed to provide remote support.
Its drawback is that currently does not support any repeater, which does not make it integrated with the solution described above (and here's the reason why I have not considered in this document). However, a flaw that I expect to be exceeded in future releases.

Last note, perhaps paranoid. The security of the connections can be further improved by the generation of keys signed, so as to avoid man-in-the-middle attack. However, since this path more complicated and less flexible than the one provided, I confined myself to illustrate some configurations, standard interventions for remote support, I think it is reasonably safe.

Usage repeater

UltraVNC Repeater is an UltraVNC addon
There are two modes available with the UltraVNC repeater: mode I and mode II
While mode I is used for UltraVNC Server and Viewer both in normal mode, mode II works with the server in listening mode.

UltraVNC Repeater Mode I

How does it work

Usage

Viewer can be behind Nat router or directly connected to the internet.
Instead of forwarding several ports, you only need to forward 1 port
If the PC that runs the Repeater has access to the local DNS server, you can use your local DNS names instead of 10.10.10.12.
This could be handy when you have a dynamic DHCP server allocating ip addresses for your PC.
To connect the the server running on 10.10.10.11 Port 5900

To connect to the server running on 10.10.10.12 Port 5902

Repeater settings

Extra options boxes

Enable mode I / Enable mode II

Here you decide if you want to run the repeater in mode I, mode II or if you enable both modes simultaneously.

Restrict access to port

If you run all the vncserver on the same port
10.10.10.11:5900
10.10.10.12:5900
You can replace the 0 in this field by 5900.
The repeater is the restricted to connections with ports 5900

Allow connection to server

If you activate this option (v), the repeater can only connect to the specified ip addresses.
10.10.10.12;10.10.10.13 -> you can only connect to 12 and 13
10.10.10. -> you can connect to all 10.10.10.X, this way you can block access to any other Subnet (10.10.11.X)

Refuse connection to server

If activated you can tell with server you cannot access
10.10.10.15 -> you can connect to all except 15

Syntax for allow/refuse

A.B.C.D
A.B.C.
separator ";"
Address allow/refuse have to be ip addresses. You cannot use DNS names in those fields.

UltraVNC Repeater Mode II

In mode II both server and viewer initiate an outgoing connection.
Viewer (normal mode)
Server (invers connection)
Repeater have to run on a machine that can be accessed from server and viewer PC.
Open on the internet (DMZ zone)
Internal, but with 2 ports forward by the Nat router
Situation is indicated by the lower image of the repeater settings window.

Server settings

Viewer settings

Repeater settings

Repeater logging

In real life, replace localhost by the ip_address of the server running the Repeater
For localhost test, remember to select allow loopback in WinVNC Server properties

Accept = port the viewer connect
Listen = port server connect (outgoing connection)
Restricts Ports: need to be 0;
Allow and deny: leave unchecked, can not be used in mode II

BSD License

UltraVNC repeater is released under the following license:

Copyright (C) 2005 UltraVNC Team Members. All Rights Reserved.Redistribution and use in source and binary forms,
with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
Neither the name of the UltraVNC nor the names of its contributors
may be used to endorse or promote products derived from this software
without specific prior written permission.

License

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

UltraVnc Viewer Usage

There are a lot of options that can be configuredfrom the viewer side.

Quick options

The quick options relate to the following configurationsettings:

Auto

LAN

Medium

Modem

Slow

Ultra

View Only
No keyboard or mouse events are sent from the viewer to theserver. The server screen can only be viewed, but notcontrolled.
Auto scaling
The viewer window is automatically scaled to fit the size ofyour local screen.
Use DSM Plugin
Choose a DSM (Data Stream Modification) Plugin and configureit.
To use an encryption plugin, for instance, check this option andselect the plugin in the combo box. The plugin file must be inthe same directory than the vncviewer.exe program. And of course,the same plugin must
be used by the UltraVNC server you connectto.
Proxy/Repeater
Specify the repeateraddress here.
Save connection settings as default
If checked, the current settings are saved as default optionsin a configuration file. So next time you run the viewer, youdon't have to reselect all your favorite settings.
Further viewer configuration can be done when pressing theOptions button.

Format and Encoding

See Encodings section below.
Note: Grey colors only works with 32 bits color screenresolution. 16/24 bits color resolutions just don't work withgrey colors.
Mouse buttons
Mouse cursor
Display
Miscellaneous

[0] number of time the reconnect is attempted
0 (default), never reconnect
9 (maximum) 9 time trying reconnect.
gui reconnectnumber only for now.
This is the number of times a reconnect is made before the viewer close the connection.

Encodings

This section (except Ultra encoding) is taken fromTightVNC'svncviewer man page.

The server supplies information in whatever format is desiredby the client, in order to make the client as easy as possible toimplement. If the client represents itself as able to usemultiple formats, the server will choose one.

Pixel format refers to the representation of anindividual pixel. The most common formats are 24 and 16 bit"true-color" values, and 8-bit "color map" representations, wherean arbitrary map converts the color number to RGB values.

Encoding refers to how a rectangle of pixels are sent(all pixel information in VNC is sent as rectangles). Allrectangles come with a header giving the location and size of therectangle and an encoding type used by the data which follows.These types are listed below.

Raw

The raw encoding simply sends width*height pixel values. Allclients are required to support this encoding type. Raw is alsothe fastest when the server and viewer are on the same machine,as the connection speed is essentially infinite and raw encodingminimizes processing time.

CopyRect

The Copy Rectangle encoding is efficient when something isbeing moved; the only data sent is the location of a rectanglefrom which data should be copied to the current location.Copyrect could also be used to efficiently transmit a repeatedpattern.

RRE

The Rise-and-Run-length-Encoding is basically a 2D version ofrun-length encoding (RLE). In this encoding, a sequence ofidentical pixels are compressed to a single value and repeatcount. In VNC, this is implemented with a background color, andthen specifications of an arbitrary number of sub rectangles andcolor for each. This is an efficient encoding for large blocks ofconstant color.

CoRRE

This is a minor variation on RRE, using a maximum of 255x255pixel rectangles. This allows for single-byte values to be used,reducing packet size. This is in general more efficient, becausethe savings from sending 1-byte values generally outweighs thelosses from the (relatively rare) cases where very large regionsare painted the same color.

Hextile

Here, rectangles are split up in to 16x16 tiles, which aresent in a predetermined order. The data within the tiles is senteither raw or as a variant on RRE. Hextile encoding is usuallythe best choice for using in high-speed network environments(e.g. Ethernet local-area networks).

Zlib

Zlib is a very simple encoding that uses zlib library tocompress raw pixel data. This encoding achieves good compression,but consumes a lot of CPU time. Support for this encoding isprovided for compatibility with VNC servers that might notunderstand Tight encoding which is more efficient than Zlib innearly all real-life situations.

Tight

Like Zlib encoding, Tight encoding uses zlib library tocompress the pixel data, but it pre-processes data to maximizecompression ratios, and to minimize CPU usage on compression.Also, JPEG compression may be used to encode color-rich screenareas (see the description of -quality and -nojpeg optionsabove). Tight encoding is usually the best choice forlow-bandwidth network environments (e.g. slow modemconnections).

Ultra

Experimental, Ultra encoding provides real time performanceover a LAN by utilizing LZO compression. LZO is a datacompression scheme which is suitable for data de-/compression inreal-time. This means it favors speed over compressionratio.

VNCViewer Toolbar

• Send CTRL+ALT+DEL

• Toggle Full Screen Mode

• Show Connection Options...

• Refresh Screen

• Send 'Start' (CTRL+ESC) to host

• Send Custom Key

• Show Status Window

• Close Connection

• Hide Toolbar Buttons

• Toggle Remote Input and Remote Blank Monitor

• Open File Transfer...

• Select Single Window

• Select Full Desktop

• Open Chat...

VNCViewer Context Menu

File Transfer... (Hotkey CTRL+ALT+F7)

Open the file transfer dialog window.

Chat... (Hotkey CTRL+ALT+F8)

Open the chat dialog window.

Show/Hide Toolbar (Hotkey CTRL+ALT+F9)

Show or hide the VNCViewer toolbar.

Disable/Enable Remote Input and Monitor

Disable keyboard and mouse input as well as the monitor onthe remote computer.

Connection options... (Hotkey CTRL+ALT+F6)

Open the connection option dialog window.

Connection info

Open the connection info window.

Request screen refresh

Redraw the screen in VNCViewer. Sometimes the display inVNCViewer misses updates or becomes corrupted. A screen refreshcan then insure that VNCViewer's display and remote computer'sdisplay are in sync.

View only

Disables sending mouse and keyboard events from the VNCViewerto the remote computer.

Various screen size options

Full screen mode (hotkey CTRL+ALT+F12) displays theremote screen on the entire screen of your display.
Together with a hidden toolbar this feels like sitting in frontof the remote computer.
Scaled viewer mode displays the scaled remote screen in a windowwith a user defined size.
Scaled server mode generates less network traffic from serverside and uses a pixel blending algorithm to optimize thedisplay.
Fuzzy screen mode combines Server and Viewer scaling to providereasonable visual comfort and speed even over very slowconnections.
Auto scaling mode scales the view to fit the viewer screen.Normal screen mode (hotkey CTRL+F11) displays theremote screen 1:1.

Full/256 Colors

Change the color depth of the screen.

Send various key combinations

Send CTRL+ALT+DEL (hotkeyCTRL+ALT+F4), CTRL+ESC (this opens thestart menu), CTRL+Key Down, CTRL+KeyUp,
ALT+Key Down or ALT+Key Up.

New connection...

Start a new connection.

Save connection info as... (HotkeyCTRL+ALT+F5)

Save the options and settings of the active connection in afile.

About VNC Viewer...

See version and licensing information of VNCViewer.

Additional Hotkeys

Pressing ALT or CTRL send ALT/CTRL directly to the VNCServer,as if the user selected "CTRL DOWN/CTRL UP/ALT DOWN/ALT UP" fromthe system menu.

When SCROLL-LOCK is activated, all keycombinations (except CTRL+ALT+DEL) are directly sentto the remote computer:

• Instead of switching applications on the client side,ALT+TAB is sent to the VNCServer.

• Instead of opening the start menu on the client side,CTRL+ESC is sent to the VNCServer.

• Instead of opening the system menu on the client side,ALT+SPACE is sent to the VNCServer.

• Pressing Break/Pause key toggles Full-Screenmode on or off.

• Pressing PRINT-Screen key requests a full screenupdate (same as selecting "Request Screen Refresh" from thesystem menu)

All the above can be disabled by turning theSCROLL-LOCK key off.

By Bryan Keadle (bkeadle@keadle.net)
2/12/2005

Using the VNC Repeater:
The VNC Repeater enables you to open up a single port on your firewall to the VNC Repeater machine (kind of a "gateway" or "proxy"), and use the VNC Viewer to remote control any local machines running the WinVNC Server. To follow are the instructions for this setup.

Download UltraVNC: http://uvnc.com
This "distribution" of the Open Source VNC project includes additional features including other compression algorithms for speed and flexibility, file transfer, chat, and MS Logon authentication, to name a few.

Install the VNC Server on a machine to be remote controlled
(WinVNC Server machine):

Select the necessary properties of WinVNC repeater

Setup VNC Repeater machine:

ON REMOTE MACHINE:

VNCViewer
Now run VNCViewer.exe:

Enter the local IP address (or DNS name) of the machine you want to control

Check on the Proxy Repeater check box, and enter the public address assigned to your VNC
Repeater (or router from which you are forwarding port 5901)

Press the Options... button to specify your connection options. I've found the best remote control
settings to be checking on the Use 8-bit color and specify Hextile encoding method.

VNC through SSH

SSH Server
You will need to provide an SSH Server. This can be a Linux machine, or a Windows machine running OpenSSH (http://sshwindows.sourceforge.net/). Configure your router to forward port 22 (SSH) to your "SSH Server".

SSH Client
Copy (or otherwise provide) vncviewer.exe and an SSH client (Putty.exe - http://www.chiark.greenend.org.uk/%7Esgtatham/putty/ ) to the client to be used to
remote control your WinVNC Server machine.

Configure PuTTY:

Setup a session to forward port 5900 to the machine you want to remote control (using it's local address (or DNS name), in this case:172.16.0.101).
Your SSH Server machine will need to be able to resolve this address/name.

Enter the host name and port (22). You can pass the username by preceding the host name with Username@ as indicated in the above graphic.
Enter a name in the Saved Sessions edit box, then press the Save button.

Select the OPEN button to connect to your SSH Server. You will need to authenticate to the SSH server to establish the SSH tunnel.

With this SSH tunnel established, you will now use VNCViewer to connect to the machine you configured PuTTY for (172.16.0.101)
In the VNC Server: edit box, enter localhost (127.0.0.1).
You will want to select the Options button and select your Format and Encoding settings as described in the graphic.
When you press the Connect button, it will route 5900 local port through the SSH tunnel to the 172.16.0.101 address (according to the PuTTY configuration).

Likewise you could configure Windows XP Remote Desktop (Terminal Services) through SSH in the same manner. To include Remote Desktop, add an SSH tunnel like this:

This configuration would give you both VNC and Remote Desktop (Terminal Services) access to 172.16.0.101 through the SSH tunnel.
Note, the Source port is defined as 127.0.0.2:3389.
This is a bit "different". When you open MSTSC.EXE (the Terminal Services client), you would enter 127.0.0.2 as the connection:
This will connect you to the Terminal Services server of the host machine through an SSH tunnel.

VNC Repeater and SSH Tunnel
Now, let's combine the VNC Repeater and the SSH Tunnel so that we are able to use the VNC Repeater through a secure SSH Tunnel.
Simply change / add the following
SSH tunnel parameters:

NOTE: the source port is 5900, and the destination port is 5901

In the VNC Viewer, connect using these settings:

NOTE: the Proxy/Repeater setting is localhost

PCHelpware Introduction

Download PCHelpware components (in Zip file format)

PCHelpware is basically made of three parts:
+A Viewer that is used to remote control a distant PC
+A Server that runs on the distant PC
+An optional Repeater that helps the Viewer and the Server to connect together. It is actually a mediation-proxy service.
Viewer and Server can be customized to fit your needs (see Part 3, Part 4 and Customization pages)
PcHelpware has two main connectivity schemes:
+Direct connection(can be used when only the server PC is behind a NAT router or simply not directly reachable)Server -> Viewer
+Connection through a repeater (can be used when both Viewer and Server PCs are behind their own NAT router)Server -> Repeater <- Viewer
Notes:
- PC standing behind a NAT means that this PC can't be easily reached from outside (from the Internet)
- You must run the Viewer on your machine. The individual you want to help must run the Server on his machine. Even if this machine is behind a NAT the connection can be done because this connection is initiated by the Server from behind the NAT router to the Viewer over the internet.
See Part 2 for more details on connection modes and settings.

PCHelpware Zip file contents

> Folders

- Connections:
This folder is used the save Viewer profiles
- Create_server:
This folder contain the needed files to generate the customized server exe
- Drivers:
If you wish to speedup your connections, you can install special Mirror Drivers under Windows 2000, XP and Vista.
- My Servers:
In this folder you find the generated servers. The servers are saved in a sub folder with the same name then the Viewer profile
- Repeater:
This folder contains the Repeater. An instance is most time running on the uvnc.com server
- Server_res:
Contain the background and icon of the server exe. Can be customized. 

PcHelpware_viewer.exe

This is the profile name used to save the viewer A "Direct Connection" is a connection between server and viewer, "Via Repeater" uses the repeater as a proxy List of saved viewer profiles.

Connection modes

Direct connection between Server and Viewer (Viewer <- Server)

Server PC connects to the public host name or ip address of the Viewer PC

(1) and (4) are the only options you have to enter to create a direct connection

To make direct connection to the viewer easier, the server can use the Repeater Dynalias functionality
The repeater dynalias is an easy way of handling connections to viewers that have a dynamic ip address. On viewer start, the ip address is sent to the repeater service, the same service is used by the server to ask the ip address of the name (7).

Indirect connection through a Repeater (Server -> Repeater <- Viewer)

Necessary when both the Server and Viewer stand behind NAT routers (typical NAT-to-NAT scheme)

 

---

Server

Executable creation

> For each Viewer profile you create you have to create the corresponding Server package that will be able to connect the this listening Viewer

> Once you have made the Viewer configuration/profile you can create the corresponding server by selecting the top menu or pressing the button (14)

> In case you selected the repeater option, you also need to enter the port used by the repeater to listen for new server connections (15)

> The Viewer profiles save the password (encrypted) and the server contains a MD5 hash of this password

> At this stage you have to make two choices:
- Force the user (on server side) to enter the password when he runs the server or make the server automatically use its embedded password hash.
- Force the user to enter the ID or Dynalias or make the server use its embedded ID and Dynalias

Summary view of Server executable creation

(1) Alias, use for saving profiles
(2) Switch: direct, repeater
(3) List of existing profiles
(4) Port used by the viewer (listening port)
(5) UPnP
(6) General log window
(7) Dynalias name
(8) Host name repeater
(9) Port dynalias service repeater (5912)
(10) The test button allow to test the repeater (server/viewer/dynalias port)
(11) ID number between 1-9999 to identify this connection
(12) Repeater port use to listen to new viewer connections
(13) Use https proxy
(14) Create server
(15) Repeater port used to listen to server
(16) Password

Viewer usage

Profiles management

Starting the Viewer - Options

> (19) is used to start the viewer in the selected mode (direct, repeater).
> A running viewer can by stopped listening with (20).
> (21) quits the application
> The quality of the image can be selected with (22).
- High is full color high quality mix of jpeg and zlib
- Mid is mix of lower quality jpeg and zlib
- Low is 4bit gray scale image especially adapted to slow connections
Depending on the bandwidth some quality setting can be to slow
> Disable directX: On some PCs there is a problem to detect the correct directx behavior.
This option allows to manually cancel directX
> Auto Reconnect: Once the initial connection is finished, the viewer puts himself back in listen mode
or reconnects himself with the repeater. It is very useful in case of broken connection.

> Debug: internal use

Viewer toolbar functions

(1) Smaller viewer
(2) Bigger viewer
(3) Fullscreen on/off
(4) Force complete screen refresh
(5) Unlock Server input
(6) Show transparent layers (XP)
(7) Open Chat window
(8) Use ctrl-at-c to sync clipboard
(9) Exit viewer
(10) Lock Server input
(11) Use ctr-c to sync clipboard (all data is synced)

The Mirror Driver SDK contain more info and samples about mirror driver usage.
More info SDK

How does it Work?

The Mirror Video Driver is a driver that UltraVNC (for instance) can use to be quickly and efficiently notified with screen changes. Using it on an UltraVNC server results in a excellent accuracy. The video driver also makes a direct link between the video driver frammebuffer memory and UltraWinVNC server. Using the framebuffer directly eliminates the use of the CPU for intensive screen blitting, resulting in a big speed boost and very low CPU load.

Supported OS for mv2 mirror driver?

win 2000 
win 2003
win 2008
XP
Vista
Win 7

Installation

If you have a previous version installed, it is recommended to uninstall it first, by doing the following: setupdrv.exe uninstall
Installation is done by setupdrv.exe install
The program setupdrv.exe is located in the folder you've chosen during the driver installation.

Manual Uninstall

1. net stop vnccom (stop communication manager service) Driver mv2 doesn't use the vnccom , only needed with the old drivers
2. Under XP: Control Panel ⇒ System ⇒ Hardware ⇒ Device Manager ⇒ Display Adapters ⇒ Uninstall mirror driver.
   Under W2000: W2000 does not allow video drivers to be removed while running.
   Trick: Remove vncdrv.sys (that is in system32/drivers), and reboot. You now can remove the driver the same way as with XP, via the device manager.

Upgrading issue

For each version the vncdrv.sys and vnccom.sys are a pair. Vncdrv.sys is a kernel driver, so can only be unloaded on reboot. After upgrading the driver, vncdrv.sys is still the old version, but vnccom.sys is already the new one. Switching of vncdrv.sys is done on reboot. Don't use the driver before you reboot.