Thanks. I'm still waiting for McAfee support to contact me (seems to be par for the course).
In the meantime, I've discovered the following commonalities:
When a machine is having the problem, (so far every machine I've looked at):
The Event Viewer -> System log shows that it starts the network driver and then never proceeds to run the W32Time process.
The Event Viewer -> Application log shows that I get FOUR Dot3Svc logs where it starts the 802.1 Authentication and then the 4th one says that the 802.1X auth succeeded (we do NOT use 802.1 authentication, so how it can succeed I don't know)
Now, when the machine is working properly:
System Log shows it loads network driver and then loads W32Time (and then other stuff)
Application log shows only THREE Dot3Svc entries, the 3rd one is the "started 802.1 authentication) and then I do NOT see the 4th one (auth succeeded)
So I'm GUESSING that for some strange reason if 802.1x auth "succeeds" it breaks something. Since I know for a fact we have nothing on our network that uses this, I've turned off the 802.1X auth in Windows for the network card on a few machines and we'll see what happens.
No wireless on our Desktop Optiplex GX-620 or 745's, and I've verified we are at the latest drivers.
IF this doesn't work, my suspicion then is that it's either the:
Unfortunately McAfee's VSE 8.8 "troubleshooting" guide is atrocious on this:
If it's mveftp then open a support call (yeah that's gone stellar so far)
If it's the mfehidk.sys then open a support call
Remove VSE. If problem goes away then it's probably related to VSE.
REALLY? Say it isn't so (step 3).
Well so much for that idea. Machines continue to have the problem.
I guess I'll have to call McAFee and complain to get this escalated.
Very disappointing that others have the same problem with VSE 8.8 and McFee's been no help at all.
Maybe we need to look at other vendors after this.
Got ahold of someone decent at tech support and we have a bunch of things to try now.
Robster--did you guys ever open an SR with McAfee?
I'm asking becauase according to the Tier 3 guys they've never heard of this before, but I was like, "there's 2 other people on the forums with the problem with 8.8 as well"
No to be honest I dont think we did. We tried so many things that we just gave up and went back to the old version as we were getting so many phone calls. It is a very strange one as it does not happen all all workstations even though a lot camefrom the same image. My plan was to wait for another version to come out and then do department by department rather than everybody like we normally do.
Did you have the problem with JUST Windows XP? Did you see the issue with Windows 7?
I've had it happen on a relatively clean vmware machine, along with a real machine with little to no extra software on it, so I'm still leaning towards some timing conflict with the mfehidk.sys driver.
Out of curiosity, did/do you guys use the Novell Client 4.91 by any chance?