Advertise -connect option (imho easier to setup than SC)

[joachim]

Hi,
I'm using UltraVNC very much. Thanks a lot!
I also had the problem that configuring the router most of the time is not feasible for the person that needs support.
Hence SC seemed the way to go, but then it was a bit too complicated for me to create.

Finally I found out about the -connect option of the winvnc.exe. It is very easy to set up.
1. I prepare my router to forward incoming requests on port 5500 to my machine in my LAN. (usually only required once)
2. I launch the UltraVNC listening viewer on my machine.

3. I ask the remote person to launch the UltraVNC server normally.
4. I inform the remote person about my IP-address.
5. Then the remote person must launch winvnc.exe -connect and in the dialog type my IP-address.
-> My screen shows the remote desktop.

If my IP address is constant the remote person can create a shortcut to launch winvnc.exe -connect ip-address.

The only thing slightly inconvenient is that the remote user must first launch the server winvnc.exe before winvnc.exe -connect will work. My wish is that in future calling winvnc.exe -connect also starts the server if not yet running.

Otherwise I would recommend this to everyone for whom the SC solution is a bit too complicated.

Cheers,
Joachim

[B]

You know, at first my reaction was "oh, that's obvious, why is he posting", but.... there's a simple elegance to your suggestion!

In the past I've always had them install VNC and then use the right-click "Add New Client" from the system tray GUI, but I have to say, typing a command might be even easier.

(I assume you're also familiar with the various SC derivatives -- I like both SCPrompt and ChunkVNC.)

[YY]

The only thing slightly inconvenient is that the remote user must first launch the server winvnc.exe before winvnc.exe -connect will work. My wish is that in future calling winvnc.exe -connect also starts the server if not yet running.

This feature is available, you just need to add the option "-run" at the end of the command. That is:

Code: Select all

winvnc.exe -connect xx.xx.xx.xx:5500 -run

This command (or shortcout) will start the winvnc server, and making the connection immediately.


Even if you have launched the winvnc.exe before, this command can still be working properly, just will popup a message of "Another instance of WinVNC is alreading running"

[B]

Thanks, YY. Very cool! I see it works in TightVNC too.

Could it really be this simple? Would a batch file with that string (accompanied by the WinVNC executable) replace all the tortuous work people are putting into the various nice SC spinoffs?

Probably not....

[joachim]

Thanks for all answers.

Yes, really great. I'll try this -run option next time. Currently I made two shortcuts on the desktop of the remote machine: "Step 1", "Step 2". That won't be necessary anymore.

But for new users I would recommend improving the homepage.
The section called "Installation" should be called "Documentation" since it covers more than just installation.
And there should be a page covering the two standard scenarios: Connection started from the viewer (client) side vs. connection started from the viewed (server) side. (I'll write it, if you want.)
All the available docs seem to be for more advanced users, but not for newbies.

Cheers,
Joachim

[B]

Most newbies in my opinion, and especially those interested in a single-click solution, are probably better off with the SCPrompt or ChunkVNC spinoff projects, both of which are discussed or developed in these forums....

But yes, they need to refresh the site, and that's been discussed.

[supercoe]

joachim,

Thanks for the homepage suggestions, the redesign is coming.