I've seen similar results when trying to ping a distant end that has
allot of delay. The TTL used for ping on an NT is different than the TTL
used for traceroute. A traceroute is successful but the ping fails, or the
ping works on a Unix but not a Windows platform. Some times adjusting the
TTL will allow the ping to work. There seems to be allot of latency in the
traceroute provided below.
Shawn
----- Original Message -----
From: "NRF"
To:
Sent: Monday, May 28, 2001 6:26 PM
Subject: With a dialup setup, I can trace, but not ping, why's that?
[7:6177]
> I got this weird situation here:
>
> I got router A that dials into router B through an analog modem (async
> lines). On both routers A and B, I am using dialer profiles with
> rotary-groups. B is also connected to the Internet, through E0 (to a
cable
> modem), and I have properly set up NAT, so that E0 is the outside
interface
> and the dialer interface is the inside interface.
>
> A can properly dial into B with no problem. A has a static route pointing
> to its dialer interface. A does not have any other routes (all other
> interfaces have been shut, etc.) So basically, A has to dial to B to get
> anywhere. I have verified that dialing does indeed work properly.
>
> A cannot ping the outside world. For example, if I ping www.yahoo.com I
get
> nothing. But here's the really weird part. Apparently, A can trace to
> www.yahoo.com, with no problem. I should also state that my dialer-list
is
> this:
>
> dialer-list 1 protocol ip permit
>
> So, does anybody know why I can trace, but not ping? Is there something
> about Async interfaces or Dialer interfaces that causes thing weird
behavior
> to happen?
>
>
>
> Check out this output:
>
> r1#trace www.yahoo.com
> Translating "www.yahoo.com"...domain server (128.32.136.12) [OK]
>
> Type escape sequence to abort.
> Tracing the route to www.yahoo.akadns.net (204.71.200.67)
>
> 1 50.50.50.50 40 msec 36 msec 36 msec
> 2 24.250.141.1 52 msec 48 msec 48 msec
> 3 r1-ge-3-0.pinol1.sfba.home.net (24.9.239.225) 52 msec 48 msec 52 msec
> 4 r1-dpt-srp-5-0.oakland1.sfba.home.net (216.197.144.148) 52 msec 52
msec
> 48 m
> sec
> 5 bb1-dpt-srp-1-0.rdc1.sfba.home.net (216.197.144.129) 56 msec 52 msec
53
> msec
>
> 6 c2-pos5-1.snjsca1.home.net (24.7.76.181) 52 msec 52 msec 52 msec
> 7 pos6-3.core1.SanJose1.Level3.net (209.245.146.129) 64 msec 56 msec 52
> msec
> 8 gigaethernet6-0.ipcolo1.SanJose1.Level3.net (209.244.13.42) 56 msec 56
> msec
> 52 msec
> 9 POS11-0.ipcolo3.SanJose1.Level3.net (209.244.13.58) 52 msec 53 msec 52
> msec
> 10 cust-int.level3.net (64.152.69.18) 56 msec 56 msec 56 msec
> 11 ge-1-2-0.msr2.pao.yahoo.com (216.115.100.154) 60 msec 52 msec 52 msec
> 12 vl21.bas2.snv.yahoo.com (216.115.100.229) 53 msec 56 msec 56 msec
> 13 www.yahoo.akadns.net (204.71.200.67) 52 msec 56 msec 52 msec
> r1#ping 204.71.200.67
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 204.71.200.67, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> r1#
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=6726&t=6726
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
