Connection Failed Error Reading Protocol Version In Dsm Plugin
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 there was an error reading an rfb packet am the IT guy for my company. I recently inherited a site using ultraVNC ultravnc viewer to connect to client desktops, to download data files. I have much experience using programs like RealVNC and Logmein to ultra vnc 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! 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 f
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 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 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://forum.ultravnc.info/viewtopic.php?t=12215 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 aDSMPlugin ..... [I think http://ultravnc-list.narkive.com/HbH16kWb/please-help-connection-failed-error-reading-protocol-version 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Žve forgotten to select a DSMPlugin aht the Server
a VNC to GDM connection arnieboyOctober 15th, 2005, 05:45 PMThis thread is now defunct! Please refer https://ubuntuforums.org/archive/index.php/t-76638.html to the following thread for a more updated Howto: http://ubuntuforums.org/showthread.php?t=122402 This https://forums.anandtech.com/threads/vnc-over-ssh.1431081/ howto is to show how to setup VNC to show a GDM login screen when you connect to your Ubuntu box, effectively using XDMCP over VNC. A VNC client is easier to get going on Windows than a X server for most people, so error reading here's how to use it to connect to your linux box. First thing you'll need to do is enable the universe repositories: https://wiki.ubuntu.com//AddingRepositoriesHowto Then it's just six easy steps: 1. System->Administration->Login Screen Setup Tab Security->Enable XDMCP Tab XDMCP--> You can disable "Honor Indirect Requests" For kdm or even xdm, just look through the settings and connection failed error find XDMCP, make sure it's enabled. For Intel chipsets 2. sudo apt-get install vnc4server xinetd (comes from universe) For AMD64 chipsets 2. sudo apt-get install vncserver xinetd (comes from universe) 3. sudo gedit /etc/services Put the following line at the end : vnc1024 5901/tcp # VNC & GDM 4. sudo gedit /etc/xinetd.conf Make it look like the following (please do not put the opening and closing braces of defaults in the same line). It wont work!: defaults { } service vnc1024 { disable = no socket_type = stream protocol = tcp wait = no user = nobody server = /usr/bin/Xvnc server_args = -inetd :1 -broadcast -geometry 1024x768 -depth 16 -once -fp /usr/share/X11/fonts/misc -securitytypes=none } 5. sudo /etc/init.d/xinetd restart 6. Restart your computer. That's it! Try connecting from another machine using and see how it goes. If you need a VNC client for Windows, try out UltraVNC http://ultravnc.sf.net it's the one I prefer. for 1024x768 -> vncviewer localhost:1 For connecting from Linux vnc4viewer with tsclient
Display results as threads More... Useful Searches Recent Posts Menu Forums Forums Quick Links Search Forums Recent Posts Menu Log in Sign up AnandTech Forums: Technology, Hardware, Software, and Deals Forums > Hardware and Technology > Networking > VNC over SSH.......... Discussion in 'Networking' started by Praetor, Oct 21, 2004. Praetor Diamond Member Joined: Oct 14, 1999 Messages: 4,498 Likes Received: 0 I've been working on this problem with my secondary computer/server for the past few days. Running Gentoo 2.6.8 and Xorg 6.8.0, tightvnc 1.3a5, and openssh on a headless box and WinXP with Putty and Ultr@VNC I can ssh into the box perfectly fine from both the intranet and internet. I've been trying to get VNC setup on this box so I can use a gui interface remotely when I'm on the road or just for giggles. I've been reading a guide for running a regular vnc server and trying to adapt some of the pointers there so I can do this over ssh. So far, I haven't had any luck at all. I've got Putty set to forward the proper ports (on linux, 1200x1024x24 tcp 5973) over ssh, Ultr@VNC is set to search for a terminal on localhost using that port. From what I've read, this should be correct. When I logon via ssh and do a "startx", it goes through the usual routine of parsing the xorg.conf, but it doesn't look any different from what it did when I had a monitor and keyboard attatched. Loading Ultr@VNC after I've done this gets me a "Failed to connect to server!" error. Has anybody tried anything similar that could help me out? Or should I ask in Operating Systems or Software forums? #1 Praetor, Oct 21, 2004 gaidin123 Senior member Joined: May 5, 2000 Messages: 962 Likes Received: 0 I have followed that exact guide twice in the past and eventually have been able to make it work. Neither time went perfectly for some reason. I remember reading through that entire thread which is very long since there are useful tidbits of info from other people who had problems. You should be SSHing into the box and then running a vnc client connecting to 127.0.0.1:73. I found with UltraVNC that you don't need to specify the full port in the 59xx range for some reason. Also, you should not be running startx from the SSH command line. If you implement that guide correctly what will happen is that when you vnc into the box it will automatic