Guacamole?

How do I ping it from guacamole itself?
Just run ping 192.168.68.15 in the Guacamole CT.

Another thing I dont understand is why it lists only 2 VMs?
Sorry I thought it was a VM, but since it is a container, the proper command would be pct config 102. It should also show up in pct list then.
 
Just run ping 192.168.68.15 in the Guacamole CT.


Sorry I thought it was a VM, but since it is a container, the proper command would be pct config 102. It should also show up in pct list then.

I get this in the Docker/Guacamole terminal
root@Docker:~# ping 192.168.68.15
PING 192.168.68.15 (192.168.68.15) 56(84) bytes of data.

root@proxmox:~# pct config 102
arch: amd64
cores: 3
features: keyctl=1,nesting=1
hostname: Docker
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=46:28:6F:63:0D:FF,ip=dhcp,type=veth
onboot: 1
ostype: ubuntu
rootfs: DIR01:102/vm-102-disk-0.raw,size=8G
swap: 512
unprivileged: 1
 
Networking stuff like this is always a bit tricky to debug, since there are a lot of moving parts.

Did you setup any firewall rules in proxmox/your router/windows ? If yes, could you just try turning off the firewall and see if it works?
Can you ping the Docker VM from your windows machine? (same command as in Linux, just with different IP)
 
Networking stuff like this is always a bit tricky to debug, since there are a lot of moving parts.

Did you setup any firewall rules in proxmox/your router/windows ? If yes, could you just try turning off the firewall and see if it works?
Can you ping the Docker VM from your windows machine? (same command as in Linux, just with different IP)

No problem pinging the guacamole machine from the windows machine:

Pinging 192.168.68.131 with 32 bytes of data:
Reply from 192.168.68.131: bytes=32 time<1ms TTL=64
Reply from 192.168.68.131: bytes=32 time<1ms TTL=64
Reply from 192.168.68.131: bytes=32 time<1ms TTL=64
Reply from 192.168.68.131: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.68.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

The only firewall rule I have set up is the one to be able to read RDP on that Windows VM machine, havent touched anything else.
 
I don't know how it is in Windows nowadays, but maybe then the Windows Firewall might block your requests? Windows Defender has a Firewall included, I would search for settings there. If you created an exception for RDP, you might need to add one for Guacamole as well?
 
Maybe I have to open a specific port on the machine that is running guacamole?

It it the same machine that is running Docker and portainer, and those I can reach just fine on different ports.
For example, portainer on the same machine I can reach on 192.168.68.131:9443
Guacamole is on http://192.168.68.131:8080/guacamole (But I am not sure how to add the /guacamole part to the firewall?)
 
Maybe I have to open a specific port on the machine that is running guacamole?

It it the same machine that is running Docker and portainer, and those I can reach just fine on different ports.
For example, portainer on the same machine I can reach on 192.168.68.131:9443
Guacamole is on http://192.168.68.131:8080/guacamole (But I am not sure how to add the /guacamole part to the firewall?)

You wouldn't need to add the /guacamole part to the firewall, this is handled by a different part.

Just to be 100% sure, cause I am a bit confused on what exactly we want to achieve in the end. You want to connect from Windows -> Guacamole or the other way around (Guacamole -> Windows)? What would be the end goal.
 
You wouldn't need to add the /guacamole part to the firewall, this is handled by a different part.

Just to be 100% sure, cause I am a bit confused on what exactly we want to achieve in the end. You want to connect from Windows -> Guacamole or the other way around (Guacamole -> Windows)? What would be the end goal.

My end goal is to connect from guacamole to the windows VM.

At the moment I am able to connect to that same windows VM using RDP on my laptop, but guacamole doesnt seem to want to connect to it at all.
My goal is to first be able to connect to it from guacamole, and then also set up so that I can reach the ubuntu machine from guacamole as well.
 
Okay, then I would look into the Windows VM if there the Firewall is set up. Then you would probably need to add an exception, so you can connect. You said you did this already for RDP, if I understand correctly.
 
Can you also run netstat -ab on the Windows machine in order to confirm that the port you are trying to reach is actually open there?
 
Okay, then I would look into the Windows VM if there the Firewall is set up. Then you would probably need to add an exception, so you can connect. You said you did this already for RDP, if I understand correctly.

Yes I added an exception for port 4191 RDP. But I also tried to add port 8080 for Guacamole, and its still not letting me in.
Is there any other port I need to add for guacamole to work?

Also I added the windows machine to DMZ in the router, so that I am sure its not blocking anything.
 
Yes I added an exception for port 4191 RDP. But I also tried to add port 8080 for Guacamole, and its still not letting me in.
Is there any other port I need to add for guacamole to work?

Also I added the windows machine to DMZ in the router, so that I am sure its not blocking anything.
Guacamole is running on port 8080 on your Linux machine, so you don't need to add an exception for that in the windows machine. Which port on the windows machine are you trying to reach. In order words, which process is listening on the Windows machine for your incoming connection?
 
Guacamole is running on port 8080 on your Linux machine, so you don't need to add an exception for that in the windows machine. Which port on the windows machine are you trying to reach. In order words, which process is listening on the Windows machine for your incoming connection?

