the session hangs on 'Negotiate Protocol Version'

[rockscientist01]

Hi there!

I use UVNC for about 3 Years now and so far I'm quite happy with it.
But there is one little thing that regularly pi%&*#s me off big time:

Every now and then after I disconnected, I am not able to reconnect:
Somehow, the viewer cant connect to the server, although it did connect like 3 min ago... It then just hangs on "Negotiate..." for hours.

edit: I just checked my PC at home via my second remote software called 'girlfriend' and she told me, the eye is still green, although Im not connected from here. I had a couple of processes in my list called 'vncviewer'. Killed'em all, but made no difference: Eye still green, still not able to connect.

Anyone know this issue?

Anyone know how to solve it?

Thanks!

AO

[Hanzolo]

absolutely the same problem here.

UVNC 1.0.2 with MSRC no reg latest

[redge]

[topic=5997][/topic]

[rockscientist01]

thats been like the first thing I encountered when I started to check for my issue... But its not like I dont ever connect to my server... Its just, that sometimes after e.g I shut down my notebook with Uvnc still connected- the server is not closing its connection somehow. And when I then try to connect, it just hangs.

THX

[Hanzolo]

Yeah the provided solutions don't match the problem.

The problem ist that the server does not support time-out at all.
When I end a VNC session on the client unnormally I can't reconnect.
It simply hangs on "negotiate protocol version..."
Of course I checked "disconnect previous clients" in the server options.

I think a not responding client is always connected and prevents further connections.

[rockscientist01]

Yeah, I think Hansolo is perfectly right on this one!
Aint there any way to implement an afore mentioned "time-out" so that the server checks for incoming packets every now and then- and for example if like 5 mins no packets arrive, kills all connected clients?

But anyhow: UVNC really kicks butt!
Thanks for that great program!
And Hanzolo: Im glad to hear that Im not alone with my little hitch!

THX
AO

[Hanzolo]

I'd like to add that this is most likely a problem concerning the authentification plugin MSRC only.
I have no proof on this. All I can say is that I never experienced such problems withoutht encryption plugins at all.

[mucka]

Hi, I have the same problem. I'm using 102 UVNC (viewer on WinXP, server on Win 2000) win athentication is ON. UVNC is running as a service on w2000 PC. The thing is that when I want to connect to distant PC after restart it would give me earlier described error but only if I'm using encryption (AES in my case). If I would dissable encryption, I could normaly connect after restart. Should I run a service with special key so it would expecting to use certain encryption? Or perhaps there is a way to enable encryption after connection is established?

[mucka]

It looks that this problem (at least in my case) was related with blank password that I used for that account. After assigning real password I was able to connect to distant machine. (I was using blank password only for testing purposes).

[psychomike]

I am having the exact same problem. Using UVNC 1.0.5 with the MSRC plugin (same versions (latest) on both client and server) I often get disconnected from the server after some connection time, usually when I'm inactive for at least half an hour, but that might be unrelated.

However, reconnecting doesn't work but fails with the error message ''Error reading protocol version". When I then look at the status of the server, it thinks the client is still connected, even though it's not.

There seems to be no way to automatically disconnect it from the client side, but I have to restart the service on the server (which then prompts a crash message "winvnc.exe encountered a problem...").

Can anyone help?

[Mhazan1]

its a problem with you ports i think, in the admin properties make sure that the http port is 5800, and that the one above it is open on ur router and firewall,

that worked for me

[Danila63]

I have the same problem. I use UltravncViewer (1.0.5.4) installed on a Windows 2003 machine, with DSMPlugin AESV2Plugin.dsm. Sometimes, when I execute the UVNCviewer for contacting a Client (VNC Server 1.0.5), the status of VNC Viewer remains "Negotiate Protocol Version" until I cancel the process. In other case, in the same conditions, yhe connection towards other VNC Servers (with the same VNCServer version) is ok. Can someone help me to resolve the problem? I suspect the problem is in using the encryption plugin, but I have to use it for security reason. have someone resolved this problem?

[ians1]

At the Server machine via Admin Properties find the box that says

Enable Javaviewer (http connect)

and uncheck it.

Connection now working OK.

I think recent and older Java updates affect this.

