Unreachable machines

[sidney_v]

Hello,

WAPT is in production (version 1.3.5) and suddenly almost all the machines have become UNREACHABLE from the administration console.

Symptoms:
* Unable to launch the update of available packages on the machine (ERROR The WAPT service is unreachable)
* Telnet on port 8088 of the machine does not work
* Access to http://127.0.0.1:8088/status works fine
* Updating the software inventory from the client works fine
* "Connect via VNC" works fine.

After updating to v1.3.8 and then verifying that name resolution was working correctly from both the server and the client machine running the console, I realized that the problem stemmed from the Windows firewall's inbound traffic rule.

Each computer has a "waptservice 8088" rule whose remote IP address is that of the WAPT server.

By allowing "Any IP address" or simply specifying the subnet mask after the IP address, it works again.

My question is: when is this rule created and how do I modify it for all computers (is it done from the console, by configuring the server and creating a new agent...)?

Thank you in advance for your answers.

[sfonteneau]

My question is: when is this rule created and how do I modify it for all computers (is this done from the console, by configuring the server and creating a new agent...)?

Thank you in advance for your answers.

The rule is created during installation. However, if the rule already exists, it will not be replaced.

But this kind of problem will be solved in the next version of WAPT because we're switching to using WebSockets, which will resolve quite a few issues

In your case, have you tried the "scan listening IPs" button?

[sidney_v]

Thanks for the reply, I'll wait then...

To avoid this problem on future deployments, do you have any idea where to modify the firewall settings that create this rule (allowing port 8088) to add the subnet mask?

Also, what is the approximate release date of this WebSocket-based version of WAPT?

Thanks in advance.