How to Ping Test your Printers

This is a guide for ping testing your machines while installing Echo. This quick and simple test will establish that the computer that is hosting Echo can reach the printers that you intend to monitor via your network.  
 
    1. Open a Command Prompt on the PC that is hosting the Echo client
      • Click on the Start Menu and in the search bar, type `cmd`, and press Enter.
      • OR press Windows Key + R to open the Run Prompt. Type 'cmd', then click OK (or press Enter)
    2. In the Command Prompt window, type `ping` followed by the destination, either an IP Address or a Domain Name, and press Enter.
      • For example, `ping 122.56.77.17`
      • For each printer you are validating,   `ping <IP Address of the target printer>`
    3. The command will then begin printing the results of the ping into the Command Prompt.
 
 
Passed Test

A normal reply looks like:

Reply from 122.56.77.17: bytes=32 time=15ms TTL=247

The ping command has received a response from the IP address, which took 15 milliseconds.

 

Failed Test

If the connection is down or the device you are pinging does not accept the ping, the ping command prints:

Request timed out.
 
Interpreting your results
 
If your Echo and Printers are all on the same network, each one should result in a normal reply in the Command prompt and will Pass their Ping test. If any of your target printers have a failed test, network connectivity between the Echo client and the target PC will need to be established before we can monitor that printer. Your IT team may be able to assist with this process and we are happy to advise as well. Please reach out to support@authentise.com if you need any help!
 

1 Comments

  • 0
    Avatar
    Lino Stavole

    So, this machine's IP address has been updated and no longer coincides with authentise. That makes me think other machines have been updated, too. I will review them and ensure they reflect the proper IP addresses.

    Just for your edification, the ping test was successful, and that made me think to go back and ensure that, even if that address is pingable, it is associated with the proper machine... it was not associated with any of our machines anymore. 😒

Please sign in to leave a comment.
Powered by Zendesk