This article describes how to validate network connectivity between the Core and the agent or between two cores.
You can use several tests and procedures to validate network connectivity between the Core and agent or between two cores.
Perform a ping test to the target core using the following:
Perform this test from both the Cores and the agents, and you should be able to successfully ping the target core.
Multi-Homed Hosts
Communication with a multi-homed core or agent domain controller may fail intermittently. This issue occurs if one of the network adapters is attached to separate networks. In this scenario, network adapters on the Core or the agent are registering both (or all) IP addresses with the DNS server. DNS name resolution look-up requests return records in a “round robin” fashion, alternating the different IP addresses. When the Core or the agents look up DNS to communicate with each half of the DNS, look-up requests return an IP address that cannot be contacted, and the operation fails.
To fix this issue, do the following:
Name Resolution
Check both the DNS and Host files to ensure that the server names are resolved correctly. If Host files are used to resolve server names, then check the hosts file on the Core as well as the protected servers. Both methods of name resolution should point to the preferred NIC on the servers.
DNS name resolution can be tested using the command nslookup.
On 32-bit versions of Windows, the Hosts file is located in the following directory: %systemroot% \system32\drivers\etc.
On 64-bit versions of Windows, the Hosts file is located in the following directory: %systemroot% \SysWOW64\drivers\etc.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center