Hi,
Lately I have problems with my uvnc (1.0.8.2) sessions. Every time I log off a normal user so that I can logon with the admin user my session closes and I am unable to connect again unless the normal user logs in again.
Uvnc is installed as a service and starts automaticly.
Anyone has a solution for this, or the same issue?
Kind regards,
Mace
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
- 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
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
- 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
Disconnection problems
Re: Disconnection problems
Huh? What do you mean by "logs in again"?
Unless you're using the MSLogon feature, the VNC connection login has nothing to do with a Windows login, <b>especially</b> if you're running it as a service.
Are you saying that the normal user has to log out <b>of Windows</b> if he left his screen up when VNC disconnects? Because that's perfectly normal. And the Windows administrator can kick him off by generating a Ctrl-Alt-Del after connecting via VNC.
Unless you're using the MSLogon feature, the VNC connection login has nothing to do with a Windows login, <b>especially</b> if you're running it as a service.
Are you saying that the normal user has to log out <b>of Windows</b> if he left his screen up when VNC disconnects? Because that's perfectly normal. And the Windows administrator can kick him off by generating a Ctrl-Alt-Del after connecting via VNC.
Re: Disconnection problems
No I don't mean the vnc connection login.
When we take over our clients computers they only have normal user rights, so they can't install something for example.
So what we did then is go to start, log of user and log in as administrator. But now from the moment we are login off the normal user, the uvnc connection shuts down.
When we were using the 1.2 version the connection would stay up and we would see the windows login screen where we could fill in user name and password for the administator.
Thanks
When we take over our clients computers they only have normal user rights, so they can't install something for example.
So what we did then is go to start, log of user and log in as administrator. But now from the moment we are login off the normal user, the uvnc connection shuts down.
When we were using the 1.2 version the connection would stay up and we would see the windows login screen where we could fill in user name and password for the administator.
Thanks
Re: Disconnection problems
Just make sure your service version is the only thing running, and confirm its userid/password settings. If you can't connect to the service from a cold boot of the server (<b>before</b> a user logs on) then the VNC service is obviously <b>not</b> running properly.
When you try to reconnect after the user logs off, what does your VNC viewer report?
The situation you describe is acting as if the VNC server is started in application mode (not service mode) and is closing with the logoff. Maybe it's in the user's startup folder?
When you try to reconnect after the user logs off, what does your VNC viewer report?
The situation you describe is acting as if the VNC server is started in application mode (not service mode) and is closing with the logoff. Maybe it's in the user's startup folder?
Re: Disconnection problems
The service is running on automatic. There is no reference to ultra vnc in startup folders.
So I tested this on a test machine, I log off through uvnc and the connection closes. When I try to log on again through ultra vnc I get the message failed to connect to server. So I log on physicaly and I see the service is still standing on automatic but isn't started.
When I start the service again, I still can't connect, I have to go to my uvnc folder and click on the winvnc.exe before I can make a connection again.
I tried to reinstall the service but that didn't solve the problem.
So I tested this on a test machine, I log off through uvnc and the connection closes. When I try to log on again through ultra vnc I get the message failed to connect to server. So I log on physicaly and I see the service is still standing on automatic but isn't started.
When I start the service again, I still can't connect, I have to go to my uvnc folder and click on the winvnc.exe before I can make a connection again.
I tried to reinstall the service but that didn't solve the problem.
Last edited by mace on 2010-08-11 10:19, edited 1 time in total.