[
https://issues.apache.org/jira/browse/GUACAMOLE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278104#comment-16278104
]
Michael Jumper commented on GUACAMOLE-455:
------------------------------------------
"Unable to connect to VNC server" is a generic connection failure which
indicates that the VNC server is unreachable. Though you may be able to reach
the VNC server outside of the Docker container, that does not necessarily mean
that guacd running within the Docker container has the same network access. To
test that your VNC server is reachable, you need to perform that test from
within the exact same environment as guacd.
That said, I strongly suspect something is amiss in your VNC setup. The VNC
protocol includes a handshake which involves the server sending its implemented
protocol version _immediately_ upon client connection. For example, using
telnet to connect to the VNC server which I use to access my work desktop, I
see:
{code:none}
[mjumper@dev-mjumper ~]$ telnet localhost 5901
Trying ::1...
Connected to localhost.
Escape character is '^]'.
RFB 003.008
{code}
whereas your telnet test shows:
{code:none}
[akmba5@awsdlbrowse1 ~]$ sudo telnet 10.239.34.90 5911
Trying 10.239.34.90...
Connected to 10.239.34.90.
Escape character is '^]'.
{code}
Note the lack of "RFB" followed by version numbers. Whatever is accepting the
connection on your port 5911 is not a VNC server. Assuming that the machine is
indeed reachable from within the Docker container, this may be why you cannot
connect.
The errors "name or service not known" and "connection reset by peer" within
the RDP logs also denote network trouble preventing the connection from
succeeding. In the final RDP connection attempt, it looks like the connection
succeeds, but actual negotiation of the connection fails. Check whether your
RDP server requires NLA (or possible TLS), and make sure the Guacamole
connection is configured to match. If TLS encryption is being used (this is the
default for recent versions of Windows), the certificate will likely be
self-signed, and you will need to set the connection parameter to ignore the
certificate.
If you continue having issues, please start a thread in the mailing lists.
Though things may not be working for you at the moment, I can definitely assert
that Guacamole isn't fundamentally broken, and can indeed establish outbound
network connections. If there is something within your environment which is
preventing this from working as expected, we can help you chase that down on
the mailing lists.
> Unable to connect to vnc server (x11VNC)
> ----------------------------------------
>
> Key: GUACAMOLE-455
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-455
> Project: Guacamole
> Issue Type: Bug
> Components: guacd-docker, VNC
> Affects Versions: 0.9.13-incubating
> Environment: red-hat 7 , with docker installed .
> Reporter: akshay barahate
> Priority: Blocker
> Attachments: RDP-issue.png, VNC_issue.png, VNC_setting.png, telnet
> 5911.jpg
>
> Original Estimate: 298h
> Remaining Estimate: 298h
>
> I am trying to connect the VNC session from guacamole , guacd throwing issue
> "Unable to connect to VNC server ".
> for testing purpose I have configured 4 protocol in portal
> 1)SSH : working fine !!
> 2)xRDP :working fine !!
> 3)RDP : Unable to connect the RDP server .
> 4)VNC(x11VNC) : unable to connect VNC server .
> All the VNC connection are running inside docker .
> I am able to connect them using google VNC plugins.
> When I try to connect from guacamole portal it is throwing me error.
> telnet for VNC and RDP port is giving me positive response .
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
