Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Can't trace route

I have two 3600 series routers I use for provisioning my DSL customers. I noticed something interesting today and was wondering if any one can explain it. I cannot trace route from either 3600 to a any user's IP, however I can trace from my workstation. The customers circuit works fine, I can ping from the router. Cisco 678 on customers end.

From workstation:

Trace ...

1 0ms 0ms 0ms TTL: 0 ( ok)

2 0ms 0ms 0ms TTL: 0 ( ok)

3 78ms 63ms 62ms TTL: 63 (No rDNS)

From router customer is connected to:


Type escape sequence to abort.

Tracing the route to

1 * * *

2 * * *

3 * * *

From core router:


Type escape sequence to abort.

Tracing the route to

1 c3640 ( 0 msec 4 msec 0 msec

2 * * *

3 * * *

Thank you,


New Member

Re: Can't trace route

This is normal behavior ......

from 7206 you can get a reply from 3640 first hop to destination but when u send it to workstation IP their stack is not supporting trace reply.

Hope this make sense !


New Member

Re: Can't trace route

So you are saying the Cisco 678 on the users end will not reply? Why then does it reply when I send a trace from my workstation? I am going through the same path:

Trace ...

1 15ms 0ms 0ms TTL: 0 ( ok)

2 0ms 0ms 0ms TTL: 0 ( ok)

3 62ms 62ms 63ms TTL: 63 (No rDNS)


New Member

Re: Can't trace route

the setup i understand is




7206------3640------678------wks ....

is this is the setup make sure through sh ip int xx commads that the icmp unreachiable is enable on the interface ,


New Member

Re: Can't trace route

Setup is


so from wks to 678 no problem, from 7206 or

VA config:

C3640#sh ip int virtual-access 25

Virtual-Access25 is up, line protocol is down

Interface is unnumbered. Using address of FastEthernet3/0 (

Broadcast address is

MTU is 1500 bytes

Helper address is not set

Directed broadcast forwarding is disabled

Multicast reserved groups joined:

Outgoing access list is not set

Inbound access list is not set

Proxy ARP is enabled

Security level is default

Split horizon is enabled

ICMP redirects are always sent

ICMP unreachables are always sent

ICMP mask replies are never sent

IP fast switching is enabled

IP fast switching on the same interface is enabled

IP Flow switching is disabled

IP Feature Fast switching turbo vector

IP multicast fast switching is enabled

IP multicast distributed fast switching is disabled

IP route-cache flags are Fast

Router Discovery is disabled

IP output packet accounting is disabled

IP access violation accounting is disabled

TCP/IP header compression is disabled

RTP/IP header compression is disabled

Probe proxy name replies are disabled

Policy routing is disabled

Network address translation is disabled

WCCP Redirect outbound is disabled

WCCP Redirect inbound is disabled

WCCP Redirect exclude is disabled

BGP Policy Mapping is disabled

IP multicast multilayer switching is disabled


Re: Can't trace route

An obvious point here but just in case by some chance it was missed: you checked for any access-lists correct - As traceroute is different depending on the source:

Hope it helps (doubtful but you never know).


New Member

Re: Can't trace route

When you tracert, your source address is the interface that is the closest to the destination. A point to keep in mind for routing and for access lists.

CreatePlease login to create content