Target Computer Offline

You receive an error indicating the target computer cannot be accessed over the network. You might also receive an error the computer's ADMIN$ share cannot be found.

In certain cases, you might receive this error if Wake-on-LAN has been initiated on a target computer during a deployment and the target computer is offline and the target is not in PDQ Inventory. 

For the first error, the most common causes are:

  • The computer is turned off
  • A firewall is blocking access to the ADMIN$ share
  • The ADMIN$ share is disabled
  • File & Printer sharing is turned off

Test connectivity to the computer via other tools, such as Windows Explorer, to determine the root cause of the failure, including accessing \\Target\ADMIN$.

In the case of a Wake-on-LAN error described above, PDQ Deploy is unable wake up the target computer because it doesn't know the MAC address since the machine does not exist in PDQ Inventory. WoL isn't even attempted in this case. To resolve this, scan the machine in PDQ Inventory then attempt to redeploy the package. 

See Also:
Can't Access ADMIN$ Share Using A Local User Account
Firewall Ports and Exceptions
Using WOL from PDQ Inventory

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0

    why do some PC.s show red in the oline column and some show green. what is the difference

  • 0

    The online/offline status is based on a ping (ICMP echo).  If the computer doesn't respond to the ping it will show red, green if it does.  They can also be red if there is a name resolution problem, so that a ping can't be sent.

  • 0

    I just wanted to add here that one issue I came up with was my add-on network card did not have the 'file and printer sharing' checkbox checked.

    This can be found here:

    Control Panel>Network and Internet>Network Connections - Right Click the NIC you are targeting, and choose Properties.

  • 0

    Another situation I've encountered related to this is that the target IP address (on a DHCP assigned computer) will not get updated in PDQ Inventory.  Since the program is still trying to connect using the old IP address, the connection will fail, even though the target computer is online.  I haven't found an "easy" fix for this yet, but I've had success either re-registering the target computer in DNS and then waiting a while or (if the computer is a clean image) renaming the computer and rediscovering it in inventory.

Article is closed for comments.
Powered by Zendesk