VNC command line

[Jonathan]

I am curious to all the command line options that VNC has.
i am aware of -password <password> which is very nice so i don't have to enter one in everytime i run VNC.

if i could get a list and what they do that'd be great.

[RobH]

from the vnc directory in dos type winvnc.exe help. should give you a box that shows all command lines.

I know that box will come up for sure if you type winvnc.exe and then a wrong command.

[ipsec]

you can also create a shortcut

with a -bogus

command after the run line.

Then it also gives you the options.. replace the -bogus with what it is you want

[Marscha]

See description of cmdline params in the online docs:
http://doc.ultravnc.net/install/cmdline.html
Hope this is complete.
Please let me know if something is missing.

[redge]

Marscha

-autoreconnect
???
Note that this "autoreconnect" param must be before the "connect" one on the command line!

my english is poor, but maybe you can find a good word than me to your "???" about -autoreconnect usage

Can the Connection Window stay Open on a Bad Connection
[topic=2644][/topic]

You are making a very good work and nice doc ...continue this way.

[Marscha]

Regde,

thanks for your encouraging words
The problem with -autoreconnect is not your English but me not knowing what autoconnect is doing exactly.
If anybody could explain it to me I'll add it to the docs

Martin

[mbrown]

It is my understanding that the -autoreconnect switch is used in conjunction with the -connect switch when having a server "back-connect" to a listening viewer. I use it with a batch file for my clients that are behind a firewall that is not under my control. The batch file looks something like this:

"c:\program files\ultravnc\winvnc" -autoreconnect -connect 12.34.56.78

On my computer I run the viewer in "listening" mode, and I have someone on the server end run the batch file. Anyway, the -autoreconnect will make the server end attempt to reconnect to my listening viewer if the connection drops or is closed. It will immediately reconnect to my listening viewer if I close the session. I must close my listening viewer altogether in order to stop the server end from "autoreconnecting" to my computer. The server attempts to "autoreconnect" for only a few seconds.

Hope this helps. If I am missing something, hopefully someone else will add to my description.

[Guest]

Hi, MBrown.

I work just like you, but when i close my listening viewer i'll be glad if the server can be closed too by security reasons...
I tried all the ways, including shutdown the server via task manager. Do you have a better solution?
Thanks!

[mbrown]

Guest,

If you are concerned about security when leaving the server running, then maybe the server package isn't the correct package for you. You may want to configure a single-click package which would be much cleaner on the "server" end.

But in the given scenario, if you want the server to stop running when you are done, then I don't think there is any other way to do it other than manually killing the server. If you have the server installed as a service, it may be a little cleaner to use a "net stop winvnc" command rather than killing the winvnc.exe process. Also, you could write a small batch file to stop the service or kill the process, which you would run when you are done on that server.

Michael

[Rob H]

Hi, MBrown.

I work just like you, but when i close my listening viewer i'll be glad if the server can be closed too by security reasons...
I tried all the ways, including shutdown the server via task manager. Do you have a better solution?
Thanks!

When you are in, right click on the server icon in the tray and select close.
It will close and knock you off.
You won't be able to reconnect but it will be closed.