1. This problem can occur if Client Agent is not able to download the build from Admin Console Site as Admin Console Site is not accessible from the remote system. This problem mostly occurs in case of domain based network and improper DNS configuration.
2. URL or port is blocked in Firewall.
3. Insufficient free disk space on remote system.
4. Agent Server service is not started on the Admin Console Server.
5. This may happen in case internet connection is configured using Proxy Server.
6. If incorrect subnet mask is configured on the remote system.

At first, check the System on which Admin Console Server is installed is getting 'ping' from remote system. Give the ping command as follows:

(If Admin Console site has been configured on IP Address)
ping < IP address of Admin Server>
E.g. ping 192.168.100.34

(If Admin Console site has been configured on Domain Name)
ping < domain name of Admin Server >
E.g. ping quickheal.admin.com

As in case of Domain based network, if the Admin Console Site is configured on Domain Name and DNS is not properly configured then remote system will not be able to ping the Admin Server system. To solve this problem, Administrator needs to configure proper DNS settings on the remote system.

We recommend you to configure Admin Site on the IP Address rather to configure it on the domain name.

Secondly, check Installer logs by going in Client Reports and clicking on View Installer logs . This will also give you clear information about why Quick Heal is not getting installed on the remote system.

If any Firewall is running then check if the URL or Port through which the build is getting downloaded is blocked.

Make sufficient disk space on the Remote System to download and install AntiVirus if installer log shows installation failed due to insufficient disk space.

Verify if the Agent Server Service is started on Admin Console Server.

1. Click on Start -> Run.
2. Type Services.msc.
3. Click on Ok.
4. In Services check the Agent Server Service status is Started.

If Internet Connection is configured using Proxy Server, it may not be able to resolve the name or IP of the Admin Console Server. In this case bypass the Proxy Settings for the Admin Console Site.

Subnet Mask of the Remote System should be as per the IP class assigned to the Admin Console Server system.

This problem occurs when Client Agent is not able to connect to Agent Server OR Agent Server is not able to connect to Client Agent

First check, if both the systems i.e. Admin Console Server and Remote System are able to communicate with each other on the configured port. To check this follow the below given steps

Verify if the Agent Server Service is started on Admin Console Server.

1. Click on Start -> Run.
2. Type Services.msc.
3. Click on Ok.
4. In Services check the Agent Server Service status is Started.

Verify if the Client Agent Service is started on Remote System.

1. Click on Start -> Run.
2. Type Services.msc.
3. Click on Ok.
4. In Services check the Client Agent Service status is Started.

Telnet < IP Address of Admin Console Server > < Agent Server Port >

Suppose IP address of Admin Server is 192.168.100.34 and 5036 is the port on which Agent Server is listening. Then execute the following command on remote system.

E.g. Telnet 192.168.100.34 5036

If you receive any response from Agent Server, then check whether Agent Server is able to communicate with Client Agent.

Telnet < IP address of Remote System > < Client Agent Port >

Suppose IP address of the remote system is 192.168.100.66 and 62107 is the port on which Client Agent is listening. Then execute the following command on Admin Server.

E.g. Telnet 192.168.100.66 62107

Please check if any Firewall service is installed on the system, If YES then that firewall can block the communication between Agent Server and Client Agent.

When proxy setting has been configured in Internet Explorer then it tries to resolve the Admin Console Site via Proxy Server and if Proxy Server is not able to resolve it then site does not get open.

In such case, check Proxy Server configuration of remote system. Proxy Server should be able to resolve the IP address or domain name on which Admin Console Site is configured. Or follow the below given steps to bypass Proxy Server while opening Admin Console Site:

1. Open Internet Explorer.
2. Go to Tools > Internet Options > Connection Tab > Click on LAN Settings.
3. Click on Advance Button.
4. In the Exceptions section type the address of Admin Console Web Site along with Port number.
5. Click on Ok.

1. Firewall is blocking the Update Manager Application.
2. Firewall is blocking the Quick Heal URL.
3. Firewall is blocking the extensions like .bin or .dat.
4. Update Manager Connection is configured through Proxy Server.

1. Check Firewall settings and allow Update Manager , Quick Heal URL and extensions like .bin or .dat if they are blocked.
2. Clear the cache of the Proxy Server

1. Web Server Service is not running.
2. Admin Console Site or its port is blocked by firewall.
3. Request is going through Proxy Server but the Proxy Server is not able to resolve.

This problem mostly caused if the Web Server Service is not running.

If Admin Console Server is configured using IIS Server then check the IIS Admin Service is running. And also check whether Admin Console Web Site is running in IIS .

If Admin Console Server is configured using Apache HTTP Server then check the Apache Service is running.

1. Click on Start > Run.
2. Type Services.msc.
3. Click on Ok.
4. In Services check the Apache2 Service status is Started.

Secondly, there can be a UTM (Unified Threat Management) device in the network, which may block the port. If it is, then open the port of the Admin Console Server.