It is possible that my testing was compromised. I'll be doing more testing this Saturday. In our environment, MaaS360 uses ActiveSync to access our Exchange environment. For this question, we have 3 impacted solutions. We have a physical secure remote access (SRA) appliance and a virtual Exchange Server environment. The Exchange environment is used for MaaS360 and OWA (Outlook Web Access). As SRA and Exchange are public facing, we use NAT to access the private IP of the devices. In my current environment, I have reflexive policies in place. This is necessary, as the static public IP of the destination is actually already on the WAN environment of the same firewall managing the Wi-Fi (which causes traffic to stop without a return policy). I generally have the Wi-Fi network completely isolated from the LAN environment. I have at times made exceptions DNS and RDP. Anyhow, I tried using the L3 Outbound rules to create a reflexive policy of the associated NAT policy. No effect. However, I was having other issues with my test environment that may have been coming into play. I'll confirm on Saturday. Oh, along that line, I need an internal device to leave with a specific public IP address. In SonicWALL, this is also addressed by NAT. Is it safe to assume that L3 outbound rules can accommodate that, too?
Thanks,
Jeremy
