The HIPS firewall Activity Log shows no traffic being blocked that would relate to Outlook.
Not all required (blocked) traffic is tied to a specific application. From the Activity log, the blocked traffic may not have any application associated with it, which means it's SYSTEM-based traffic (meaning a firewall rule will be needed to allow the traffic and you cannot associate it to a specific application; the application column will need to be left blank).
- Does disabling the Firewall resolve this issue?
- Add a firewall Allow all rule to the top of the policy. Does this resolve the issue?
- If so, then you'll need to parse the Host IPS Client UI Activity Log and look for any blocked traffic (remote IP address of an Exchange server, or something) needed by Outlook (look through all traffic; not just that associated with Outlook.exe).
First of all, it is so cool to be able to post a question and get an actual response so fast. Unheard of in the tech support community. I'm starting to like this board.
Setting the firewall to Adaptive mode is all that's required to make the crashes stop. You don't even have to disable it. And I should be clearer--the HIPS firewall activity log doesn't show any traffic being blocked at all, other than some of the normal broadcast stuff that happens all day every day.
I would suggest opening a McAfee Service Request for further investigation. That does seem quite odd.