diagnose | PeteNetLive

Problem

Event ID 4107

Failed extract of third-party root list from auto update cab at: <Microsoft URL>with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

There’s a lot of info on this error out there in forums, and 99% of it had nothing to do with my problem.

Its basically a certificate error, to get to the bottom if it you need to dig a bit deeper.

Solution

If you have been hunting for a fix, and got here, you may of already tried some or all of these which DID NOT WORK, downloading and installing the certs from the link in the error,or deleting all your expired root certs.

1. First you need to get some detailed logging on what’s failing, Click Start > Control Panel > Administrative tools > Event Viewer > Expand Applications and Services > Microsoft > Windows > CAPI2 > Right click “Operations” > Select “Enable Log” >Then reboot.

2. Return to the same place in Event Viewer > And open the errors listed there, as you can see “In My Case” the problem is McAfee, after I removed McAfee and installed the latest version (8.7i with patch 3 at time of writing), the error ceased.

Note: Your problem may not be McAfee, but at least you now have a better idea of what it is 🙂

KB ID 0000439

Problem

While attempting to connect to a Windows share you receive the error.

Windows cannot access {target machine name} Check the spelling of the name. Otherwise there might be a problem with your network. to try to identify and resolve network problems, click diagnose.

if you click “Diagnose” you will see the following,

Error code: 0x80070035 The network path was not found.

Note: You may also find that if you attempt to connect a share or map a drive via the target machines IP address it works fine.

Solution

1. Firstly I’m assuming you have used the correct target machine name (can you ping the target server by its name?)

2. Make sure the Computer Browser Service is both enabled and running.

3. On both the source and target machine, make sure NETBIOS over TCP/IP is enabled.

4. Finally of none of the above have worked, drop to command line and issue the following two commands. (Note: before proceeding take note of the machines IP address, subnet mask, default gateway and DNS settings (from command line run “ipconfig /all”).

[box] netsh winsock reset netsh int ip reset c:tempresetlog.txt [/box]

5. Reboot the server.

WARNING: When the server has rebooted, it will come back up with a DHCP address, if this is a server or machine that has a static IP address, you will need to re-enter the correct details post reboot.

PeteNetLive

Technology that 'Just Works'

Tag Archives: diagnose

Event ID 4107

Problem

Solution

Related Articles, References, Credits, or External Links