ian

ps be sure to allow the permissions when clicking Apply and OK

[redge]

bug discovered and confirmed after many test make me little crazy for troubleshoot it but finally found it

tested as application for easy quick check.
bug happen sometime and winvnc close and then could crash the vncviewer with MSRC4Plugin 1.2.4.0 both side

SecureVNCPlugin.dsm 1.0.2.0 stuck on negociate protocol everytime only if server connect first to repeater then viewer connect repeater after 30sec.

settings:
vncviewer + securevncplugin.dsm ID:12345
winvnc + securevncplugin.dsm ID:12345
repeater linux (customized Oliver) : swiss.ultravnc.info
port viewer: 5900
port server:5500
tested with uvnc 1.0.8.2 viewer and server


1. problem
if winvnc iniate connection 1st to repeater swiss.ultravnc.info:5500 with ID:1234 ... wait fews second (30sec)
then
run vncviewer connect to repeater swiss.ultravnc.info:5900 with same ID:1234 and securevnc 1.0.2.0
it stuck negociate protocol version until time out ... 5min.


2. no problem
if viewer connect 1st to repeater and then the server connect to repeater, everything is OK every test.

---------------
remark:
viewer connect first to server is not possible if server autoreconnect to repeater.

[YY]

Thanks redge! Finding out this bug.

I re-do your test again, and my discovery is:
1. This bug is not related to the dsmplugin, just the timeout (at repeater) for remove a server is too short. If the server is not got connected within 30 sec., it will be removed. In contrast, the timeout for viewer is 5 min. (So if the viewer can reach repeater within 30 sec., the connection can be established)

2. Previous version of the repeater has the same bug, EXCEPT the one from 1.0.2, which having a timeout of 5 min for both the viewer & server.

[redge]

YY,

thank you your re-do test. you are right,

after further test, i was arrival that winvnc without dsmplugin, show running as application while vncviewer connect to repeater
That confirm, that what i have sometime but unable to explain what happen.

Question:
is repeater disconnect winvnc like you said ?
or
----edit begin ---
tested after 30sec (repeater108 windows)
recv 0
connection closed by peer
Server Removed from list 12345

for me is winvnc disconnect from repeater to early.
not repeater disconnect server.
---- edit end ----

How do you know ?
what do you think ?

otherwise
the solution is back to change only the timeout 30sec by 1min or 5min, nor any change should be made.


so is'nt break anything, right solution ?

[YY]

----edit begin ---
tested after 30sec (repeater108 windows)
recv 0
connection closed by peer
Server Removed from list 12345

for me is winvnc disconnect from repeater to early.
not repeater disconnect server.
---- edit end ----

How do you know ?
what do you think ?

I ran the test with the winvnc.exe, vncviewer.exe and repeater all in my LAN, so that I can keep watching the repeater log information, and measuring the time that the server/viewer be removed from repeater when not got connected.

I did the test with the same winvnc.exe (1.0.8 ) and vncviewer.exe (1.0.8 ), and only change the repeater for compare.

The tested repeaters are:
- repeater 1.1.0.7 (the one bundled with uvnc 1.0.2 package)
- repeater 1.0.8 (introduced in [topic=16510]Beta repeater 108[/topic]
- PcHelpWare repeater 1.0

The test result:
1. All repeaters will remove a vncviewer if not got connected after 5 min.
2. When the server is not got connected:
　　repeater 1.1.0.7 will remove it after 5 min.
　　All other repeaters will remove it after 30 sec.

Because the viewer & server, and all other test condition are the same, and only the repeater is difference, so with this result I imply this timeout is controlled by the repeater, and thus this is a bug in repeater.

Also 5 min == 3000 sec,
Is a mistake of replacing it with 30 after ver. 1.1.0.7 ?

[redge]

Also 5 min == 3000 sec,
Is a mistake of replacing it with 30 after ver. 1.1.0.7 ?

Ok thank you a lot for the great clarification, that remove any doubt.

3000s = 50min
300s = 5 min
30 sec = 0.5min
yes, is think is a mistake

Ok, i will try to ask change the thing at repeater108 beta
hope will be applied to linux repeater.
back to 300 seconds like before.