On Wed, Jul 31, 2019 at 4:18 AM Niubbo75 <a.sir...@me.com> wrote:
> Hello all,
> sorry if I jumping in into your question, but I have the same issue.
> If I use mstsc I do not have a full login screen but only the login box of
> the application itself, this both on M$ Windows Server 2016 & 2019 STD.
> IMHO it could be some change on RDP protocol from M$ side. I have also try
> to leave a "blank" password and putting in only username or insert a blank
> space in password field, both without goal.
> I have used to configure RDP connections w/out insert any username &
> password with older version of guacamole (till 0.99 if I remember right)
> and
> they works on Windows Server 2008 R2 (and I'm sure of this) and Windows
> Server 2012 R2 (not really sure of that).
> Today I'll check again with guacamole 1.0.0 and Windows Server 2008 R2 (ATM
> I do not have any iso of 2012 R2 here).
>
>
>
You are most likely running into the same issue with NLA being required on
the servers you are connecting to. Because NLA requires the username and
password at connection time, you will not see the Windows login
screen/prompt, and, with the current Guacamole Client, the connection will
fail. We are actively working on getting connection prompts to work such
that this information can be requested from the user during the connection
process, but that doesn't currently work in 1.0.0, nor will it be present
in 1.1.0. Hopefully in whatever release comes after that.
In the meantime, you have a couple of options:
- Disable the NLA requirement and use either TLS or RDP encryption. This
needs to be changed from within Windows.
- Integrate Guacamole with AD authentication (using LDAP) and use the
${GUAC_USERNAME} and ${GUAC_PASSWORD} tokens within the connection
configuration so that username and password are automatically passed
through (
http://guacamole.apache.org/doc/gug/configuring-guacamole.html#parameter-tokens
).
-Nick
