FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Observe client and client monitor from the outside

Observe client and client monitor from the outside 16 Nov 2017 01:46 #2804

  • Maxim Chernyshev
  • Maxim Chernyshev's Avatar Topic Author
  • Offline
  • 1st level - White Belt
  • 1st level - White Belt
  • Posts: 2
  • Thank you received: 0
Hi,

I am trying to find a reliable solution to be able to use the Observe Client and Client Monitor features in our evaluation setup.

In this setup, we have got a FW server (Linux) hosted in the cloud, and FW admin GUI (OS X) running inside the corporate LAN.

In this LAN, we also have x2 clients enrolled - macOS and Win 10.

I am unable to use any of the Observe Client and Client Monitor features via the public external IP of the main border router and can only do client monitoring of the macOS client via Bonjour.

When I try to observe either client I am getting "Unable to observe client: invalid server state" error.



Are there any additional configuration steps required on each client to enable observing?

Is client monitoring supported externally via a cloud-based FW server?

Thanks!
Attachments:

Observe client and client monitor from the outside 16 Nov 2017 07:00 #2805

  • Ben Miles
  • Ben Miles's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 172
  • Karma: 8
  • Thank you received: 8
Are you hosting with FileWave or on your own?

Yes, observe/control is designed to work from outside to things outside, and it uses the FileWave server as a hub.
Check out filewave.com/kb/tcp

Note in the first illustration of the client connections, there is a client to server 20030 Observe Data, and an admin to server 20030.
Make sure that connection is working.

Also be sure the observe is enabled on your clients by making a Superprefs file.

The issue you are seeing with client monitor not working has to do with connected IP vs current IP.
Remember Device Details are stored inventory information, client monitor is a direct admin to client connection (see that tcp first illustration again)
Lets say you have a computer on an internal network (Ip 192.168.1.100) but your server is hosted and sees the client connection coming from the NAT IP (32.54.54.51).
When you select a client in admin, and choose client monitor, I'm guessing it is auto-filling that NAT address that the server sees the client coming from.
You will see the current IP in the client info window > device details. Entering that into the client monitor should allow you to connect to the client directly (given that you are on the same network as them, and that 20010 port is open between you and the client).
Ben Miles
FileWave (USA), Inc.
(fw)
Toll free: 1-888-filewave
  • Page:
  • 1