Maybe the next steps would be to confirm that the connection from Server A is coming to ASA through ASDM monitor perhaps?
If they are coming to ASA you can probably also see what happens to the connection. Is the connection perhaps tore down because SYN Timeout or something else.
Maybe you can even take a capture of the traffic from Server A on the ASA to see what happens.
Does the ASA have an permitting statement on the inside ACL? Your ASA configuration attachment doesnt show the access-list itself, but only that an access-list has been attached to the inside interface.
I guess one culprit might even be the inspect command on the ASA if you have it enabled under the policy-map (at the very end of the configuration when issuing "show run" on CLI, or you can just issue "show run policy-map") But this is just guessing from me.
Have you tried using ICMP to confirm that there is connection from Server A to the other network?
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...