Connection failed--error reading protocol version

[zooeyhall]

I am the IT guy for my company. I recently inherited a site using ultraVNC to connect to client desktops, to download data files. I have much experience using programs like RealVNC and Logmein to manage desktops remotely, but never used UltraVNC.

Anyway--I am having a problem with connecting to one computer. It brings up the error in the subject line of this post. There are other computers that we connect to and they are working fine.

As I am so new to this program, can anyone suggest any of the more obvious things I should check first? It must be something with the server running on this particular client pc (the one we are trying to connect to), because the viewer on the connecting pc is able to see other ultravnc clients.

I have done a search on the forum for this problem, and found about as many causes for this as there are letters in the alphabet. I need someone to narrow it down to obvious things I should check first.

Thanks for the help! It IS appreciated!

[X3]

You post makes me giggle, I cant help it it really does.

Lets presume that the machine can be pinged and its networked properly, as well as firewall routers are not an issue depending on circumstances...

The causes could be several, could be that the server is using encryption and your viewer is not selected encryption option or vice-versa.

Could be that the RC4.key is not the same in between the viewer and server

Could be that the server and viewer have become incompatible by superceeded versions in either end (I dont know if that matters with uVNC) but it makes little difference.

or it could be something it escapes me but I could probably resolve would I have more information or be in your shoes.

What I would do is grab a full uVNC directory from a working laptop and drop it in the other one.

Which brings me to the first paragraph of my post.

Ironic really but thats another story and Im not in the mood.

Hope it helps eh!

And if it does give me a job.

No really Im serious.

[redge]

> Connection failed--error reading protocol version
Is the exact message or you wrote what you remember from your mind ?


[topic=5997][/topic]
[topic=7023][/topic]

[zooeyhall]

That's the exact message. It also goes on to say:

You've forgotten to select a DSMPlugin...
Viewer and server not compatable (..different RFB protocols)
Bad Connection

Similar to other posts I have read on this issue.

I did check the server properties and the DSM only allows "None" (no other option available)

[zooeyhall]

Sorry I made X3 laugh.

[redge]

did you try to use Ultra vncviewer 1.0.4 ?
[topic=11850][/topic]

What you did successful ?

realvnc <--> ultravnc
ultravnc <--> ultravnc
tightvnc <--> ultravnc
tightvnc <--> realvnc

client: what is it for you ?
Your customer or vncviewer known as client ?
if your customer, this mean ultravnc server (remote)
you, ultravnc viewer (local)

[redge]

> I did check the server properties and the DSM only allows "None" (no other option available)

This mean, there no dsmplugin on the folder of your ultravnc viewer or ultravnc server
you don't know about your customer, because you can't connect to it with your viewer.

[redge]

viewer or server

maybe this not help you
this an incompatible version between your viewer and customer ultravnc server.

can you know the exact name and build of ultravnc server of remote computer of your customer by phone or e-mail or whatever you prefer.

[zooeyhall]

As I didn't set this up originally, I have to proceed from what I was told about the setup. Here are the facts as I know them:

We have 20 remote desktops we connect to, that are running the Server.

We have only one viewer (ourselves) that is accessing these desktops.

They were all setup 6 months ago, at the same time. Nothing has been installed or updated on either end since then.

Since everything was setup at the same time (during a single day), I can only assume that the same UltraVNC Server version and settings were used for all the remote computers.

Everything was working as far as connectivity to the 20 remote computers, until 1 week ago, when the one remote computer started bringing up the error I have described. We are still able to access the other 19 remote computers ok.

It all points to something changing with the one computer that cannot be accessed. I will try to find out from the remote user the version number of UltraVNC they are using, and compare it with ours. However, it is unlikely that the remote computer user would have changed the software on their own.

Clarification: Remote user, remote customer=running UltraVNC server

[zooeyhall]

deleted incorrect post

[X3]

have you at least tried to do what I suggested?

and it was giggle you made me giggle not laugh...

Try what I suggested please.

you can instruct him how to stop/service run service upload the files that you email to him fro a known working directory from a working computer (sometimes things happen to currupt data or someone deleted somethisng or some other cause does not matter which or what.

Replace his crap reboot start service and run

and hopefully he can have admin control otherwise the other solution is to use uVNC-SCIII

[Rudi De Vos]

I can only explain the origin of the message, many possible causes

When the viewer connect to the server, the server need to answer
that he is a vnc server with a version number.
When something else is receive -> protocol error

In cmd a good server answer like this ( you can use telnet to test it)
C: \ telnet ipaddress_server 5900
RFB 003.006

*encryption can be the cause
*unstable state of the server (restart server does the trick)
*Firewall, the server message get blocked send partial message (RFB 0)
*...

It happen on the very first handshaking between server and viewer.

[YY]

I did check the server properties and the DSM only allows "None" (no other option available)

That means the server cannot find any dsmplugin in its working folder, so the server is now working w/o it. Although the reason is still unknow (may be just deleted by someone in mistake), but can you try to connect it w/o dsmplugin as well, to see what's going on?

You got the said error message, that means at least the VNCserver is still running and can response your connection. Of course, it may be running under a abnormal state caused by infection of virus or .....

[X3]

I already suggested a solution that will work.

[sure]

..