10-12 users that use email/O365 regularly. There isn't a heavy workload that would explain any significant lag. ... View more

No "sysop..." line, and both inside and outside interface is/was static IP.  ... View more

As far as traffic shaping goes, I've:   1) disabled all rules, 2) ran with just the default set,  3) ran with just the Office365 (in Productivity) set on high priority, 4) set all email to high priority and 5) basically every combination of 2-4 (2+3, 2+4, 3+4, 2+3+4)    and the issue persists. So.... 😞   ... View more

The ASA5510 MTU was also 1500 so I don't see that as the issue. Thanks for the suggestion though! ... View more

If nothing else, your post made me laugh. 😄    I work for a non-profit that thinks IT ranks behind cutting down trees in the parking lot. So, yes, I have crappy outdated infrastructure which has certainly caused many headaches. (Until last year, they were running on Exchange2003, on an WinServer2003 box...) It is certainly a possibility that improving one aspect of security can make an older system fail, my thought is the huge increase in our bandwidth. I'm trying to throttle email back down to ASA5510 levels to see if that helps (why it would, I don't know, but I'm grasping at straws). Thanks for pitching in! ... View more

These are the only entries in the event log, although they repeat every 30 minutes.   Nov 14 07:29:40 70:71:bc:53:39:a2 Source IP and/or VLAN mismatch source_client_ip: 192.168.0.71, source_client_mac: 70:71:BC:53:39:A2, source_client_assigned_vlan: 1  « hide last_illegal_ip 10.1.10.3 client_total_illegal_packets 24027 all_total_illegal_packets 52127 last_reported_total 51450 Nov 14 06:59:40 00:50:56:ae:00:01 Source IP and/or VLAN mismatch source_client_ip: 169.254.229.95, source_client_mac: 00:50:56:AE:00:01, source_client_assigned_vlan: 1  « hide client_total_illegal_packets 4165 all_total_illegal_packets 51450 last_reported_total 50787 ... View more

I am aware of the deprecated support for Office 2010 (so is our board, as I tell them every month). However, if I put the ASA5510 back in place as the front edge device, the issues go away. They are only present with the MX device. ... View more

The MX is solely acting as the front edge Layer 3/7 device, no VPNs are configured. All clients experiencing the O365 issues are internal.   I do have traffic shaping rules in place delegating O365 (and all email functions) as high priority. I have internal controls on access to YouTube/gaming/etc in place so they are not relevant.   I'll check out the Meraki Insight tool - if I can find it! 😉 Thanks for the advice. ... View more

It's not. In fact, our throughput has increased about 30-50x with the new MX appliance. The average DL/UL speed with the ASA5510 was 3-5Mbps, and the MX is in the 170Mbps range.    As to the application specific issue, while I'm open to that possibility, when I switch back to the ASA5510 as the front edge device, the O365 issues disappear. There are no specific rules on the ASA5510 relative to O365/Microsoft.com etc. either. ... View more

Most users are connecting via Outlook2010. I have checked event logs, and the only thing I get is a generic AppHang - Outlook has lost connection to Microsoft, followed by a Windows Error log:   Source:        Windows Error Reporting​ Date:          11/13/2019 4:36:47 PM​ Event ID:      1001​ Task Category: None​ Level:         Information​ Keywords:      Classic​ User:          N/A​ Computer:      ***************************​ Description:​ Fault bucket 1251049214596579294, type 5​ Event Name: AppHangB1​ Response: Not available​ Cab Id: 0​ ​ Problem signature:​ P1: OUTLOOK.EXE​ P2: 14.0.7230.5000​ P3: 5c673b81​ P4: 87fc​ P5: 134217728​   Nothing specific to Outlook in the application logs either.  ... View more