Connection Failed Error Reading Protocol Version
Contents |
reading protocol version New to UltraVNC? Your questions are welcome in this subforum. Post a reply 15 posts • Page 1 of 1 Connection failed--error reading protocol version by zooeyhall » 2008-02-29 21:01 I am uvnc error reading protocol version the IT guy for my company. I recently inherited a site using ultraVNC
Vnc Viewer Error Reading Protocol Version
to connect to client desktops, to download data files. I have much experience using programs like RealVNC and Logmein to there was an error reading an rfb packet 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
Ultravnc Viewer
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 ultra vnc 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! zooeyhall Posts: 6Joined: 2008-02-29 20:38 Top Re: Connection failed--error reading protocol version by X3 » 2008-02-29 21:29 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 direc
Post #1 of 8 (1550 views) Permalink Error Reading Protocol Version Hi, I've now had this error twice in as many days. When I try to connect to my home Win2K desktop, via SSH on a Linux box, from a Win2K laptop, I get the following error (vncviewer trace): Started and Winsock (v 2) initialised bufsize expanded to 4352 Registered connection with app Connected to localhost port 5902 reading 12 bytes Error reading protocol version: `q@ Deregistered connection from app Exiting VNC viewer closing down If I start vncserver on the Linux box, http://forum.ultravnc.info/viewtopic.php?t=12215 then I can connect to that desktop OK from the laptop, so it looks like it's the server on the Win2K that has the problem. This I confirmed the 1st time by rebooting the desktop. After the reboot, I could connect again, for a while. I've not noticed anything significant that causes this to start happening (yet). Any ideas what might be causing this 'version error'. http://www.gossamer-threads.com/lists/vnc/list/45083 Cheers, Eddie _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com --------------------------------------------------------------------- To unsubscribe, mail majordomo [at] uk with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- alex at bittnet Mar28,2002,3:25PM Post #2 of 8 (1504 views) Permalink Re: Error Reading Protocol Version [In reply to] My favorite check for this: try Telnet
running xp, conected to internet via router makingnat. Router making port forwardind to the pc. Running Ultravnc RC9 (yes,I have just seen there is RC10...). Listening on port http://ultravnc-list.narkive.com/HbH16kWb/please-help-connection-failed-error-reading-protocol-version 443 ;-) (not thehttp vnc server, I mean the RFB one)control machine: running xp, conected to internet via FW (applicationlevel gateway) making nat, and allowing https (that certainly https://archive.realvnc.com/pipermail/vnc-list/2002-March/029572.html goesthrough 443; I am unsure what could the application level gateway check... but it seems could not make nothing at application level); runningultra viewer RC9if I make with error reading a browser http://remote.router.fixed.ip:443 I get thefoolowing response in the browser: a page with only RFB 003.006 (ofcourse there is not a single trace of html...)If I launch UltraVnc viewer, request to conect toremote.router.fixed.ip::443 I receive the following message:***@VNC Info:Connection Failed - Error reading protocol versionPossible causes:- YouŽve forgotten to select a DSMPlugin aht the Server uses error reading protocol aDSMPlugin ..... [I think I have not selected such in the server ...]- Viewer and Server are not compatible (they use different RFBprotocoles) !!!!!!!- Bad connection ????Any hint?TIACarlos Brian S. Bergin 2003-08-22 12:06:13 UTC PermalinkRaw Message Post by Carlos BachmaierHi all,controlled machine: running xp, conected to internet via router makingnat. Router making port forwardind to the pc. Running Ultravnc RC9 (yes, Ihave just seen there is RC10...). Listening on port 443 ;-) (not the httpvnc server, I mean the RFB one)control machine: running xp, conected to internet via FW (applicationlevel gateway) making nat, and allowing https (that certainly goesthrough 443; I am unsure what could the application level gateway check... but it seems could not make nothing at application level); runningultra viewer RC9if I make with a browser http://remote.router.fixed.ip:443 I get thefoolowing response in the browser: a page with only RFB 003.006 (of coursethere is not a single trace of html...)If I launch UltraVnc viewer, request to conect toConnection Failed - Error reading protocol version- YouŽ
My favorite check for this: try Telnet