Hi Nick, I have a tool that generates an RDP file where the address field is hardcoded. To work around this configuration, we added "full address:s:server-name" to connect to another server. But now we added a guacamole server to allow HTML5 sessions. unfortunately, we are blocked because the field is not taken into account. Is there a way to make it work?
Thank's for your help. Le ven. 17 mai 2024 à 16:00, Nick Couchman <vn...@apache.org> a écrit : > On Fri, May 17, 2024 at 8:54 AM Nick Couchman <vn...@apache.org> wrote: > >> On Fri, May 17, 2024 at 8:51 AM Karim Hamrouni <hamrouni.ka...@gmail.com> >> wrote: >> >>> Hello team, >>> >>> I want to use the "*Alternate full address:s:server name*" option with >>> guacamole. Unfortunately, this doesn't work. only the "*full >>> address:s:server-name*" field is taken into account. >>> If I'm not mistaken, this option has worked in the past. Could you help >>> me? or is there another way to achieve this? >>> >>> >> I'm lost - these options do not look familiar to me in the context of >> Guacamole or even RDP. Could you please provide more detail on where these >> fields are and what you're talking about? >> >> > After some quick Google digging, I see that those are options in the RDP > file when you use the native client. Guacamole has never supported the > "Alternative full address" option (at least, not in recent history); > however, it does support specifying a connection gateway if your goal is to > be able to use that to connect through a gateway. > > Perhaps you can share why you think you need the "Alternate full address" > option? > > -Nick > >>
