First thing we would need to know is if the connections for ports 4480 and 4481 are TCP or UDP or both? We would also need to know which host/server opens/forms these connections? Are the connections opened from your LAN or from the WAN?
When the ASA allows a connection it will naturally allow any return traffic for this connection. This means when you have allowed the original opening direction of this connection then the return traffic back to the original connecting host will be allowed by the firewall.
If your LAN host opens the connection then I would imagine that this traffic is already allowed since in most environments most traffic outbound is usually allowed.
If these connections are formed from the WAN then first you would naturally need a NAT configuration for the host to which they are connecting to. Each host that is connected from the external network need their own NAT configuration or this connectivity is not possible.
On the ASA there is a command called "packet-tracer" that will let you test different type of packets entering the ASA on a certain interface. This will tell you if it will be allowed or blocked by something.
If you for example have an interface called "inside" and there you have an host with IP address 10.10.10.10 that is trying to form a connection to an external host with the IP address 126.96.36.199 with the destination port TCP/4480 then you could test that with the command
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...