Please check if any Firewall service is installed on the system. Suppose IP address of the remote system is 192.168.100.8 is the port on which the Client Agent is listening, then execute the following command on Endpoint Security Server.
If you receive any response from the Agent Server, check whether the Agent Server is able to communicate with the Client Agent. Then execute the following command on remote system. is the port on which Agent Server is listening. Suppose IP address of Endpoint Security Server is 192.168.100.
Ensure there is sufficient disk space on the Remote System to download and install Seqrite Endpoint Security, if the installer log shows installation failed due to insufficient disk space.If any Firewall is running, check whether the URL or Port through which the build is getting downloaded is blocked.Check the Installer logs (Go to Client > Client Settings > View Status > View Installer logs).Here, you will get the exact reason about why Seqrite is not getting installed on the remote system.We recommend you to configure Endpoint Security Site on the IP Address rather to configure it on the domain name.To solve this problem, Administrator needs to configure proper DNS settings on the remote system. In case of Domain-based network, if the Endpoint Security site is configured on Domain Name and DNS is not properly configured, the remote system will not be able to ping the Endpoint Security Server system.If the Endpoint Security site has been configured on Domain Name.If the Endpoint Security site has been configured on IP Address.Give the ping command in the following way: Check the system on which the Endpoint Security server is installed whether it is getting 'ping' from the remote system.You can resolve this problem in any of the following ways: Incorrect subnet mask is configured on the remote system.Internet connection is configured using Proxy Server.The Agent Server service is not started on the Endpoint Security server.
Insufficient free disk space on remote system.
This problem generally may occur in case of domain-based network and improper DNS configuration.