use command line to control ultraVNC

[sharonch]

Hi,
My question is a very beginner level. It took me awhile.
I want to use command prompt to control the ultraVNC. for example, I want to use one command to give the server a password and initiate it. I did it in the Mac, but I have no idea how to do it in uVNC. I know this is not going to work, but what I have in mind is:

winvnc -pw:12345678 -run

any idea?

[B]

Google lists an older page at http://uvnc.net/install/cmdline.html

but the better documentation on winvnc.exe command line parameters is at http://www.uvnc.com/docs/uvnc-server.html

UltraVNC Server Commandline Parameters
winvnc [-sc_promt] [-sc_exit] [-id:????] [-autoreconnect[ ID:????]] [-connect host[:port]] [-connect host[::port]] [-run]

Parameters are order dependent !!

-connect host[:port]
-connect host <--- would connect to port 5500
if port < 1024 +5900 is added
Sample: host:1 -> port=5901,host:21 -> port=5921
-connect host[::port] ( 2 X : )
host::21 -> port=21
Special case: host[::port] =??? == request host and port

-autoreconnect
Is used in conjunction with the -connect switch when having a server "Reverse-connect" to a listening viewer.
You can use it in a batch file for your clients that are behind a firewall that is not under your control.
The batch file looks something like this:
"c:\program files\ultravnc\winvnc" -autoreconnect -connect 12.34.56.78
On the local computer run the viewer in "listening" mode, and have someone on the server end run the batch file.
The -autoreconnect will make the server end attempt to reconnect to the listening viewer if the connection drops or is closed.
It will immediately reconnect to the listening viewer if the session is closed.
Close the listening viewer altogether in order to stop the server end from "autoreconnecting" to your computer.
The server attempts to "autoreconnect" for only a few seconds.
Note that this "autoreconnect" param must be before the "connect" one on the command line!
-autoreconnect[ ID:????]
-id:????
The id is used when using a repeater. In that case the id
identify the server to the repeater. When id is used, the
host in "-connect host..." is the repeater.

example:
winvnc -sc_prompt -sc_exit -id:1234 -connect repeaterhost -run

-kill
Close winvnc running as service or started as application

-run
Need to be the last parameter, tell winvnc that no more
parameters are left

-sc_prompt
This option modify some behavioiur for Single Click usage.
*Pass server info to viewer and request viewer accept
(This use an unofficial rfb protocol, require ultravnc viewer)
-sc_exit
*Server quit when viewer disconnect
*Don't exit when desktop switch to UAC/winlogon

-settings
Internal used to be able to save to ultravnc.ini.
On >= Vista, the program folder is a protected folder and require elevated permission.
ultravnc.ini is first saved in a temp folder, then this file is red and data is copied
to the real ultravnc.ini in program files.

-securityeditor
Start the acl editor for mslogon II

SERVICE
-service
Internal switch used by uvnc_service to tell winvnc is started by a service
-service_run
Internal used for the special service_commandline option in ultravnc.ini.
-stopservice
Stop winvnc service
-startservice
Stop winvnc as application and restart winvnc as service
-install
Install the service, require admin (<=xp) or elevated access ( >=Vista)
-uninstall
Uninstall the service, require admin (<=xp) or elevated access ( >=Vista)
-uninstallhelper
-installhelper
-startservicehelper
-stopservicehelper
-securityeditorhelper
-settingshelper
Internal used by winvnc. The helpers are needed to simulate the current console user ( Service run as system). The start winvnc with the corresponding command line without "helper" with the "runas" option.
Sample winvnc (press install service) -->create process as current user
winvnc -installhelper
winvnc -installhelper -> start winvnc -install with (shellexec "runas" option)
-multi :
don't check if winvnc is already running

Notably missing from that expanded list is password control -- I think you still have to put that in an INI file.

[sharonch]

I agree. It is in the ini file. I also try to connect the server with the ini info, but the password in the ini is not the one to connect. I assume it is some kind of hash. Therefore, I even don't know how to test it or change it.

[B]

Correct. The simplest way is to configure the server manually (once) and set the password, and then copy the hashed INI line to as many remote servers as necessary.

Some people have tried to find or write scripts to generate the passwords more automatically, but I don't have a good link handy; you could search this forum. Please also be aware that SecureVNC (the "DSM plugin") is far more secure than standard VNC passwords, and it overrides the need for a standard VNC password (as do reverse / repeater connections).

[YY]

I also try to connect the server with the ini info, but the password in the ini is not the one to connect. I assume it is some kind of hash. Therefore, I even don't know how to test it or change it.

Reference these threads:

Encrypting Passwords

Generated password (vncpwd, vncpwdump) <> ultrawinvnc-passwd

[sharonch]

Correct. The simplest way is to configure the server manually (once) and set the password, and then copy the hashed INI line to as many remote servers as necessary.

Yes, I do have that idea in mind to setup the password manually first. But how? I have consider to use powershell to do so, but I don't know how to link the command prompt with the admin properties window. It is very different than Mac. maybe it is because I am too new to window scripting. I just want everything happen on the command line so that I can control things better.

[B]

Well, at a very simple level you could just create a batch file (.bat or .cmd) that issued a COPY command to copy the same INI file. Past that there are all kinds of scripting possibilities, including powershell. You don't have to "link to the admin properties window" -- everything in there has corresponding settings in the ultravnc.ini file.

[sharonch]

Hi B,
I think my problem is how to paste those password to the admin properties. I think I want to start with the very first step: I have already set up a UVNC server on Win7 and a chickoftheVNC(viewer) on a mac. How can I use the ini file to make the mac control the Win7? In another words, can I still use ini in the viewer and how?

[B]

Sorry I don't know how CoTVNC hashes, or how it stores, its passwords.

Apparently there's a fork called "Chicken" that uses the native OSX keychain...

http://sourceforge.net/projects/cotvnc/ ... ic/4597945

[sharonch]

I guess I make it too complicated. What if both of UVNC and viewer are on different Win7(I am avoiding loopback). Do you have any idea how to use ini file to make the viewer to control the server?