The "packet-tracer" test seems to indicate that the test is DROPed because the packet initially matches NO NAT configuration on the firewall but the reverse (RPF) check fails because it matches a NAT configuration.
It would seem to me that since your source address is a public IP address that you are probably attempting to simulate a connection coming from the public network, therefore the destination IP address should be a public NAT/PAT IP address configured on the ASA and not the actual private IP address of the destination host.
So the reason for the "packet-tracer" fail might be that you are using the private IP address as the destination but if the actual connection is not working then there might be other problems too.
I would suggest running the "packet-tracer" through the CLI of the firewall with the command
packet-tracer input tw tcp 12345
You can do this through the ASDM also from Tools -> Command Line Interface
There is either confusion about the actual destination IP address to connect to or perhaps some NAT/ACL configuration problem. For me personally troubleshooting would be easier looking at the CLI format of the ASA configuration.
Hope this helps