1. AutoReconnect should be a option in server's UI, not just a command line. now , i have no way to let server to auto connect to viewer or repeater when the server computer startup without login windows.
2. server should connect to the proxy(repeater) auto according to settings(or remember the proxys or viewers settings) after system reboot, then wait new viewers to start a new sessions. now, have to give a ID code.it's not so good. if any connect droped, server should connect to the proxy auto for all sessions or some sessions based on settings.
The following is the Case:
I have a pc in office and another in home,both are behind firewall and NAT, now, i'm in home want to control the pc in office, but the pc in office is power off, so i call someone to power on my pc in office[no body can login my pc],then i can connect to and login my pc in office from home.Or,i reboot the system and then login to do something...
that's what many people need!!!
NOTE: I use windows scheduled task to run a .bat when system start, BUT it not work!!! <intallPath>\winvnc -autoreconnect -connect ViewerIP or ProxyIP. (I have verify the .bat is run, all commands before the winVnc is run correct). BUt it work when i run the .bat by double click after login.
Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Server Auto Connect should be improved in 2 point!!!
-
Jethro.Guo
- Posts: 3
- Joined: 2007-01-22 07:43
Server Auto Connect should be improved in 2 point!!!
Last edited by Jethro.Guo on 2007-01-25 03:00, edited 2 times in total.
-
Jethro.Guo
- Posts: 3
- Joined: 2007-01-22 07:43
Re: Server AutoReconnect should be improved in 2 point!!!
copy from http://www.realvnc.com/pipermail/vnc-li ... 54055.html
Yes, I have it running as a service. But I've tried every
configuration.
In user mode the service won't even run without a user logged in, so
user mode is out.
When running the server as a service, there are three options:
1. Log on as "Local System Account", with "Allow service to interact
with desktop" checked. This is the default Log On mode that VNC
registers itself .This allows the service to run without a user session, but, as stated in my original post, when my scheduled task runs...
winvnc.exe -connect mysubdomain.homeip.net::<port>
...it executes without an error but the client is not added.
2. Log on as "Local System Account", with "Allow service to interact
with desktop" unchecked. I tried this configuration to see if it would
make any difference. The difference is that now my scheduled task (see
above) executes and returns the following error:
"Unable to locate existing VNC Server."
3. Log on as "This account". This option requires you to specify
either a domain or machine user account and password. It doesn't
"interact with desktop" and therefore doesn't respond to "add client"
commands. Whether I use a domain account or user account (both with
machine Admin privileges, of course) I still get the error:
"Unable to locate existing VNC Server."
Yes, I have it running as a service. But I've tried every
configuration.
In user mode the service won't even run without a user logged in, so
user mode is out.
When running the server as a service, there are three options:
1. Log on as "Local System Account", with "Allow service to interact
with desktop" checked. This is the default Log On mode that VNC
registers itself .This allows the service to run without a user session, but, as stated in my original post, when my scheduled task runs...
winvnc.exe -connect mysubdomain.homeip.net::<port>
...it executes without an error but the client is not added.
2. Log on as "Local System Account", with "Allow service to interact
with desktop" unchecked. I tried this configuration to see if it would
make any difference. The difference is that now my scheduled task (see
above) executes and returns the following error:
"Unable to locate existing VNC Server."
3. Log on as "This account". This option requires you to specify
either a domain or machine user account and password. It doesn't
"interact with desktop" and therefore doesn't respond to "add client"
commands. Whether I use a domain account or user account (both with
machine Admin privileges, of course) I still get the error:
"Unable to locate existing VNC Server."