Network connectivity is lost upon upgrading Endpoint Protection
Last Updated July 01, 2019
You upgrade an existing Symantec Endpoint Protection (SEP) client and find there is no network connectivity after a reboot. Ipconfig shows there are no installed network adapters.The issue mainly occurs on systems where Cisco AnyConnect is or was installed.
ERROR: Call to installNetComponent() failed: 0x8007007e
CreateProcess Return Value: 8007007E = The specified module could not be found.
Process Monitor boot logging:
7:37:07.9571150 PM NetCfgNotifyObjectHost.exe 1804 2040 IRP_MJ_CREATE C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\drv\acnamfdbctl.dll PATH NOT FOUND
7:37:47.8109596 PM installTeefer.exe 5888 6116 IRP_MJ_CREATE C:\Program Files (x86)\Cisco\Cisco AnyConnect Secure Mobility Client\drv\acnamfdbctl.dll PATH NOT FOUND
7:37:47.9417175 PM installTeefer.exe 5888 5844 Process Exit SUCCESS Exit Status: -2147024770
The installation and removal of the SEP Firewall driver is a complex process that is dependent on the proper functioning of Windows' network configuration interface (INetCfg). INetCfg provides methods to initialize, uninitialize, apply changes to, cancel changes to and retrieve information regarding network configuration.
When one or more libraries INetCfg depends on are either missing or corrupted, or a third-party library –e.g. acnamfdbctl.dll ("Cisco AnyConnect Network Access Manager Bind Controller")– is tied to it but missing and/or no longer properly registered, calling its methods may result in unexpected behavior and network configuration damage.
Other than the above mentioned INetCfg-related issues, teeferInstall.exe may also fail due to registry settings, GPOs or other software hampering its execution.
Capture Process Monitor Boot Logging during the reboot immediately after SEP is installed. Events related to a missing third-party library (such as the one shown in the Error section above) may occur around the time of failure. If that should be the case, and installTeefer.exe specifically references that library, then please contact the third-party vendor for further assistance.
Verify the following files are present in both C:\Windows\System32 and C:\Windows\SysWOW64 and not corrupted (e.g. by comparing their file hashes with known good versions on a system where you do not experience the issue):
Note that, due to the ever-changing nature of Windows, this may not be an exhaustive list of libraries required to perform INetCfg functions. If in doubt, contact Microsoft.
Check SEP Firewall network bindings and service state:
Open a CMD.exe prompt as admin.
Enter the following command (a blank result will be returned if teefer2 has no binding):
netcfg -b symc_teefer2
Enter the following command, which will show if the teefer2 service exists or is started:
sc query teefer2
The issue may be worked around in the following manner:
Modify the SEP client's installed features to remove the Firewall, and reboot.
Modify the SEP client's installed features to re-add the Firewall, and reboot again.
Confirm whether or not networking is now functional.
If the issue continues to persist, run CleanWipe and reinstall SEP.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe