skunkey
asked on
Intel PROSet Wireless Drivers: Event ID ( 5005 ) in Source ( NETw5x32 ) cannot be found.
Hi All,
I have a laptop exhibiting some strange issues:
Dell E6410 using Intel PROSet V13.1.1.1 on a large corp LAN using RADIUS/WPA-TKIP/LEAP
Drivers were upgraded from 10.5(old removed, new installed).
The description for Event ID ( 5005 ) in Source ( NETw5x32 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: , Intel(R) Centrino(R) Advanced-N 6200 AGN
Frequency: 4 times in the last week.
This has only happened after the drive was encrypted using a Sophos SafeGuard solution however I don't believe its is related.
Can anyone tell me what this message actually means?
One thing I do know is that the Sophos solution does ammend the registry to ensure it comes first in the GINA chain (The current environment has the Intel PROSet drives initialising before the Windows LogOn) but I can't see why this would throw up an error like this.
I have a laptop exhibiting some strange issues:
Dell E6410 using Intel PROSet V13.1.1.1 on a large corp LAN using RADIUS/WPA-TKIP/LEAP
Drivers were upgraded from 10.5(old removed, new installed).
The description for Event ID ( 5005 ) in Source ( NETw5x32 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: , Intel(R) Centrino(R) Advanced-N 6200 AGN
Frequency: 4 times in the last week.
This has only happened after the drive was encrypted using a Sophos SafeGuard solution however I don't believe its is related.
Can anyone tell me what this message actually means?
One thing I do know is that the Sophos solution does ammend the registry to ensure it comes first in the GINA chain (The current environment has the Intel PROSet drives initialising before the Windows LogOn) but I can't see why this would throw up an error like this.
ASKER
Hi Sajen_Jose,
Thanks for the quick response, I did see that article when browsing yesterday.
I don't know if all the bluetooth drivers are up to date or not so I'll check that out. I do know that the Sophos SafeGuard product is all about controlling information flow and offers the ability to lock down USB Ports. It must have to interact with the USB Driver stack to do this so maybe thats whats causing an issue.
The machine is being re-deployed and then tested to see if the issue re-occurs. If it doesn't then we will encrypt again and see what happens.
I'll post the results.
Thanks for the quick response, I did see that article when browsing yesterday.
I don't know if all the bluetooth drivers are up to date or not so I'll check that out. I do know that the Sophos SafeGuard product is all about controlling information flow and offers the ability to lock down USB Ports. It must have to interact with the USB Driver stack to do this so maybe thats whats causing an issue.
The machine is being re-deployed and then tested to see if the issue re-occurs. If it doesn't then we will encrypt again and see what happens.
I'll post the results.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
Am not sure of the solution but we have a similar thread here
https://www.experts-exchange.com/questions/24313364/Can't-connect-manually-to-access-points.html