Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Force an Agent to be Classified Internal

Derek Lindridge

September 17, 2018 19:54

Is it possible to force a computer Agent to be classified as Internal? Maybe by setting the definition of internal IP address ranges somewhere?

As an example External agents now report their public IP addresses. Ok, I guess that makes some sense. But we have agents on the servers in the DMZ and while PDQ has full permission and ability to talk to those directly via firewall rules, it still classifies them as External and lists their public IP addresses and tries to connect to them via the public IPs (which of course it won't be able to).

Comments

2 comments

Official comment

Permanently deleted user
September 23, 2019 17:23

We are announcing the End of Life (EOL) of the optional PDQ Agent beta from our existing products. See this blog post for more information https://www.pdq.com/blog/pdq-agent-status-update/
Colby Bouma
September 17, 2018 20:15

Agents are considered Internal if they are able to talk to the Server over the port it's listening on, TCP 7337 by default. If they can't talk to the Server they will try to reach agentapi.pdq.com. If that works they will be External. If that doesn't work they will be Unavailable.

The Agent FAQ covers some of this in more detail: https://support.pdq.com/knowledge-base/875

0