Can't connect 1.0.2 viewer with 1.0.1 server

[Friedel]

Hi!

I upgraded my UltraVNC to 1.0.2. When I now try to connect to one of my 1.0.1 servers, negotiating the protocol times out.
We use MS_Logon plus the DSM plugin.
When I upgrade the server to 1.0.2 it works fine, but I cannot upgrade all my VNC servers at once.

I tried to run the standalone version of UltraVNC viewer 1.01 as a second instance, but as long as version 1.0.2 is installed on the same machine, the viewer refuses to connect. After deinstallation of 1.0.2 and reinstallation I can connect to the 1.0.1 servers. Ho can I manage to upgrade to 1.0.2?

The readme file stated 1.0.2 will allow a connection to a 1.0.1 server after confirming a warning, but I never got any warning. Just a lockup. Canceling the VNCViewer connect, the task manager still lists VNCviewer.exe in the process list.

Any ideas?

[mod=494,1153330061]moved from bug and fix rel 1.0.x[/mod]

[Marscha]

There is something I don't understand:

I tried to run the standalone version of UltraVNC viewer 1.01 as a second instance, but as long as version 1.0.2 is installed on the same machine, the viewer refuses to connect.

The viewer is not "installed", it is possible to start 1.0.1 and 1.0.2 viewers at the same time on the same machine.
You cannot start two vnc servers listening to the same port on one machine.
What you can try is to start another vnc server listening to a different port and then connect to it with explicitly specifying the port in vncviewer.

[Friedel]

I know that it is possible to run 2 instances of the server on different ports. My problem is the viewer. I can run 1.01 and 1.02 on the same machine but it does not work. 1.01 seems to read registry values of 1.02 that make 1.01 behave the way 1.02 does.

Let me setup a table to explain the situation:

Server version | Viewer version | Result:
Server 1.01 + Viewer 1.01 : OK
Server 1.02 + Viewer 1.02 : OK
Server 1.02 + Viewer 1.01 : fails as expected
Server 1.01 + Viewer 1.02 : fails though readme claims it should work
Server 1.01 + Viewer 1.02 + Viewer 1.01 : 1.01 viewer fails same way 1.02 does.

I cannot upgrade all servers at once, they are located all over the world. So I need the option to either access 1.01 VNC servers with the 1.02 Viewer or to keep both viewers simultanously to chose the viewer version that matches the server version.

[tako]

I suspect version of dsmPlugins are not the same between two VNC releases.
Try to unify the plugin version.
In theory, different version dsmPlugin can connect each other, but sometimes can't.
Hope this helps.

[Friedel]

Thank you, that solved it.

Version 1.02 comes with new plugins. After switching to the former version, everything was ok. Now I can upgrade my server step by step.