Technical Tip: Windows Dissolvable Agent Fails to Locate Server on Machines with Multiple Domains
Description
This article describes that Windows Dissolvable Agent Fails to Locate Server on Machines with Multiple Domains.
Scope
FortiNAC.
Solution
DATE: 03.22.2016
VERSION: Windows Agent versions 3.5.6.6, 4.0.x and higher
If a machine attempting to run the Windows Dissolvable Agent has more than one Connection-specific DNS suffix name, the agent may insert the wrong domain in the DNS SRV request sent to Network Sentry. This will cause Network Sentry to fail to respond appropriately to the agent's DNS request, causing the agent to display the error "Failed to Locate Server."
The existence of multiple Connection-specific DNS suffix names can be viewed by typing "ipconfig /all" in the Windows cmd on the endstation.
WORKAROUND:
Disable the endstation adapter(s) listing the different suffixes that are not used to connect to isolation, then re-run the agent.
Or
When prompted, enter the name of the Network Sentry Application Server or Network Sentry Server to proceed.
Or
Change the Endpoint Compliance Policy to distribute an agent version lower than 3.5.6.6.
Solution: This issue is fixed in Agent versions 3.5.8.12 and 4.0.3.38.
VERSION: Windows Agent versions 3.5.6.6, 4.0.x and higher
If a machine attempting to run the Windows Dissolvable Agent has more than one Connection-specific DNS suffix name, the agent may insert the wrong domain in the DNS SRV request sent to Network Sentry. This will cause Network Sentry to fail to respond appropriately to the agent's DNS request, causing the agent to display the error "Failed to Locate Server."
The existence of multiple Connection-specific DNS suffix names can be viewed by typing "ipconfig /all" in the Windows cmd on the endstation.
WORKAROUND:
Disable the endstation adapter(s) listing the different suffixes that are not used to connect to isolation, then re-run the agent.
Or
When prompted, enter the name of the Network Sentry Application Server or Network Sentry Server to proceed.
Or
Change the Endpoint Compliance Policy to distribute an agent version lower than 3.5.6.6.
Solution: This issue is fixed in Agent versions 3.5.8.12 and 4.0.3.38.
