Unable to update Windows Agent remotely

[manu]

Like it

Up

0

Down

Drop it

::

You are misunderstanding things here.
remote_config is an Enterprise feature, and it allows you to edit pandora_agent.conf remotely.

The network modules are completely a different thing. The reason why the ping is not running might be a misconfiguration you’re having checks these things:

1- The agent has an IP? Did you put an IP to the module when you added it?
2- The network server is running? (check it at Pandora Servers) in the menu

[tealnet]

Like it

Up

0

Down

Drop it

::

The agent has an IP address, an internal IP (192.168.1.10), which I have specified at the server. Does the agent need a public, or at least a publicly accessible, IP address since it is remote on a different network? The network server (as well as all the servers) on the pandora box are all running.

My situation is that I’d like the ability to monitor many different networks from a central location. I have Pandora installed on a public dedicated server. I’d like to install an Agent within all the remote networks I monitor and have all the data sent back to the main server. Ideally, I’d like to do this without having to open up ports on each network, but I can if I have to.

Thanks for your help!

[manu]

Like it

Up

0

Down

Drop it

::

Well, first of all, does the agent has an network server assigned to it?

Another thing, Pandora is not going to be able to ping a private IP (192.168.1.10) from a public IP, you might want to add network rules to be able to do that, does it make sense?

[raul]

Like it

Up

0

Down

Drop it

::

Check if you can ping from your Pandora Server to the internal IP, and depending on the protocol you’re using to send the data packages, that you can reach from the agent the open port on the server: SSH, 22/TCP; FTP, 21/TCP or tentacle, 41121/TCP