[
https://issues.apache.org/jira/browse/GUACAMOLE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
R Aspinwall updated GUACAMOLE-1236:
-----------------------------------
Description:
Found that old Guacamole 0.9.14 server would not establish an RDP to Windows
2019 Server, but was able to connect using Windows RDP client.
After experimentation on the Windows 2019 Server, I found a Group Policy
setting which would allow Guacamole 0.9.14 to make an successful RDP connection.
Modify Group Policy (for Guacamole 0.9.14)
Computer Configuration -> Administrative Templates -> Windows Components ->
Remote Desktop Service -> Remote Desktop Session Host -> Security -> Require
use of specific security layer for remote (RDP) connections - Enable (and set
to policy to negotiate)
Tried with Guacamole 1.2.0 on our new server and to get it to work I had to
change the Group Policy
Modify Group Policy (for Guacamole 1.2.0)
Computer Configuration -> Administrative Templates -> Windows Components ->
Remote Desktop Service -> Remote Desktop Session Host -> Security -> Require
use of specific security layer for remote (RDP) connections - Enable (and set
to policy to RDP)
There is a bug in Guacamole RDP client in 1.2.0 in that it can not negotiate
RDP or SSL connectivity with Windows 2019 Server. When you configure Windows
2019 to use SSL in the Group Policy object above the connection fails, if set
to negotiate it fails it only works with set to RDP
was:
Found that old Guacamole 0.9.14 server would not establish an RDP to Windows
2019 Server, but was able to connect using Windows RDP client.
After experimentation on the Windows 2019 Server, I found a Group Policy
setting which would allow Guacamole 0.9.14 to make an successful RDP connection.
Modify Group Policy
Computer Configuration -> Administrative Templates -> Windows Components ->
Remote Desktop Service -> Remote Desktop Session Host -> Security -> Require
use of specific security layer for remote (RDP) connections - Enable (and set
to policy to negotiate)
Tried with Guacamole 1.2.0 on our new server and that to get it to work I had
to change the Group Policy
Computer Configuration -> Administrative Templates -> Windows Components ->
Remote Desktop Service -> Remote Desktop Session Host -> Security -> Require
use of specific security layer for remote (RDP) connections - Enable (and set
to policy to RDP)
> Guacamole 1.2.0 can not make RDP connection to Windows 2019 Server
> ------------------------------------------------------------------
>
> Key: GUACAMOLE-1236
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1236
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
> Affects Versions: 1.2.0
> Environment: Ubuntu 20.04 Server running Guacamole 1.2.0
> Reporter: R Aspinwall
> Priority: Major
>
> Found that old Guacamole 0.9.14 server would not establish an RDP to Windows
> 2019 Server, but was able to connect using Windows RDP client.
> After experimentation on the Windows 2019 Server, I found a Group Policy
> setting which would allow Guacamole 0.9.14 to make an successful RDP
> connection.
> Modify Group Policy (for Guacamole 0.9.14)
> Computer Configuration -> Administrative Templates -> Windows Components ->
> Remote Desktop Service -> Remote Desktop Session Host -> Security -> Require
> use of specific security layer for remote (RDP) connections - Enable (and
> set to policy to negotiate)
>
> Tried with Guacamole 1.2.0 on our new server and to get it to work I had to
> change the Group Policy
> Modify Group Policy (for Guacamole 1.2.0)
> Computer Configuration -> Administrative Templates -> Windows Components ->
> Remote Desktop Service -> Remote Desktop Session Host -> Security -> Require
> use of specific security layer for remote (RDP) connections - Enable (and
> set to policy to RDP)
>
> There is a bug in Guacamole RDP client in 1.2.0 in that it can not negotiate
> RDP or SSL connectivity with Windows 2019 Server. When you configure Windows
> 2019 to use SSL in the Group Policy object above the connection fails, if set
> to negotiate it fails it only works with set to RDP
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
