[RESOLVED] Client workstation unreachable on VLAN

[jcurnill]

Hello,
our firewall, which manages the different VLANs, is a pfSense. Only the workstations on the VLAN where the WAPT server is installed are reachable. The others are disconnected. The client installs correctly, no problem, the workstation appears correctly on the server's interface, but nothing works. Even with DNS, I've allowed the server's IP address on all interfaces using both TCP and UDP. Do you have any advice (port number to open?)?
Sincerely

[dcardon]

WAPT version, etc. (see forum rules)?
As mentioned in the documentation, the WAPT client only uses port 443 to connect to the server, and then creates a WebSocket on port 443 as well. The server doesn't need to see the client machines. We need to check why the WebSocket isn't mounting.
Regards,
Denis

[jcurnill]

Hello,
thank you for your reply. Our server is running Windows Server 2019, WAPT version 2.2.3.12481. How can I determine the source of the WebSocket error? Regards

[sfonteneau]

Do you have HTTPS certificate verification enabled?

[jcurnill]

Hello,
how do I activate this verification?
Installing the client is no problem; I can access the WAPT Enterprise console from my workstation on the administrative VLAN, even though the server is on the pedagogical VLAN. But nothing works; workstations outside the pedagogical VLAN are disconnected.
Thanks in advance.

[dcardon]

Good morning,

If you launch the agent in debug mode, do you get more explicit messages?

In a command prompt with high rights:

Code: Select all

cd c:\program files (x86)\wapt\
runwaptservice.bat -l debug

You should have this if everything goes well:

Code: Select all

2023-01-17 14:21:00,817 [wapttasks SocketIOClient 14556] INFO Connecting Socketio to https://srvwapt.mydomain.lan:443
2023-01-17 14:21:00,818 [waptws SocketIOClient 14556] INFO Attempting WebSocket connection to wss://srvwapt.mydomain.lan:443/socket.io/?transport=websocket&EIO=3
2023-01-17 14:21:00,837 [waptws SocketIOClient 14556] INFO WebSocket connection accepted with {'sid': '3b85cbfe59844c649e30d9ac3b901fae', 'upgrades': [], 'pingTimeout': 60000, 'pingInterval': 25000}
2023-01-17 14:21:00,838 [waptws SocketIOClient 14556] INFO Engine.IO connection established
2023-01-17 14:21:00,842 [waptws Thread-3 5324] INFO Sending packet PING data None
2023-01-17 14:21:00,844 [wapttasks SocketIOClient 14556] INFO WS read loop for 120s
2023-01-17 14:21:00,844 [waptws Thread-5 8772] INFO Received packet MESSAGE data 0
2023-01-17 14:21:00,850 [waptws Thread-6 12212] INFO Namespace / is connected
2023-01-17 14:21:00,851 [waptws Thread-5 8772] INFO Received packet PONG data None

Let's see what error message you get at that point.

Sincerely,

Denis

[jcurnill]

Hello, after multiple attempts it finally worked. Probably a problem between my PC firewall and my pfSense. Thank you for your help.

[dcardon]

Thank you for your feedback, I'm marking the topic as resolved.
Regards,
Denis