• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5218
  • Last Modified:

Nonfunctional Networking - Network Details Blank

One of my servers stopped talking on the network late last week. After a reboot, the network cards simply do not send or receive once autonegotiation completes. The link goes up as indicated by the "Network cable unplugged" changing to "Enabled", along with a logged event indicating the link goes up. It seems to successfully complete autonegotiation, but doesn't go beyond that.

I am attaching 2 screenshots: first is the network connection showing no sent or received traffic. Second is the details page showing completely blank.

Here's what I have tried:
1) Reinstalling the drivers
2) Install a new, known-good network card
3) Rollback driver to the earliest available
4) Uninstall all windows updates, antivirus, and other potentially conflicting software
5) Turn off the server and leave it completely disconnected for several hours
6) Reset TCP/IP
7) Run malware scans
8) Connected the server to another switch
9) Replaced the cable with one known to be good
10) Updated the BIOS to the newest version

There are no event logs that point to problems except for one that I'm still looking into at the moment, which at first glance it does not seem to be related.
Event ID 7026
The following boot-start or system-start driver(s) failed to load: eeCtrl Teefer3

I'm at a loss of how to continue. Additionally, this problem has now appeared on two more computers: a Windows XP pro and a Windows 7 pro desktop.
Status.png
Details.png
0
egmtech
Asked:
egmtech
  • 8
  • 6
1 Solution
 
R_EdwardsCommented:
0
 
egmtechAuthor Commented:
The symantec article did not work. The registry key it referenced was correct without modification.
0
 
R_EdwardsCommented:
remove the symantec Endpoint protection and see if that fixes your issue, did this just stop overnight, did you install software, ect..
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
egmtechAuthor Commented:
I actually  removed symantec endpoint protection a few days ago.

The problem started after a reboot following the uninstallation of a web filter authentication client.
0
 
R_EdwardsCommented:
in device manager do you  see any "Teefer2" entry's
0
 
egmtechAuthor Commented:
Nope, I checked all entries and did not find Teefer2.
0
 
R_EdwardsCommented:
i believe they are hidden, because you installed a known working NIC, i believe that the TEEFER2's are still there but hidden.  follow the accepted answer to the below link.  i believe it will fix your issue.
http://www.experts-exchange.com/Hardware/Networking_Hardware/Q_23508822.html
0
 
egmtechAuthor Commented:
Unfortunately that did not fix the problem. Teefer2 was not in the hidden list. I followed the process in the article you linked but the problem persists. I also went through the microsoft kb article linked in that experts-exchange article, but it also had no effect.
0
 
R_EdwardsCommented:
If you go into Device Manager and under View select Show Hidden Devices, do you see anything relating to Teefer under Non-Plug and Play Drivers?

Open a command prompt and type "sc query teefer3" without quotes

What shows?
0
 
egmtechAuthor Commented:
Here are screenshots from those.
Non-Plug-and-Play-Drivers.png
teefer3.png
0
 
R_EdwardsCommented:
Because you still have a teefer3 service, that is what (i believe) is preventing your NIC, the following link is teedious and long and I appologize ahead of time for having you go through it all.  http://www.symantec.com/business/support/index?page=content&id=TECH91038

hopefully this fixes your problem.
0
 
R_EdwardsCommented:
egmtech, did you get this resolved?
0
 
egmtechAuthor Commented:
Thanks Mr. Edwards, that worked. It was indeed tedious but that's a small price to pay to restore network connectivity to a server.

There were a few entries related to teefer and eeCtrl that were not removed from the automated uninstall. Only 2 or 3 of the steps in that huge process needed to be done, but they did the trick!
0
 
R_EdwardsCommented:
glad i could help
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now