Hi,
Could you share the output of the following command
show run nat
The thing that catches my eye on the above partial configuration is that there is a "static" type NAT configuration for the "inside" interface which binds "any" source address staticly to the public IP address of the "outside" interface since the parameter "interface" is used in the command. The "static" type configuration is typically used when you have a specific host for which you want to give a static public IP address or perhaps forward only specific ports. When you want to share a single public IP address for multiple hosts then the "nat" command typically uses the parameter "dynamic"
I mean this command
nat (inside,outside) source static any interface
Now I am not sure if this is related to the problem but its atleast a NAT configuration that I would change.
You could actually do a Dynamic PAT for all the internal hosts/devices with the below command in which case you would not need the above 2 commands at all. And actually the below Dynamic PAT configuration would only get used if the above NAT configurations were not on the device. The reason for this is that they are configured on higher priority which comes from the fact that they dont have the parameter "after-auto" included in them.
nat (any,outside) after-auto source dynamic any interface
Have you looked at the real time logs through the ASDM while attempting the connections through the firewall? This might give a hint on what the problem is if its not NAT related.
- Jouni