for the purpose of this post, we are going to work with IP 10.0.0.2
In Windows open a Command Prompt and type the command to ping like this:
- Code: Select all
ping 10.0.0.2
You should receive the follwoing output:
- Code: Select all
Pinging 10.0.0.2 with 32 bytes of data:
Reply from 10.0.0.2: bytes=32 time=50ms TTL=63
Reply from 10.0.0.2: bytes=32 time=49ms TTL=63
Reply from 10.0.0.2: bytes=32 time=53ms TTL=63
Reply from 10.0.0.2: bytes=32 time=48ms TTL=63
Ping statistics for 10.0.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 53ms, Average = 50ms
If you receive output like this, you can't reach the IP or the firewall on the IP is blocking your ping:
- Code: Select all
Pinging 10.0.0.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
The Next test you can do is to trace a route to the Ip to see where it gets stuck, if your ping is not working.
In the Windows command prompt type the following command to trace route:
- Code: Select all
tracert -d 10.0.0.2
You should receive output like this:
- Code: Select all
Tracing route to 10.0.0.2 over a maximum of 30 hops
1 <1 ms <1 ms 6 ms 192.168.15.120
2 * * * Request timed out.
3 50 ms 51 ms 51 ms 10.0.0.2
Trace complete.
The entries with the "*" means it is taking long to figure out if the connection is going through.
The last entry is showing that the traffic got tot he finial IP.
If you get output like this, the traffic is not getting to the destination IP:
- Code: Select all
Tracing route to 10.0.0.2 over a maximum of 30 hops
1 <1 ms <1 ms 6 ms 192.168.15.120
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
.....
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.