Client hangs on "negotiate protocol version" - Need help.

[slacker]

i believe i'm having the same problem, or a variation on this problem that other posters are having. here's what is happening with version 1.0.1 of the server (i need to confirm whether or not it's also happening with 1.0.2 but i'm not near those servers at the moment):

1) i logon using the viewer and the correct DSM encryption key and plugin (version 1.1.8 in this case). everything works fine and i logoff.

2) i select version 1.2.0 of the encryption plugin from the drop down menu in the connection window on the client and attempt to connect. it hangs on "negotiate protocol version" until i hit "cancel."

3) i try to logon using the correct DSM plugin from the menu, 1.1.8, and now the connection which worked perfectly a moment ago no longer works, and it hangs on "negotiate protocol version." i hit "cancel."

4) now the interesting part: i go to the server and restart the VNC service. the instant i do that, a window pops up on the client even after some time has passed and all active vnc status windows have already been closed:

"Connection failed - Error reading Protocol Version
Possible Causes:
-You've forgotten to select a DSMPlugin and the Server uses a DSMPugin... etc"

what this means for me is that if i was a thousand miles away from the server i'm trying to access and i inadvertently tried to connect with the wrong plugin, i would effectively shut myself out from that server until the service could be restarted locally (or perhaps after some unspecified amount of time or some other factor i'm not aware of yet).

this problem could be very, very frustrating if i required access to that machine and suddenly lose it completely because of this! does anyone think they have experienced this same problem and have a solution? is this something that 1.0.2 fixes?

[slacker]

udpate: i upgraded the server i was using to 1.0.2 and the problem is still there. attempting to logon with the incorrect DSM plugin renders the server unreachable until the service is restarted.

there are ways of doing this remotely through an SSH shell, but who wants to deal with that if there's no other reason to run it?

[redge]

[topic=8471][/topic]

instead of only stop and replace the file and run again
you should stop , replace, and restart the computer before begin new test.

[devone]

its becoz "vncviewer.exe" process does not end once u close it.
it still remains in the process list after u close it.

goto task manager and end task all "vncviewer.exe" processes

enjoy!!!

[slacker]

devone, you are so right, and now i'm wondering why i didn't figure that out myself because it perfectly accounts for the behavior i was seeing.

other than that problem, i don't think i'm having stability issues with the latest ultravnc version, so i guess i'll hold off on the patch for now and wait to see what happens.

thanks!

[devone]

ur welcome..
but this is a bug with the viewer and they need to fix it..
the viewer process should end(atleast in sometime) when we close it..

[Igor]

Hello everybody from Russia, Saint-Petersburg. I had such a problem on windows 2008 standart. A welcome window appeared where I entered a password. Then I saw "negotiation of protocol' til i push Cancel button. 1) I've opened port 5900 in firewall. 2)Then i entered to control pannel-administrative tools- services and saw that vnc service was off. In the options i choose from the list 'auto' instead of "off'.3) Reboot the system. And program have started without any problems with negotiations of protocol. And it's stil functioning ok