After switching from ASA 5510 to ASA 5512 strange ack = (big number) behavior?

After switch from ASA 5510 to ASA 5512 the internal network are acting strangely. We can't connect and print to our Konica-Minolta printers. And can't connect to WMware ESX via Sphere. Everything else seems to work OK. Our switch is a Cisco 2960S. No vLan.
The funny thing is when we connect to our hosted office server via RDP we can connect and print.
The ASA's are configured 1 to 1 as closely as possible. Latest firmware on both.
Switching back to ASA 5510 removes the problem.

We have had Cisco people looking at this, but no luck so far, except for the communication to the printer, ACK= are not 1, but a large number?

Does anyone have clue to this?
khcAsked:
Who is Participating?
 
AkinsdConnect With a Mentor Network AdministratorCommented:
I probably would recommend a packet trace to identify where the packets are dropping

- packet-tracer input inside tcp 192.168.118.x 4444 192.168.118.x 4444 detailed

You can also use Examdiff to compare both configs to determine if a command is missing or a new command is introduced
http://www.prestosoft.com/edp_examdiff.asp

Also, check if aaa authentication is enabled on the switch or any acl that may be filtering traffic based on MAC address
0
 
SouljaCommented:
Can you post both fw configs as well as the switch? Please attach them to the post instead of pasting them.
0
 
Cyclops3590Commented:
ACK being a large value doesn't mean anything.  I'm assuming you're talking about seeing it in wireshark maybe.  could happen if it doesn't know where the sequence numbers started depending on when the capture was started so it doesn't know the relative number to the starting point.

But as Soulja commented, the configs would help.
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
Henk van AchterbergSr. Technical ConsultantCommented:
How is your NAT config?

Are you sure that ProxyArp is not messing things up?

When you are on the same network traffic should not flow trough the ASA when connecting internally.
0
 
SouljaCommented:
Until configs are provided, we can only make assumptions.
0
 
khcAuthor Commented:
Thank you for answering. Here are the configs for ASA 5510 and ASA 5512.
ASA5510-5512runningconfig.txt
0
All Courses

From novice to tech pro — start learning today.