Difference between revisions of "Ping on Mac OS"
(importing article from wikihow) |
m (Text replacement - "<br><br>" to "") |
||
| Line 9: | Line 9: | ||
#* To view a full explanation of the command and all the available arguments, type in {{kbd|man ping}} and press {{keypress|Enter}}. | #* To view a full explanation of the command and all the available arguments, type in {{kbd|man ping}} and press {{keypress|Enter}}. | ||
#Read the output. After sending the ping command, you will see a readout with all the data related to the pin. Interpreting this data can help troubleshoot your network or a server problem. | #Read the output. After sending the ping command, you will see a readout with all the data related to the pin. Interpreting this data can help troubleshoot your network or a server problem. | ||
| − | #* The first line of output describes what the Ping utility is going to do. It will display the address you are pinging along with the size of the data packet you will be sending. For example: | + | #* The first line of output describes what the Ping utility is going to do. It will display the address you are pinging along with the size of the data packet you will be sending. For example: '''ping example.com<br>PING example.com (192.0.32.10): 56 data bytes''' |
| − | #* The ensuing lines of display the results of the ping and any communication received back from the server. This includes the amount of data returned, the amount of times until the packet expired (ttl), and the amount of time that the ping response took, in milliseconds (ms). For example: | + | #* The ensuing lines of display the results of the ping and any communication received back from the server. This includes the amount of data returned, the amount of times until the packet expired (ttl), and the amount of time that the ping response took, in milliseconds (ms). For example: '''64 bytes from 192.0.32.10: icmp_seq=0 ttl=240 time=98.767 ms<br>64 bytes from 192.0.32.10: icmp_seq=1 ttl=240 time=96.521 ms<br>64 bytes from 192.0.32.10: icmp_seq=2 ttl=240 time=95.766 ms<br>64 bytes from 192.0.32.10: icmp_seq=3 ttl=240 time=95.638 ms<br>64 bytes from 192.0.32.10: icmp_seq=4 ttl=240 time=95.414 ms<br> 64 bytes from 192.0.32.10: icmp_seq=5 ttl=240 time=93.367 ms''' |
| − | #* The final lines of output summarize the results. The number of packets transmitted, received, and lost will be shown. Lost packets are indicative of a poorly configured network or bad signal. For example: | + | #* The final lines of output summarize the results. The number of packets transmitted, received, and lost will be shown. Lost packets are indicative of a poorly configured network or bad signal. For example: '''6 packets transmitted, 6 packets received, 0.0% packet loss <br>round-trip min/avg/max/stddev = 93.367/95.912/98.767/1.599 ms''' |
=== Troubleshooting If the Ping Fails === | === Troubleshooting If the Ping Fails === | ||
#Try another host name. If you receive the ping report {{samp|ping: cannot resolve example.com: Unknown host}}, it usually means that the you have misspelled the host name. Try another host name like “example.com”. If that reports “Unknown host,” then the problem is most likely the address of the domain name server. | #Try another host name. If you receive the ping report {{samp|ping: cannot resolve example.com: Unknown host}}, it usually means that the you have misspelled the host name. Try another host name like “example.com”. If that reports “Unknown host,” then the problem is most likely the address of the domain name server. | ||
