On Sun, Apr 18, 2021 at 12:23 PM greggailly
wrote:
> I've actually managed to fix this.
>
> So it was a route problem. I now run the vpn with --no-routes flags to make
> sure no routes come and disturb the rest of the process.
> I manually add the necessary route once the container is up and
I've actually managed to fix this.
So it was a route problem. I now run the vpn with --no-routes flags to make
sure no routes come and disturb the rest of the process.
I manually add the necessary route once the container is up and running.
--
Sent from:
Yes when running xfreerdp it is from my personal computer so it has no
interaction with the guacd server.
To be a little more precise, here are a few details concerning the
infrastructure:
1) A docker container running a vpn client connects to the remote network
2) This VPN container exposes
On Sat, Apr 17, 2021 at 7:03 AM greggailly
wrote:
> Hi,
> I can't connect to a remote desktop using guacamole.
> I can confirm the remote accepts connections as I can connect with Microft
> Remote Desktop and xfreerdp on my mac.
> The command on xfreerdp is the following one:
> xfreerdp -u user
Hi,
I can't connect to a remote desktop using guacamole.
I can confirm the remote accepts connections as I can connect with Microft
Remote Desktop and xfreerdp on my mac.
The command on xfreerdp is the following one:
xfreerdp -u user -p password -v 192.168.0.11:08442 --cert-ignore
This works jus