On Thu, Oct 10, 2019 at 2:57 PM Peter Gui <[email protected]> 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
