You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by dieter-erich <di...@meduniwien.ac.at> on 2017/04/29 13:57:01 UTC
guacamole 0.8.3 "invalid login"
Hi,
I just subscribed to this forum because I got completely stuck: Having
installed tomcat8 and guacamole-0.8.3 from the ubunu-16.04 repository
without major problems on my old 32 bit laptop I have spent hours trying to
find out why I always get "invalid login" when entering the test credentials
below on the webpage: http://localhost:8080/guacamole.
I have:
1) defined userid "tomcat" password "tomcat" in
/etc/tomcat8/tomcat-users.xml:
----------------------------------
2) the same userid and password in /etc/guacamole/user-mapping.xml
<!--
<authorize username="tomcat" password="tomcat">
<protocol>vnc</protocol>
<param name="hostname">localhost</param>
<param name="port">5901</param>
<param name="password">tomcat</param>
</authorize>
---------------------------------------
3) I have started turbovncserver with port 5901
--------------------------------------
4) In /var/log/tomcat8/catalina.out I have:
WARNING: Authentication attempt from 127.0.0.1 for user "tomcat" failed.
Apr 29, 2017 3:19:25 PM
org.glyptodon.guacamole.net.basic.AuthenticatingHttpServlet warn
WARNING: Permission denied: Not authenticated
-------------------------------------
Everything seems fine except from that I cannot login. How can I find out
what is wrong? Is there any test to run? Is a file at the wrong position?
Does guacamole not find any of the configuration files?
Thank you so much for help,
D-E
in /var/log/tomcat8/catalina.out:
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/guacamole-0-8-3-invalid-login-tp883.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: guacamole 0.8.3 "invalid login"
Posted by dieter-erich <di...@meduniwien.ac.at>.
Hi Mike,
the following solved the problem:
> citation DRC (TurboVNCusers)
-------------------------------------------------
I generally recommend noVNC over Guacamole for HTML 5 viewing, and I'm
trying to secure funding to add the RFB flow control extensions to noVNC
so that it will perform better on high-latency connections (it will
still never be as fast as Java or native, however.)
As far as Guac, I'm not sure why it's reporting 2.0 as the VeNCrypt
version. It may mean 0.2, which is the version of VeNCrypt that we
support (also the version that TigerVNC supports.) To globally disable
VeNCrypt in the server, edit /etc/turbovncserver-security.conf and set
permitted-security-types such that it only allows non-VeNCrypt security
types. Example:
permitted-security-types = VNC, OTP, UnixLogin, None
will make the server behave like TurboVNC 2.0.x. If you want to do this
just for one instance of the server, then you can start it with an
appropriate -SecurityTypes argument, such as:
-SecurityTypes VNC,OTP,UnixLogin,None
> end citation------------------------------------------------------------------------
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-tp883p935.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: guacamole 0.8.3 "invalid login"
Posted by dieter-erich <di...@meduniwien.ac.at>.
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: dieter.blaas@meduniwien.ac.at
------------------------------------------------------------------------
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.
Re: guacamole 0.8.3 "invalid login"
Posted by Mike Jumper <mi...@guac-dev.org>.
On Mon, May 1, 2017 at 11:41 PM, dieter-erich <dieter.blaas@meduniwien.ac.at
> 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
Re: guacamole 0.8.3 "invalid login"
Posted by dieter-erich <di...@meduniwien.ac.at>.
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?
D-E
---------------------------------------------------------------------
Am 02.05.2017 um 03:06 schrieb Mike Jumper [via Apache Guacamole
(incubating) - Users]:
> On Sat, Apr 29, 2017 at 10:02 PM, dieter-erich
> <[hidden email]> wrote:
>
>> Hi Mike,
>>
>> After modifying /etc/guacamole/user-mapping.xml IT WORKS! Thank you
>> so
>> much for your quick and most helpful answer!
>>
>> 1) I preferred installing from the repository because I felt it more
>> easy
>> and I only later found the very complete description of how to install
>> the
>> newer version from source.
>>
>> Can I still do this? Will it overwrite the older version or do I first
>> have
>> to uninstall the old one?
>>
> You will need to uninstall the old one first.
>
>> 2) I defined a user for tomcat out of despair because I believed that
>> its
>> lacking might be a reason for my problem. Now I understand that this
>> is not
>> necessary
>>
>
> Ah, OK.
>
>> 3) I completely ignored xml synthax and believed that the example
>> would work
>> as such and did not need to be modified.
>>
>> 4) I still cannot login into VNC and, when hitting 'Default' it tries
>> to
>> initalize but then I get the message: 'Error initializing VNC client'
>> despite it is running and I can connect to it via a VNC client by
>> using the
>> same password that is specified in user-mapping.xlm ('xyz' see below).
>> What
>> might be the reason? Does the password have to be the same for both,
>> i.e.
>> 'tomcat'?
>>
> No, the VNC password is independent of the user/password used for
> Guacamole.
>
>> <authorize username="tomcat" password="tomcat">
>> <protocol>vnc</protocol>
>> <param name="hostname">localhost</param>
>> <param name="port">5901</param>
>> <param name="password">xyz</param>
>> </authorize>
>>
>
> You're sure that the VNC server is reachable at localhost from the
> machine running guacd (and that 5901 is the correct port)? Remember
> the connection is established from the perspective of the Guacamole
> server, not the browser.
>
> - 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-tp883p894.html
> To unsubscribe from guacamole 0.8.3 "invalid login", click here.
> NAML
--
View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/guacamole-0-8-3-invalid-login-tp883p896.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: guacamole 0.8.3 "invalid login"
Posted by Mike Jumper <mi...@guac-dev.org>.
On Sat, Apr 29, 2017 at 10:02 PM, dieter-erich
<di...@meduniwien.ac.at> wrote:
> Hi Mike,
>
> After modifying /etc/guacamole/user-mapping.xml IT WORKS! Thank you so
> much for your quick and most helpful answer!
>
> 1) I preferred installing from the repository because I felt it more easy
> and I only later found the very complete description of how to install the
> newer version from source.
>
> Can I still do this? Will it overwrite the older version or do I first have
> to uninstall the old one?
>
You will need to uninstall the old one first.
> 2) I defined a user for tomcat out of despair because I believed that its
> lacking might be a reason for my problem. Now I understand that this is not
> necessary
>
Ah, OK.
> 3) I completely ignored xml synthax and believed that the example would work
> as such and did not need to be modified.
>
> 4) I still cannot login into VNC and, when hitting 'Default' it tries to
> initalize but then I get the message: 'Error initializing VNC client'
> despite it is running and I can connect to it via a VNC client by using the
> same password that is specified in user-mapping.xlm ('xyz' see below). What
> might be the reason? Does the password have to be the same for both, i.e.
> 'tomcat'?
>
No, the VNC password is independent of the user/password used for Guacamole.
> <authorize username="tomcat" password="tomcat">
> <protocol>vnc</protocol>
> <param name="hostname">localhost</param>
> <param name="port">5901</param>
> <param name="password">xyz</param>
> </authorize>
>
You're sure that the VNC server is reachable at localhost from the
machine running guacd (and that 5901 is the correct port)? Remember
the connection is established from the perspective of the Guacamole
server, not the browser.
- Mike
Re: guacamole 0.8.3 "invalid login"
Posted by dieter-erich <di...@meduniwien.ac.at>.
Hi Mike,
After modifying /etc/guacamole/user-mapping.xml IT WORKS! Thank
you so much for your quick and most helpful answer!
1) I preferred installing from the repository because I felt it more
easy and I only later found the very complete description of how to
install the newer version from source.
_Can I still do this? Will it overwrite the older version or do I first
have to uninstall the old one?_
2) I defined a user for tomcat out of despair because I believed that
its lacking might be a reason for my problem. Now I understand that this
is not necessary
3) I completely ignored xml synthax and believed that the example would
work as such and did not need to be modified.
_4) I still cannot login into VNC and, when hitting 'Default' it tries
to initalize but then I get the message: 'Error initializing VNC client'
despite it is running and I can connect to it via a VNC client by using
the same password that is specified in user-mapping.xlm ('xyz' see
below). What might be the reason? Does the password have to be the same
for both, i.e. 'tomcat'?
_
<authorize username="tomcat" password="tomcat">
<protocol>vnc</protocol>
<param name="hostname">localhost</param>
<param name="port">5901</param>
<param name="password">xyz</param>
</authorize>
best, Dieter
------------------------------------------------------------------------
Am 29.04.2017 um 19:25 schrieb Mike Jumper [via Apache Guacamole
(incubating) - Users]:
> On Sat, Apr 29, 2017 at 6:57 AM, dieter-erich <[hidden email]
> </user/SendEmail.jtp?type=node&node=884&i=0>> wrote:
>
> Hi,
> I just subscribed to this forum because I got completely stuck:
> Having
> installed tomcat8 and guacamole-0.8.3 from the ubunu-16.04 repository
> without major problems on my old 32 bit laptop I have spent hours
> trying to
> find out why I always get "invalid login" when entering the test
> credentials
> below on the webpage: http://localhost:8080/guacamole
> <http://localhost:8080/guacamole>.
>
>
> 0.8.3 is quite old at this point - it was released almost 4 years ago.
> Though not the source of your issue, if possible, I recommend instead
> using the latest release:
>
> http://guacamole.incubator.apache.org/releases/0.9.12-incubating/
>
> There have been quite a few improvements since the days of 0.8.3.
>
> I have:
> 1) defined userid "tomcat" password "tomcat" in
> /etc/tomcat8/tomcat-users.xml:
>
>
> Why are you defining a user for Tomcat?
>
> ----------------------------------
> 2) the same userid and password in /etc/guacamole/user-mapping.xml
> <!--
> <authorize username="tomcat" password="tomcat">
> <protocol>vnc</protocol>
> <param name="hostname">localhost</param>
> <param name="port">5901</param>
> <param name="password">tomcat</param>
> </authorize>
>
>
> Your <authorize>...</authorize> section here is commented-out (see the
> "<!--" at the beginning). You will need to remove the "<!--" and "-->"
> surrounding that section for it to be actually read. See:
>
> https://en.wikipedia.org/wiki/XML#Comments
>
> This is likely why you are unable to log in.
>
> ---------------------------------------
> 3) I have started turbovncserver with port 5901
>
>
> Lacking a VNC server running on the port defined within your Guacamole
> connection would prevent the connection itself from being established
> once you've logged in, but would not prevent you from logging in in
> the first place.
>
> - 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-tp883p884.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-tp883p890.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
Re: guacamole 0.8.3 "invalid login"
Posted by Mike Jumper <mi...@guac-dev.org>.
On Sat, Apr 29, 2017 at 6:57 AM, dieter-erich <dieter.blaas@meduniwien.ac.at
> wrote:
> Hi,
> I just subscribed to this forum because I got completely stuck: Having
> installed tomcat8 and guacamole-0.8.3 from the ubunu-16.04 repository
> without major problems on my old 32 bit laptop I have spent hours trying to
> find out why I always get "invalid login" when entering the test
> credentials
> below on the webpage: http://localhost:8080/guacamole.
>
>
0.8.3 is quite old at this point - it was released almost 4 years ago.
Though not the source of your issue, if possible, I recommend instead using
the latest release:
http://guacamole.incubator.apache.org/releases/0.9.12-incubating/
There have been quite a few improvements since the days of 0.8.3.
I have:
> 1) defined userid "tomcat" password "tomcat" in
> /etc/tomcat8/tomcat-users.xml:
>
>
Why are you defining a user for Tomcat?
----------------------------------
> 2) the same userid and password in /etc/guacamole/user-mapping.xml
> <!--
> <authorize username="tomcat" password="tomcat">
> <protocol>vnc</protocol>
> <param name="hostname">localhost</param>
> <param name="port">5901</param>
> <param name="password">tomcat</param>
> </authorize>
>
Your <authorize>...</authorize> section here is commented-out (see the
"<!--" at the beginning). You will need to remove the "<!--" and "-->"
surrounding that section for it to be actually read. See:
https://en.wikipedia.org/wiki/XML#Comments
This is likely why you are unable to log in.
---------------------------------------
> 3) I have started turbovncserver with port 5901
>
Lacking a VNC server running on the port defined within your Guacamole
connection would prevent the connection itself from being established once
you've logged in, but would not prevent you from logging in in the first
place.
- Mike