1 of 1 people found this helpful
1. The Agent machine needs to have port 4155 open to listen for commands from the Protect server and the Protect server needs to have port 3121 open to receive the response back from the Agent.
- Test 4155 from the Protect server to the target agent machine. This is for agent commands to the target machine.
- Test 3121 from the target agent machine to the Protect server.
(you should note if you need to use NetBIOS, FQDN or IP to make this work)
- To test this you can use Telnet: Using Telnet to Test Ports
2. Ensure that DNS resolution is working correctly when contacting the Protect console system. From the client system run the following commands. The results should match up.
- nslookup consolemachinename
- nslookup consoleIPaddress
3. Is your Agent machine able to resolve the names in your Console Alias Editor. If needed update the Console Alias Editor by adding the IP Address, NetBIOS and FQDN. To do this in Protect go to Tools > Console Alias Editor and add the Alias needed. Then manually have your Agent check-in to update it. (do this from the target machine Agent UI or allow the Agent to check-in at it's normal time)
4. Is the time on your Agent Machine within 2 minutes of the time on the Console. If the times are not synced they will not communicate because of trust issues by not being able to verify the certificates.
Still not working for these users.
All options checked