Tranquil IT Forum

Hello, I'm currently testing the WAPT solution with the intention of deploying it across my network of 500 machines and potentially upgrading to the paid version.

However, the tests are inconclusive. I have three remote machines running Windows 10 for testing and a 2012 R2 x64 server for administration. My PCs appear to be in OK mode with their correct IP addresses, but when I try to connect to them, for example, in disk management mode, I get the message: "

No IP address is available for this machine. Check the firewall, routes, etc."
I should mention that I've verified the firewall rule for the WAPT service is correct with the correct IP address.

Ping is successful, and the port is indeed the one for the WAPT service!

I don't understand where the problem lies. If anyone can help me move forward, I would be very grateful.

Cyril,
IT Asset Management

LSDH45 wrote: ↑January 2, 2020 - 5:13 PM My PCs are in OK mode, as seen with their correct IP addresses, but when I try to connect to them, for example in disk management, I get the message: "

No IP addresses are accessible for this machine. Check the firewall, routes, etc."
I should mention that I've checked the firewall rule for the Wapt service and it's correct with the correct IP address.

Ping is OK, and the port is indeed the one for the Wapt service!

I don't understand where the problem is. If anyone can help me move forward, I would be very grateful.

Good morning,

There seems to be a misunderstanding about how WAPT and native Windows remote administration tools work.

When the WAPT server "says it sees the IP" of a remote machine, it means that the machine initiated contact with the server and the two can then exchange information through a secure bidirectional websocket, so the WAPT agent basically uses the OUTGOING firewall rules of its machine.

When you try to use the native Windows remote administration tools (RDP, access to administrative shares, etc.), it's the console that initiates the connection, and this INCOMING connection will be blocked by the native Windows firewall, hence what you're observing; it's perfectly normal!

WAPT operates without any open listening ports on the remote machine. The tools you mentioned are provided to make things easier for you; it remains your responsibility to open the necessary ports in your machines' firewalls for these convenience tools to function correctly. A WAPT firewall rule package should resolve your issue.

A remote access mechanism similar to TeamViewer is on the 2020 roadmap for the Enterprise version if you prefer not to have to open a port in your Windows FW, which is the most recommended option.

Sincerely.

Vincent