Tracert results oddity

When i do tracert from any of my internal vlans to the internal dns servers i the results are like the below which is normal.

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms <1 ms <1 ms server.domain.com [192.168.0.10]

I have one network that returns results like this

1 4 ms 3ms. 8ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

Trace complete.

Why is this happening?

Comments

  • One possible reason is that Pings are being denied from the source IP addr.

  • james.carsonjames.carson Moderator, WatchGuard Representative

    If the server is set not to reply to ping/tracert from external networks, it may not reply. If it's a windows server and you don't recall setting that up, check any group policy templates that might have been applied. Some of the default ones will tell servers and workstations to not reply to pings from distant networks.

    -James Carson
    WatchGuard Customer Support

  • edited September 30

    @Bruce_Briggs This ended up being the cause. Thanks

Sign In to comment.