From: Raphael Gallegos (raphaeljg@xxxxxxxxxxx)
Date: Sat Feb 02 2002 - 19:35:07 GMT-3
Try modifying the extended access-list for the nat and deny the interface ip
subnet from being natted (Both ways on the access-list), my guess is that
the ping needs to reach the other side when pinging your own
interface(Without the no keepalive), and then changes source ip on you when
doing so.
Raphael
>From: "McCallum, Robert" <Robert.McCallum@let-it-be-thus.com>
>Reply-To: "McCallum, Robert" <Robert.McCallum@let-it-be-thus.com>
>To: "'Ccielab' (E-mail)" <ccielab@groupstudy.com>
>Subject: NAT problem
>Date: Sat, 2 Feb 2002 18:12:34 -0000
>
>I have came across a really strange problem with NAT.
>
>I have got a router configured with the inside source blah blah blah blah.
>You dont need to know this part!!
>
>When I ping the interface which should be getting Natted then it doesn't
>work. However, when I do a ping (press return) select ip and then type in
>the same ip address but selecting to record the path the damn thing works.
>WHY??
>
>As far as I was aware doing an extended ping but with the record path
>option was just the same as doing a bog standard ping but it tells you
>where it has went. The access list to permit the Natting incidently was
>just permit any so that couldn't be the problem.
>
>Anyone else seen this.??
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:10 GMT-3