cannot control win7 64bit. It will only view with quirks

[cypherx]

I just seemed to run into this with 1.0.9.5 so I updated both the client and the server to 1.0.9.6.1.

I can connect to the vnc server and see the screen, however I cannot control anything at all. There are TWO PC's that have 1.0.9.6.1 and I can view either of them, but not control them. From those TWO PC's they can also view each other, but not control them either. I'm not sure what happened but here is a series of events that occurred.

VNC 1.0.9.5 was installed and working. Everything was A OK! Remotely, I went into the VNC admin properties, and here I lost all control. SO I disconnect and reconnect and now the authentication is rejected. Did some trials and it seems every time I enter the admin properties, the authentication will always be rejected, unless I highlight the password field and retype it.

Now after resetting the password, I can connect, but I can no longer control the vnc server. So then I updated to 1.0.9.6.1 on both servers and also the client.
I rebooted and STILL cannot control either of the VNC servers.

ALL three computers in question (the client and two servers) are Windows 7 Professional 64-bit. VNC is running as a service. Also after rebooting, the VNC password (while appears masked in admin properties) NEVER works.

I need to get these working to deploy them in our organization. We use VNC for remote support, so I need to be able to control on these computers if someone calls with an issue.

Thanks!

[B]

The most common cause is when the view-only and VNC passwords are the same, but there are other possibilities. Have you been through the FAQ entry?

https://forum.ultravnc.net/viewtopic.php?f=9&t=16839

[cypherx]

I'm not sure, but to rule out the connecting client (my desktop), I uninstalled UltraVNC on the two end users PC's and installed TightVNC 2.0.3. That works just fine, so it was def. a problem on the client side.

We used to use the regular VNC (like the free official version), but for Win7 with Aero and all that, it just doesn't work as good.

[B]

That didn't actually mean it had to be a client side problem -- all except one of the 5 solutions in that FAQ link are server-side issues! (The passwords, for example, are kept server side.)

But if TightVNC does the trick for you, great.

[redge]

B,
for many users like cyperx, client side = vnc server (winvnc), remote
and local is helper or technician (vncviewer)

[B]

Good point, thanks redge!

It's still hard for me to tell which interpretation he meant, but it's probably a moot issue now.

[kio]

Hello,

I'm having the same problem of being able to view but cannot control. My issue is that I am able to control every machine in my network except there is one machine that I cannot control. It pings fine and I can view but for this one machine I am unable to control the machine. Most of the solutions I've seen floating around have been for server-side issues, anyone know how to fix this error client-side?

Thanks. I'm a bit new to VNC so any help would be useful!

[Rudi De Vos]

Are you sure the server is not set to view only (server option "disable viewer input"