Yes X windows is back to front ie. 6000 is an Xwindows port and in absence of inspection you would need to allow that port back in from the remote client. Trouble is X runs on a range of ports 6000 -> 6xxx, apologies but can't remember off the top of my head what the top range is !
An alternative is to look into tunnelling X through port 22 which would allow you to secure the connection. I must admit i didn't realise they had dropped the inspection - seems like a mistake to me.
For testing puposes I have amended my inbound ACL on the ASA to allow ALL IP from the Remote IP address to the IP address our connection gets NATed to.
I have also created an ACL, put this ACL in a class map and added this class map to the policy map to esnure that matching traffic gets inspected, but still no joy. The same error I'm afraid.
I don't suppose you have any other ideas do you? also, does anyone know of a command I can use on the ASA to show inspected traffic, I am looking for a similar command to the router command, sho ip tcp inspect....
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...