I've had exactly the same issue with W10. Could log on fine with RDP or
even Remmina, and W7 was fine via Guacamole... other than all the usual
stuff I needed to check/do this:
Ensure NLA is off
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp]
???SecurityLayer??? = 1
???UserAuthentication??? = 0
On 11/10/2019 2:03 p.m., Peter Gui wrote:
Darren, Thanks, I have to pull myself away from this for the rest of
the evening but perhaps we could try that out tomorrow? In the mean
time I want to try using freerdp client by itself to see if that is
indeed the problem. I also thought about down grading the remote
desktop app in Windows to an older version but it sounds like that
should not be necessary.
Nick, Yes I have disabled NLA and my connection via rdesktop relies on
authentication at Windows sign in.
Thanks I will let you all know tomorrow if I have any luck
On Thu, Oct 10, 2019 at 5:12 PM Nick Couchman <vn...@apache.org
<mailto:vn...@apache.org>> wrote:
On Thu, Oct 10, 2019 at 2:57 PM Peter Gui <pguit...@gmail.com
<mailto:pguit...@gmail.com>> wrote:
Hello everyone
I have just installed Windows 10 pro inside of a VirtualBox
VM. It is the newest version of windows and is currently
un-activated although I have an OEM key ready. My problem is
that I cannot get remote desktop to work with Guacamole from
my Linux machine.
Here is what does work:
rdesktop (RDP client) works with remote desktop.
Guacamole works with vrde
<https://www.virtualbox.org/manual/ch07.html#vrde> via RDP
Here is what I have tried:
modified registry keys
<https://mangolassi.it/topic/17846/make-windows-10-server-2016-rdp-work-with-guacamole>
ignore cert and security
<http://guacamole.apache.org/doc/gug/configuring-guacamole.html#rdp>
Guacamole will try to connect but will ultimately time out
with the web application stating "The connection has been
closed because the server is taking to long to respond..."
user-mapping.xml:
<connection name="Windows">
<protocol>rdp</protocol>
<param name="hostname">my local ip</param>
<param name="port">3389</param>
<param name="security">any</param>
<param name="ignore-cert">true</param>
</connection>
What I do not see here, that is almost certainly required for RDP
access to a Windows 10 system, is a username and password. If
your Win 10 system is set up to require NLA (which it is by
default), then the username and password *must* be provided at
connection time, or the connection will fail. At this point
Guacamole does not support prompting for parameters, though that
is in the works, so you will have to provide this information or
you will need to turn off the NLA requirement for Windows 10.
-Nick
