Desktop Central Server Not Reachable!

Problem

You have problems in reaching the Desktop Central server or Distribution Server, and you run the "Agent Diagnostic Tool". You get an Error "Server Not Reachable!", during the process.

Cause

You will encounter this error due to one or more of the following reasons:

1. Desktop Central Server/Distribution Server has been Stopped
2. Desktop Central Server/Distribution Server has been configured with a new IP address
3. Desktop Central Server/Distribution Server has been migrated
4. Computer on which Desktop Central Server/Distribution Server has been installed has been shutdown
5. Ports blocked on the firewall of the Desktop Central Server/Distribution Server

Resolution

Follow the steps mentioned below to

You need to verify

Verify Connectivity to reach Desktop Central server

Follow the steps mentioned below to verify the connectivity from the agent to Desktop Central server or Distribution Server:

1. Open command prompt and type "tracert" followed by server's IP address. For Example : tracert 101.104.12.104
2. The TRACERT diagnostic utility determines the route taken to a destination by sending Internet Control Message Protocol (ICMP) echo packets with varying IP Time-To-Live (TTL) values to the destination.
   The TRACERT command can be used to determine where a packet stopped on the network. In the following example, the default gateway has determined that there is not a valid path for the host on 22.110.0.1.
   There is probably a router configuration problem or the 22.110.0.0 network does not exist (a bad IP address).
   Example:
   燙:>tracert 22.110.0.1?br> Tracing route to 22.110.0.1 over a maximum of 30 hops
   1 157.54.48.1 reports: Destination net unreachable. Trace complete.
3. Ping the server ip ( ip:port) using browser and see if it gets connected. If not, check the error it throws.
4. If you still can not reach the Desktop Central server, then verify the port numbers that needs to be open on the Desktop Central firewall.

In case you are not able to troubleshoot the error, and the problem still persists, then contact support team with the Log files.

Applies to: Asset Scan Locked, Software Inventory Tracking, Hardware Inventory Tracking, Asset Management, WMI Connection Failed

Keywords: Asset Scan Locked, Inventory Scan, Asset Scan, Manual Scanning, Scheduled Asset Scan, WMI Connection Failed