Appendix A Network Troubleshooting
If your ping test fails to get a response, then you may see a message like this:
C:\>ping www.example.com
Pinging www.example.com [192.0.32.10] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.0.32.10:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>
When a request times out it may mean:
•your computer is not connected to the network
•your Internet access device is not connected to the network
•or the device which you are pinging is not connected to the network
If you think the destination is active but responding slowly, you can try increasing the ping timeout value from its default of 4 seconds (4000 milliseconds) to something like 8 seconds (or 8000 milliseconds).
C:\>ping
Pinging www.example.com [192.0.32.10] with 32 bytes of data:
Reply from 192.0.32.10: bytes=32 time=157ms TTL=238
Reply from 192.0.32.10: bytes=32 time=154ms TTL=238
Reply from 192.0.32.10: bytes=32 time=152ms TTL=236
Reply from 192.0.32.10: bytes=32 time=162ms TTL=236
Ping statistics for 192.0.32.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in
Minimum = 152ms, Maximum = 162ms, Average = 156ms
C:\>
A long ping response could indicate network problems:
•on your side of the connection
•between the start and end points of the connection
•on the receiving end
To determine where the slowdown is, you may need to use traceroute.
406 |
| |
| ||
|
|
|