Reconnecting after reboot

[tanza14]

Is this a part of chunkvnc and maybe im missing it? Is there anyway to have it reconnect after reboot. I would want to specify when the reconnection would occur and not just reconnect all the time.

[B]

If ChunkVNC is installed as a service, then it is always trying to connect to the repeater, even after rebooting.

You'll still need to relaunch the viewer manually.

And there may still be some problems; I believe ChunkVNC is really intended for support when people at both end are physically present.

[tanza14]

yes that works but if its not installed as a service that option would be nice to have. ive tested a different software ,the remote support system and it works really well but its expensive

[supercoe]

Is this a part of chunkvnc and maybe im missing it? Is there anyway to have it reconnect after reboot.

As B stated if you want to reboot the machine just choose the "Install as Service" option from the tray icon.


I would want to specify when the reconnection would occur and not just reconnect all the time.

Simple, save InstantSupport.exe to their desktop and tell them when to start it.

[supercoe]

B,

I've been having luck lately with the 1.0.9.6.1 always reconnecting even after a day. Further testing is in order but I think we are good to go on that front now.

[B]

Excellent. Combine that with NAT2NAT and ohboyohboy.....

[supercoe]

Wouldn't have to combine anything with NAT2NAT as the server is just sitting there listening as opposed to making an outgoing connection.

[B]

(I meant once the redirector code is available for integration with the repeater.)

[KapaiKiwi]

We are running the latest version of ChunkVNC.

As with previous versions we have had issues getting to reconnect when running as a service.

The domain name points to a webserver which has the repeater on it and a static IP.

We are using the tool 20+ times a day and it works every time but If you select install as a service, and then reboot the machine it just never comes back.

What should I be looking for to solve this? Is this a known issue?

Its a feature we would find quite handy but have never been able to get working.

Any help would be appreciated.

[B]

That makes no sense; I've never heard that particular issue -- are you sure you have rights to install it as a service? Do you get UAC prompts? After rebooting does the service appear in the control panel, and what are its settings?

[JonD]

I have had this happen (no recovery after a reboot) with installed service. Every time, when it happened it was the local software firewall/anti-virus looking for permission. Once the local user granted and saved the permission, subsequent reboots worked as expected.

I frequently work on computers that are unattended once I get through the initial anti-virus/firewall issues and have had no trouble doing reboots.

In answer to an early question in this thread, if I work on a computer over 2 days, I usually schedule a service shutdown and restart (typically overnight when my repeater goes off-line) using:
net stop "uvnc_service"
and
net start "uvnc_service"
next morning.

When I was having issues with my repeater IP address changing and the client not connecting, I even scheduled additional stop/starts during the day.

JonD

[KapaiKiwi]

@B

Once rebooted we have checked that the service is starting correctly and that it is pointing to the right place.

It says its all running but when you try to connect remotely you just get nothing.

We are running Eset Nod32 AV, I will try disabling that as above and see if it makes any difference