no there is no solution at the moment. My partner could not help me with that issue and now I'm waiting for an answer from McAffee. I will contact you if I got a solution.
I get the same behaviour if I connect an Ehternet cable.
Please open a ticket as well. Maybe we can raise the priority. I thenk they are waiting until every company has upgraded to WIN7 😞
Thank you in advance.
We discovered that uninstalling and reinstalling the wireless driver (Broadcom in this case) resolved the problem. Upgrading the driver had no effect. But, we also discovered that a subsequent uninstallation and reinstallation of McAfee HIPS will result in the original problem, preventing the WLAN card from connecting. I have a case open with McAfee and will be shipping them a PC to troubleshoot the problem further. They were unable to recreate the problem in their lab.
I have multiple users with the same issue. Multiple Wi-Fi adapters (Dell Lattitudes E6400, E4300, E4310, E6410, E6420, E6220) but all so far are on Windows XP. This occurred only after a HIPS 7 to 8 upgrade. Our rulesets are wide open; for some people removing and re-adding the adapter seems to work. For others that only works for ~15 minutes. We're gathering more information now.
By way of following up, HIPS 8 patch 2 solved virtually all of our Wi-Fi issues with Latitude E-series laptops from Dell. No need to touch QoS, even. On a completely unrelated and somewhat strange note, the only other thing about our 10,000+ client upgrade from HIPS 7 to 8p1 and 8p2 is that a few people (<100) with Win XP have their laptops take 20-40 minutes to boot now -- but only if it's in their docking stations. Taking it out of their docking station results in a 4-5 min boot time. Suspects include Symantec Endpoint Encryption (versions 7.04, 7.05 and maybe 7.08) in conjunction with HIPS 8 regardless of patch level.
here a Workaround to solve your issue. Change the configuration of the rule "Allow 802.1x Authentication" like this
Don't ask why, but on my Windows XP this solved the issue.
thank you for your help. But I already tried your workaround and it did not solve my issue.
Now I got feedback from mcafee and they told me to use the Adaptive" or "Learn" mode and to activate
"Allow traffic for unsupported protocols".
Now there are new rules with netbios (port 137 and 138) which are added by the adaptive mode. This solves the issue and the wlan is working properly.
I created an allow all rule for testing purpose. Nothing happend.
How can a rule solve the issue if there is a rule on topwhich allows all traffic? This does not make any sense!!?!?
Thank you in advance
have you changed the log settings to debug logging for the firewall-log. Are there any information about blocked traffic in the debug log?
Have you recognized that i changed the rule to custom specify ether type.
Our wireless performance improved after disabling the Startup Protection, "Allow only outgoing traffic until the Host IPS service has started" in the Firewall Options policy. We still occasionally have issues with Bootp and EAPOL communications, which prevents the wireless connection. But, it's intermittent and a reboot or manual "Enforce Policies" usually fixes it.