What are you pinging at the spoke ? If it's the router then it could be the same issue, are you running NAT at both ends ??
Depending on traffic load, do a 'debug ip packet' that'll show you. ""Richard Botham"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Hi Joely, > Thanks for that. > However: > 1 - I don't specify a source interface when pinging from the spoke to the > hub and this works > IP NAT detailed debugging is on > r4#ping 10.128.10.10 > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 10.128.10.10, timeout is 2 seconds: > !!!!! > Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/12 ms > r4# > 4d00h: NAT: o: icmp (10.128.10.4, 9525) -> (10.128.10.10, 9525) [191] > 4d00h: NAT: i: icmp (192.168.4.1, 9525) -> (10.128.10.4, 9525) [191] > 4d00h: NAT: o: icmp (10.128.10.4, 9526) -> (10.128.10.10, 9526) [192] > 4d00h: NAT: i: icmp (192.168.4.1, 9526) -> (10.128.10.4, 9526) [192] > 4d00h: NAT: o: icmp (10.128.10.4, 9527) -> (10.128.10.10, 9527) [193] > 4d00h: NAT: i: icmp (192.168.4.1, 9527) -> (10.128.10.4, 9527) [193] > 4d00h: NAT: o: icmp (10.128.10.4, 9528) -> (10.128.10.10, 9528) [194] > 4d00h: NAT: i: icmp (192.168.4.1, 9528) -> (10.128.10.4, 9528) [194] > 4d00h: NAT: o: icmp (10.128.10.4, 9529) -> (10.128.10.10, 9529) [195] > 4d00h: NAT: i: icmp (192.168.4.1, 9529) -> (10.128.10.4, 9529) [195] > > 2 - Whether or not I specify a source interface at r1 (hub) the pings never > succeed. > > Any more ideas ? > > Cheers > Richard Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33431&t=33424 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
