FortiNAC
NOTE: FortiNAC is now named FortiNAC-F. For post-9.4 articles, see FortiNAC-F. FortiNAC is a zero-trust network access solution that provides users with enhanced visibility into the Internet of Things (IoT) devices on their enterprise networks.
FortiKoala
Staff
Staff
Article Id 195212
Description
Persistent Agent 3.x and Above Unable to Communicate with Network Sentry

Scope
Version: Persistent Agent 3.x and above
Solution
Version: Persistent Agent 3.x and above.


Issue:  Persistent Agent unable to  communicate with Network Sentry while host is in production.

Successful Persistent Agent communication with Network Sentry requires the agent to know the name of the Network Sentry appliance it is trying to reach.  This information can be provided to the agent using one of two methods:
  • Through DNS from either Network Sentry (if in isolation) or the corporate DNS server (if in the production network).   
  • Through Registry key configurations via software push.

If using DNS, SRV records are required.  These SRV records help the agent locate Network Sentry and determine what ports to use.  The name contained in the SRV response is written to the host registry (Windows) or preferences (OS X, Linux). For details, refer to the section entitled "Agent Server Discovery Process" in the Network Sentry Agent Overview Guide.



Solution: 
SRV records already exist in Network Sentry.  However, they will need to be added to the production DNS server.  For details on SRV record configuration, see section "DNS Server Configuration" in the Network Sentry Agent Overview Guide.

If configuring keys via software, see the appropriate section in the Overview Guide:
"Configure the Persistent Agent on Windows Hosts"
"Configure the Persistent Agent on Mac OS X Hosts"




Contributors