Re: [EXT] WELCOME to user@guacamole.apache.org
On Mon, Oct 11, 2021, 12:53 Sanjeevi Mahalingam wrote: > Thank you, Nick. > > The AWS AMI contains both client and server configured. > > We can be able to login the Guacamole console and added new connection for > RDP. > > When we tried to connect the RDP, we can see that the windows blue screen > with message saying, “Waiting for Local Session manager" "Waiting for Group > Policy Client". > These messages are being rendered by Windows over RDP. If you are seeing these messages, you have already connected successfully, and are now just waiting for Windows itself to prepare the desktop session. - Mike
Re: [EXT] WELCOME to user@guacamole.apache.org
On Mon, Oct 11, 2021 at 3:53 PM Sanjeevi Mahalingam wrote: > Thank you, Nick. > > The AWS AMI contains both client and server configured. > > We can be able to login the Guacamole console and added new connection for > RDP. > > When we tried to connect the RDP, we can see that the windows blue screen > with message saying, “Waiting for Local Session manager" "Waiting for Group > Policy Client". > > Okay, this indicates that Guacamole is working fine, if you are able to create a connection and get a "Waiting for Local Session manager" message. Whatever issue you're seeing, this would indicate that Guacamole is working fine. > The AWS AMI published by Bitnami. > > Okay, but my point was that the Guacamole project does not publish that image, so, while we can try to help you figure out what's going on, we don't know how they've configured the image, what customizations it may contain, etc. -Nick
RE: [EXT] WELCOME to user@guacamole.apache.org
Thank you, Nick. The AWS AMI contains both client and server configured. We can be able to login the Guacamole console and added new connection for RDP. When we tried to connect the RDP, we can see that the windows blue screen with message saying, “Waiting for Local Session manager" "Waiting for Group Policy Client". The AWS AMI published by Bitnami. Sanjeevi Mahalingam Office: Email: smahalin...@vitechinc.com<mailto:smahalin...@vitechinc.com> Web: www.vitechinc.com<http://www.vitechinc.com/> [cid:image001.png@01D7BEB8.FCD49890] [Vitech Logo]<https://www.vitechinc.com/> [LinkedIn] <https://www.linkedin.com/company/vitech-systems-group> [Twitter] <https://twitter.com/vitechsystems> [Facebook] <https://www.facebook.com/vitechinc/> From: Nick Couchman Sent: Monday, October 11, 2021 3:48 PM To: user@guacamole.apache.org Subject: Re: [EXT] WELCOME to user@guacamole.apache.org ⚠ This email originated from outside the organization. Be careful while clicking on links or opening attachments. On Mon, Oct 11, 2021 at 3:39 PM Sanjeevi Mahalingam mailto:smahalin...@vitechinc.com.invalid>> wrote: Hello Guacamole Team, We are using Amazon Marketplace AMI for Guacamole Application and, we launched an EC2 machine. We can able to login the guacamole console however the RDP to Windows machine is not working within same network. The Guacamole Project does not publish any official AWS AMI for the application, so I'm not sure who produced this. Please assist in case of any misconfiguration against the guacamole-server. When I did the below command. guacd -b then the error is "ERROR: Unable to bind socket to any addresses." When you run "guacd -b ", the value for "" should be one of the IP addresses of the system running guacd, not the system you're trying to connect to. This is the IP address to which guacd binds, not the IP to which it connects. Also, Guacamole is made up of two components: 1) guacd, or guacamole-server, the component that connects to the remote desktop systems (RDP, SSH, etc.), and translates that to the Guacamole protocol. 2) guacamole-client, the web-based front-end application, which runs in a Java application server (Tomcat, for example), serves the web application, and provides the tunnels between the browser and guacd. You need *both* of these components to use Guacamole as a whole. I highly suggest you start by reading the documentation on the Guacamole site to gain an understanding of how it works and how to configure it - it seems that there is some misunderstanding in how to use Guacamole to correctly configure and use Guacamole. http://guacamole.apache.org/doc/gug/ -Nick This e-mail message and any files transmitted with it may contain confidential and proprietary information and are intended solely for the use of the individual or entity to which they are addressed. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this e-mail in error please notify the sender by reply email and destroy all copies of the original message. Thank you for your cooperation. <> - To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org For additional commands, e-mail: user-h...@guacamole.apache.org
Re: [EXT] WELCOME to user@guacamole.apache.org
On Mon, Oct 11, 2021 at 3:39 PM Sanjeevi Mahalingam wrote: > Hello Guacamole Team, > > We are using Amazon Marketplace AMI for Guacamole Application and, we > launched an EC2 machine. We can able to login the guacamole console however > the RDP to Windows machine is not working within same network. > > The Guacamole Project does not publish any official AWS AMI for the application, so I'm not sure who produced this. > Please assist in case of any misconfiguration against the guacamole-server. > When I did the below command. > > guacd -b then the error is > > "ERROR: Unable to bind socket to any addresses." > > When you run "guacd -b ", the value for "" should be one of the IP addresses of the system running guacd, not the system you're trying to connect to. This is the IP address to which guacd binds, not the IP to which it connects. Also, Guacamole is made up of two components: 1) guacd, or guacamole-server, the component that connects to the remote desktop systems (RDP, SSH, etc.), and translates that to the Guacamole protocol. 2) guacamole-client, the web-based front-end application, which runs in a Java application server (Tomcat, for example), serves the web application, and provides the tunnels between the browser and guacd. You need *both* of these components to use Guacamole as a whole. I highly suggest you start by reading the documentation on the Guacamole site to gain an understanding of how it works and how to configure it - it seems that there is some misunderstanding in how to use Guacamole to correctly configure and use Guacamole. http://guacamole.apache.org/doc/gug/ -Nick
