cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
608
Views
0
Helpful
3
Replies

Strange response from ASA

lynne.meeks
Level 1
Level 1

We have two identical ASA 5540s on our Border.

If we try to connect to a host protected by one of the ASA's on a port that is not permitted for this host, this results in a brief connection; the connection is then immediately closed- see below:

...$ telnet host.domain.edu 24

Trying x.x.x.10...

Connected to host.domain.edu.

Escape character is '^]'.

Connection closed by foreign host.

If we move the routing for this same host to the other ASA -which has the same rules and settings as the first ASA- we do not get this result; no connection is opened.

We can't figure out what is causing this.

Anyone else seen anything like this?

thanks,

Lynne

3 Replies 3

Patrick Iseli
Level 7
Level 7

Looks like an application layer protocol inspection or fixup in the old versions.

http://www.cisco.com/en/US/docs/security/asa/asa72/configuration/guide/inspect.html

Have setup this for tcp port 24 ?

Take a look in your config.

I've looked at the config and there is nothing that should respond on TCP port 24 for that IP address.

Yesterday we moved the routing for this host to another ASA with an identical configuration with respect to all rules for this host and all inspect commands - and the problem went away.

So I'm thinking it is not a configuration issue... Strange, huh?

Solution found: We reloaded the firewall and this behavior went away.

The last time this box was reloaded was just after we had located and stopped some malware traffic that was causing severe memory overload on the FW and causing it to stop passing traffic.

So perhaps there was still some memory corruption from that event- that's my best guess for now.

thanks-

Lynne

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: