cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1955
Views
0
Helpful
19
Replies

ASA doesn't route the packet

michelerossi
Level 1
Level 1

I have an ASA 5500 and it has a gateway of my Lan.

The asa rotates the packets destined to 2 remote nets toward a router cisco,through a chart of static routes.

The problem is that it only passes the ping toward the remote lan, while all the other protocols and sessions are blocked !!!!

Only ICMP packet are forwarding.

I have capture this message into the ASA log:

" 106015 192.168.10.14 192.168.13.13Deny TCP (no connection) from 192.168.10.14/21438 to 192.168.13.13/1720 flags RST on interface LAN.

Best Regards

19 Replies 19

Collin Clark
VIP Alumni
VIP Alumni

Can you post a diagram with IPs?

the attachments describe the network and Ip addresses assigned to the Cisco Routers and ASA.

Thanks

Michael

IP adresses in diagram and in you post do not match. Can you correct please?

Also please run

sh run access-group

access-group xxxx in interface inside

If you see a line like above, (xxxx is your acl name) please send the output of

sh run access-list xxxx

husycisco
Level 7
Level 7

If this was a routing issue, you would have the following log in syslog

No route to host 192.168.13.13

This looks like an ACL issue. Is 192.168.10.14 in your inside network (inside interface)? And where is 192.168.13.13 located? DMZ interface?

sorry

but this is the correct message:

106015 172.31.0.14 172.29.0.14 Deny TCP (no connection) from 172.31.0.14/21438 to 172.29.0.14/1720 flags RST on interface LAN.

My first message was correlate to another ASA Log message, where I've the same problem.

Thanks

So can you please post the output of following commands

sh run access-group

access-list xxxx in interface LAN

(xxxx is the name of your ACL)

sh run access-list xxxx

Sent the attachment.

 

 

 

 

Thanks. Please post the output of following also

packet-tracer input tcp LAN 172.31.0.14 21438 172.29.0.14 1720 detailed

See the attach

According to packet trace, ASA allows the flow, nothing wrong with ASA. And as I see RST statement in syslog, I suspect the remote client. Maybe restarting the client may work, do you encounter the same issue when you try to reach another client again in that subnet too?

I've got the same issue to reach all clients of all remote networks, include the Lan ip address routers.

The ASA version is 8.0.(2).

If I do a traceroute from ASDM Tools from the Lan to the 172.29.0.0 or 172.30.0.0, it function only if I flag "use ICMP" button

Also I've the same problem into another client with the same ASA (version 8.0.(3)).

what happens when you temporarily add

access-list LAN_access_in permit ip any any

The same thing.

Michel can you please post the following commands output also ?

traceroute 172.29.0.14 use-icmp

and

traceroute 172.29.0.14

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: