How can I have vncserver initiate/add new client on startup?

[SuperTurtle]

I setup the vncserver as a service. I now want to on windows startup execute a command line to initiate an outgoing connection. (the machine is behind a firewall, and so I am using the repeater).

I want to execute the following:

winvnc -autoreconnect ID::2345 -connect 192.168.1.10::80

(as you can see in the above, I using the repeater).

If I set winvnc to run as a service, then when I execute the above command line as a startup batch file, I get the message to the effect that an instance of winvnc cannot be found. However, if I let windows 100% finish its boot process and THEN click on the same batch file in the menu startup folder, then the above line runs just fine and the connection works.

And, of course after windows boots and I in place of that batch file simply go:
run->cmd to get to the command prompt, the following works fine:

winvnc -autoreconnect ID::2345 -connect 192.168.1.10::80

So, in both cases, the service does start and I can enter the command above and it works fine. However, I want this to occur during windows startup, or at least as a batch file in the startup menu.

So, how can one set the startup parameters (using windows xp) for winvnc? As it stands now you really can't use the repeater with this setup unless some workaround is possible.

I generally use single click vnc for support. But, in this case I simply need remote access to a computer of mine and it is on dhcp. The repeater thus solves this problem very nice. However, I still have to have someone start the remote session as per above.

I thinking that other people out there likey have had a need to remote access their computer without the need for someone to actually start the connection on the other end (so, a solution to this problem would help many people).

My spider sense tells me this limitation might be design for security reasons, but perhaps some type of hack or workaround is possible. I just simply want to be albe to connect to a pc using the repeater.

It seems that you have to have the server initiate the connection AFTER the service has started and after windows has complete booted and that = asking person on other end to start this.

Kind of chicken or egg who is first deal here.

Any and all suggestions welcome.

I am using:
Windows sp3, no virus software. For testing, the fire walls on all computers are disabled.
UltraVNC Win32, 1.02

Super Turtle

[YY]

You need to switch to 1.0.5, which supports this feature.

See [post=51726]How to make UVNC server automatically reverse call Repeater[/post] for a reference.

[SuperTurtle]

You need to switch to 1.0.5, which supports this feature.

See [post=51726]How to make UVNC server automatically reverse call Repeater[/post] for a reference.

Excellent....

Wow, that is a new and nice feature (just tried it..and it works).

About the only thing was I had to move the option to the top of the section

[Admin]
service_commandline=-autoreconnect ID::2345 -connect 192.168.1.10::80

I initially placed the “service_commandline” it at the end of the section…and it did not work.

I will have to play around to get the logon working. However, this is a nice feature that expands the flexibility of ultra vnc.

If one has a repeater setup like I do, then this feature allows one a zero config in terms of not having to touch the routers and networks involved.

Thank you very kindly for taking the time to point out this new feature!...well done!!

Super Turtle