We are seeing this issue. It looked to start yesterday for us. Have you gotten your issue resolved yet?
No, McAfee support and I have not resolved the issue yet.
Since it states it is a SSL Handshake error, we suspected it may have something to do with our recently enabled SSL Scanning rule. However, the first reports of the issue were on machines that aren't included in my SSL Scanning test group, so I don't think it is related to that. Nevertheless, we created a test SSL Scanning ruleset to enable if the problem happens again; this will prove whether the SSL Scanning rule is responsible for the error or not. Unfortunately (or fortunately, depending on you outlook), I haven't been able to catch the problem happening for over a week now. It appears to be a VERY intermittent problem.
I'll post back here if I get more news. In the meantime, feel free to use this thread for any updates from your end.
Thanks for the update Travler. We cam in this morning and our issues seem to have resolved themselves. Very odd behavior.
We occasionally had problems with Google before McAfee provided the feature to NOT "Include indication that previous handshake failed". If you use "Alternative handshake settings" with lower TLS protocol level make sure NOT to activate that feature because otherwise Google servers will put you down on second attempt because of TLS_FALLBACK_SCSV
After speaking with McAfee support, we created some troubleshooting rules to help pin point the problem. However, we have never caught the problem happening again. For that matter, none of our end users have reported experiencing the problem again, either. I can only conclude that it was an intermittent problem with perhaps one or two of Google's servers.
If we ever experience it again, I'll be sure to post back here.