[
https://issues.apache.org/jira/browse/GUACAMOLE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rodrigo Gonçalves reopened GUACAMOLE-370:
-----------------------------------------
Dear all,
I've set up a guacamole installation using the docker images (latest) and the
problem persists.
Same config as presented before.
guacamole/guacd log from Docker:
Error: protocol security negotiation failure
connected to xxxxxx:3389
guacd[1]: INFO: Creating new client for protocol "rdp"
guacd[1]: INFO: Connection ID is "$da3faff8-0e3b-4b11-bdbd-df31ade016e2"
guacd[46]: INFO: No security mode specified. Defaulting to RDP.
guacd[46]: INFO: Resize method: none
guacd[46]: INFO: User "@f5f9b730-f888-48e7-a7bf-830cb504c2be" joined
connection "$da3faff8-0e3b-4b11-bdbd-df31ade016e2" (1 users now present)
guacd[46]: INFO: Loading keymap "base"
guacd[46]: INFO: Loading keymap "en-us-qwerty"
recv: Connection reset by peer
Any ideas?
> Missing broker support in RDP
> -----------------------------
>
> Key: GUACAMOLE-370
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-370
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 0.9.13-incubating
> Environment: Ubuntu Xenial 16.04
> Reporter: Rodrigo Gonçalves
>
> Connecting to a broker does not work. _load-balancing-info_ informed as well
> but no success.
> Only "Error connecting to RDP server" in guacd logs.
> When trying to connect to one of the serves in the collection, it will work
> if it is the server running the user session.
> If a connection is tried to a secondary server, and this tries to redirect to
> the correct one, the connection is lost in guacd.
> Config used:
> {code:xml}
> <config name="Desktop Virtual" protocol="rdp">
> <param name="hostname" value="broker-address" />
> <param name="port" value="3389" />
> <param name="enable-printing" value="true" />
> <param name="ignore-cert" value="true" />
> <param name="load-balancing-info" value="tsv://MS Terminal Services
> Plugin.1.Secretarias" />
> </config>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
