After being connected for a while my viewer window will stop responding: the mouse cursor will still show, but I can't click on anything. When I check the server itself (with a monitor, keyboard and mouse) it will work fine.
Sending a ctrl-alt-del doesn't work. However I've found that sending a ctrl-esc (for the Start menu) will work: it brings up the Start menu, and after that the viewer will respond normally. Does anybody know what the problem might be?
Both computers are running Windows 2000 SP4, McAfee firewall (both viewer and server are allowed incoming and outbound TCP/IP traffic on ports 5800 and 5900), and are connected through a switch. I'm using v1.0.0 RC18, with the server installed as a service.
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
Viewer stops responding
I'm having pretty much the same problem. I'm running RC18 with the video driver as a server on a Windows 2000 Advanced Server (w/ SP4 and all updates) box. I've tried the client from two different machines (both XP SP1). When I connect, I get the Windows logon box after sending a C+A+D sequence. I then type in my u/n and p/w and the viewer shows a "Loading you personal settings" dialog box. The viewer then stays on this screen.
When I hook a monitor up to the server machine, my mouse actions are as they should be, but not reflected in the viewer. I can see the cursor, but it does not allow me to do anything. I also tried this with the java-based web client and got pretty much the same result. Is this a problem with the video driver? This is the first time I've installed it, and I've never had a problem before
When I hook a monitor up to the server machine, my mouse actions are as they should be, but not reflected in the viewer. I can see the cursor, but it does not allow me to do anything. I also tried this with the java-based web client and got pretty much the same result. Is this a problem with the video driver? This is the first time I've installed it, and I've never had a problem before
try with ultravnc rc19_12
http://dl.ultravnc.net/TEST19_12
http://dl.ultravnc.net/TEST19_12
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Guest, it doesn't sound like you have the exact same problem. My viewer will work fine one minute then stop responding to mouse clicks. The way you tell it it sounds like you have a problem getting the viewer to run at all?
I may have a solution for you though: it could be something to do with a software firewall running on the host system. As it turns out firewall and antivirus software don't start until a user logs in, so when you log in, the firewall will start and shut the viewer out. The same thing happened to me when I set up an XP box for VNC access. The solution is to allow the VNC traffic through the firewall.
I may have a solution for you though: it could be something to do with a software firewall running on the host system. As it turns out firewall and antivirus software don't start until a user logs in, so when you log in, the firewall will start and shut the viewer out. The same thing happened to me when I set up an XP box for VNC access. The solution is to allow the VNC traffic through the firewall.
Posted first time before I registered, so the Guest entry above is mine.
No, I don't have a firewall running on the server box. I did have that problem before though. I had to connect a monitor and keyboard to the server box to train the firewall.
I know the traffic is getting through to the server as I attached a monitor. When I move the mouse and click buttons on the viewer machine, everything is replicated on the server, i.e. the traffic is passing to the server correctly. I'm just not getting a response on the viewer box. I've tried 2 different viewers (ultr@ and RealVNC) and the java viewer. All exhibit the same behavior.
I'll try RC19 this weekend to see if that works. It's odd, I had Win2K (workstation, not server) in the same setup with no problems, but that was also an older build. I'll have to experiment.[/b]
No, I don't have a firewall running on the server box. I did have that problem before though. I had to connect a monitor and keyboard to the server box to train the firewall.
I know the traffic is getting through to the server as I attached a monitor. When I move the mouse and click buttons on the viewer machine, everything is replicated on the server, i.e. the traffic is passing to the server correctly. I'm just not getting a response on the viewer box. I've tried 2 different viewers (ultr@ and RealVNC) and the java viewer. All exhibit the same behavior.
I'll try RC19 this weekend to see if that works. It's odd, I had Win2K (workstation, not server) in the same setup with no problems, but that was also an older build. I'll have to experiment.[/b]