Port 4191, that is what I use from the RDP app, and that is what I am trying to use from guacamole as well.

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 Win_11:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:445 Win_11:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:4191 Win_11:0 LISTENING
TermService
[svchost.exe]
TCP 0.0.0.0:5040 Win_11:0 LISTENING
CDPSvc
[svchost.exe]
TCP 0.0.0.0:7680 Win_11:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49664 Win_11:0 LISTENING
[lsass.exe]
TCP 0.0.0.0:49665 Win_11:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49666 Win_11:0 LISTENING
Schedule
[svchost.exe]
TCP 0.0.0.0:49667 Win_11:0 LISTENING
EventLog
[svchost.exe]
TCP 0.0.0.0:49668 Win_11:0 LISTENING
SessionEnv
[svchost.exe]
TCP 0.0.0.0:49669 Win_11:0 LISTENING
[spoolsv.exe]
TCP 0.0.0.0:49670 Win_11:0 LISTENING
Can not obtain ownership information
TCP 192.168.68.15:139 Win_11:0 LISTENING
Can not obtain ownership information
TCP 192.168.68.15:4191 RT-AX56U-49E8:59367 ESTABLISHED
TermService
[svchost.exe]
TCP 192.168.68.15:49971 20.54.37.64:https ESTABLISHED
WpnService
[svchost.exe]
TCP 192.168.68.15:51045 152.199.19.161:https LAST_ACK
[SearchHost.exe]
TCP 192.168.68.15:51054 20.103.253.93:http ESTABLISHED
DsmSvc
[svchost.exe]
TCP 192.168.68.15:51056 a2-22-1-123:http TIME_WAIT
TCP 192.168.68.15:51057 a2-22-1-123:http TIME_WAIT
TCP 192.168.68.15:51058 a-0001:https ESTABLISHED
[SearchHost.exe]
TCP 192.168.68.15:51059 a2-21-97-41:https ESTABLISHED
[SearchHost.exe]
TCP 192.168.68.15:51060 13.107.246.254:https ESTABLISHED
[SearchHost.exe]
TCP 192.168.68.15:51061 204.79.197.222:https ESTABLISHED
[SearchHost.exe]
TCP [::]:135 Win_11:0 LISTENING
RpcSs
[svchost.exe]
TCP [::]:445 Win_11:0 LISTENING
Can not obtain ownership information
TCP [::]:4191 Win_11:0 LISTENING
TermService
[svchost.exe]
TCP [::]:7680 Win_11:0 LISTENING
Can not obtain ownership information
TCP [::]:49664 Win_11:0 LISTENING
[lsass.exe]
TCP [::]:49665 Win_11:0 LISTENING
Can not obtain ownership information
TCP [::]:49666 Win_11:0 LISTENING
Schedule
[svchost.exe]
TCP [::]:49667 Win_11:0 LISTENING
EventLog
[svchost.exe]
TCP [::]:49668 Win_11:0 LISTENING
SessionEnv
[svchost.exe]
TCP [::]:49669 Win_11:0 LISTENING
[spoolsv.exe]
TCP [::]:49670 Win_11:0 LISTENING
Can not obtain ownership information
UDP 0.0.0.0:4191 *:*
TermService
[svchost.exe]
UDP 0.0.0.0:5050 *:*
CDPSvc
[svchost.exe]
UDP 0.0.0.0:5353 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:5355 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:60165 *:*
Dnscache
[svchost.exe]
UDP 0.0.0.0:65429 *:*
Dnscache
[svchost.exe]
UDP 127.0.0.1:1900 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:59130 *:*
SSDPSRV
[svchost.exe]
UDP 127.0.0.1:61499 127.0.0.1:61499
iphlpsvc
[svchost.exe]
UDP 192.168.68.15:137 *:*
Can not obtain ownership information
UDP 192.168.68.15:138 *:*
Can not obtain ownership information
UDP 192.168.68.15:1900 *:*
SSDPSRV
[svchost.exe]
UDP 192.168.68.15:59129 *:*
SSDPSRV
[svchost.exe]
UDP [::]:4191 *:*
TermService
[svchost.exe]
UDP [::]:60165 *:*
Dnscache
[svchost.exe]
UDP [::]:65429 *:*
Dnscache
[svchost.exe]
UDP [::1]:1900 *:*
SSDPSRV
[svchost.exe]
UDP [::1]:59128 *:*
SSDPSRV
[svchost.exe]
 
Apparently Windows RDP and Guacamole don't seem to work well together, there are some workarounds though apparently, maybe this works? https://www.mogilowski.net/2020/03/24/windows-10-server-2016-rdp-work-with-guacamole/

Thanks, that didnt help either.
Could the problem be the network that was created for the guacamole server?
According to the guide I had to create a new network inside docker. And also I am unable to ping anything at all from that docker/guacamole machine, so I have a feeling thats where the problem is somehow?
 
Thanks, that didnt help either.
Could the problem be the network that was created for the guacamole server?
According to the guide I had to create a new network inside docker. And also I am unable to ping anything at all from that docker/guacamole machine, so I have a feeling thats where the problem is somehow?
can you run docker network inspect <NETWORK_NAME> where <NETWORK_NAME> is the name of your created network?
As well as docker inspect <GUACAMOLE_CONTAINER>, where <GUACAMOLE_CONTAINER> is the name or id of your container running guacamol?
 
Guaca can be hard to setup at first, but after you got the option you are good to go fast. Forget prox and especially docker stuff. Just plug usb live iso, install xubuntu over an usb drive. Then on this pc set guaca and have it run. Then check on docker . portainer by itself is another set of time wasting problem to add on top. Start at first and guaca forum is nice for all the setup and config.