Home › Knowledgebase › KB-972

How to fix a 'Destination Host Unreachable' error when pinging devices on your Brisbane office network

Summary

This guide helps you troubleshoot and resolve: How to fix a 'Destination Host Unreachable' error when pinging devices on your Brisbane office network. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

A "Destination Host Unreachable" error means your computer can reach your local router, but it cannot find the specific device you are trying to contact on your Brisbane office network. This usually indicates a configuration issue on the target device, a physical connection problem, or a local firewall blocking the request.

Quick Fix Steps

  1. Verify the target device is powered on and connected to the network.
  2. Check that the Ethernet cable is securely plugged in or that the device is connected to the correct Wi-Fi network.
  3. Restart both your computer and the target device.
  4. Ensure both devices are on the same network subnet (e.g., both starting with 192.168.1.x).

Detailed Instructions

1. Check Physical Connections

For wired devices, ensure the network cable is firmly seated in both the computer and the wall socket or switch. Look for activity lights on the network port. Common small business setups in Brisbane offices often use Cisco, Netgear, or D-Link switches; ensure the port on the switch is active. For wireless devices, confirm they are connected to your office SSID and not a guest network.

2. Check for IP Address Conflicts

An IP address conflict occurs when two devices on the same network are assigned the same IP address, which can cause "Destination Host Unreachable" errors.

  1. Check the IP address of your computer and the target device.
  2. If both devices share the exact same IP address, one device must be reconfigured.
  3. On the target device, switch the network adapter from a static IP to Obtain an IP address automatically (DHCP) to allow your router to assign a unique address.
  4. Restart the target device to apply the new DHCP lease.

3. Verify IP Address Settings

Devices on the same local network must share the same IP address range to communicate.

  1. On Windows, open Settings, go to Network & internet, and select Properties for your active connection.
  2. On macOS, open System Settings, click Network, and select your active connection.
  3. Compare the IP address of your computer with the target device. They should share the first three segments (e.g., 192.168.1.10 and 192.168.1.15).

If you are unsure of the target device's IP address, check the device's network settings menu or print a network configuration page if it is a printer.

4. Test with the Ping Command

Use the command line to verify if the device is reachable.

  1. Press Windows Key + R, type cmd, and press Enter. On macOS, open Terminal.
  2. Type ping [IP address] (for example, ping 192.168.1.15) and press Enter.
  3. If you receive "Destination Host Unreachable," the issue is likely with the target device or a local firewall.

5. Flush the ARP Cache

If your computer has a stale ARP (Address Resolution Protocol) entry, it may be trying to contact the target device using an old or incorrect MAC address.

  1. On Windows, press Windows Key + R, type cmd, press Ctrl + Shift + Enter to open Command Prompt as Administrator.
  2. Type arp -d * and press Enter to clear the ARP cache.
  3. Attempt to ping the target device again.

6. Check Local Firewall Settings

Security Warning: Enabling File and Printer Sharing opens ports on your device that allow other computers on the network to access shared resources. Only enable this on trusted private office networks. Avoid enabling these settings on public Wi-Fi networks to prevent unauthorised access to your computer.

Many devices block incoming ping requests by default for security reasons.

  1. On the target Windows device, open Windows Security.
  2. Navigate to Firewall & network protection.
  3. Click Allow an app through firewall.
  4. Click Change settings and ensure File and Printer Sharing is enabled for Private networks.

7. Check Network Adapter Status

Ensure the network adapter on the target device is enabled and not disabled.

  1. On Windows, right-click the Start button, select Device Manager, expand Network adapters, and ensure the adapter is not showing as disabled.
  2. On macOS, open System Settings, click Network, and ensure the connection shows as active.

8. Check Static vs DHCP IP Assignment

Verify whether the target device is using a static IP address or obtaining one automatically via DHCP. If using a static IP, ensure it falls within the same subnet as your computer and does not conflict with other devices.

9. Check for Wireless Client Isolation

If the target device is connected via Wi-Fi, your office router may have "Client Isolation" (sometimes called "AP Isolation") enabled. This feature prevents wireless devices from communicating with each other, even if they are on the same network.

  1. Log into your office router's administration panel (common brands include Cisco, Netgear, or D-Link).
  2. Navigate to the Wireless or Wi-Fi Settings section.
  3. Look for a setting named Client Isolation, AP Isolation, or Wireless Isolation.
  4. Ensure this setting is Disabled so that wireless devices can communicate with wired devices on the same subnet.

If you have followed these steps and still cannot reach the device, please Open a Ticket for further assistance.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket