Thanks! I have posted the question in the turbvnc user group and shall let you know! Dieter
------------------------------------------------------------------------ Dieter Blaas, Max F. Perutz Laboratories Medical University of Vienna, Inst. Med. Biochem., Vienna Biocenter (VBC), Dr. Bohr Gasse 9/3, A-1030 Vienna, Austria, Tel: 0043 1 4277 61630, Fax: 0043 1 4277 9616, e-mail: [email protected] ------------------------------------------------------------------------ Am 07.05.2017 um 23:50 schrieb Mike Jumper [via Apache Guacamole (incubating) - Users]: > On Mon, May 1, 2017 at 11:41 PM, dieter-erich <[hidden email] > </user/SendEmail.jtp?type=node&node=923&i=0>> wrote: > > I have checked again: turbovncserver 2.1.1 is running and I can > definitely reach localhost via vnc on port 5901 with turbovncviewer > v2.1.1. > > However, when trying to run vnc over guacamole I find the following > lines in syslog: > > May 2 08:23:13 ubuntu guacd[3224]: Protocol "vnc" selected > May 2 08:23:13 ubuntu guacd[3224]: VNC server supports protocol > version > 3.8 (viewer 3.8) > May 2 08:23:13 ubuntu guacd[3224]: We have 3 security types to read > May 2 08:23:13 ubuntu guacd[3224]: 0) Received security type 19 > May 2 08:23:13 ubuntu guacd[3224]: Selecting security type 19 > (0/3 in > the list) > May 2 08:23:13 ubuntu guacd[3224]: 1) Received security type 2 > May 2 08:23:13 ubuntu guacd[3224]: 2) Received security type 16 > May 2 08:23:13 ubuntu guacd[3224]: Selected Security Scheme 19 > May 2 08:23:13 ubuntu guacd[3224]: GnuTLS initialized. > May 2 08:23:13 ubuntu guacd[3224]: Got VeNCrypt version 2.0 from > server. > May 2 08:23:13 ubuntu guacd[3224]: Unsupported VeNCrypt version. > May 2 08:23:13 ubuntu guacd[3224]: Error instantiating client: > UNKNOWN > STATUS CODE: > > is there anything wrong with my turbovncserver? Am I missing > anything? > > > I don't think you're missing anything per se, nor that TurboVNC is > doing anything particularly wrong, but it looks like libvncclient > doesn't fully support the security scheme used by TurboVNC. During > security negotiation, TurboVNC reports that it supports several > methods including "VeNCrypt", libvncclient chooses that method, and > then subsequently finds out that the version used by TurboVNC is > actually unsupported and has to bail out. > > Is there a way to configure TurboVNC to exclude the "VeNCrypt" method? > > - Mike > > > > ------------------------------------------------------------------------ > If you reply to this email, your message will be added to the > discussion below: > http://apache-guacamole-incubating-users.2363388.n4.nabble.com/guacamole-0-8-3-invalid-login-tp883p923.html > > > To unsubscribe from guacamole 0.8.3 "invalid login", click here > <http://apache-guacamole-incubating-users.2363388.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=883&code=ZGlldGVyLmJsYWFzQG1lZHVuaXdpZW4uYWMuYXR8ODgzfC0xMTk1NTc0MzI=>. > NAML > <http://apache-guacamole-incubating-users.2363388.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > -- View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/guacamole-0-8-3-invalid-login-tp883p924.html Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
