After removing the component and restarted, the driver was identified as NDIS 6. Your email address will not be published. Every time we tried to add the NIC to the existing team we got the following error message: Definitely not something that you want to have to do very often. Please let me know if you would like further assistance. Thank you for posting this! Saturday, September 23, 4:
|Date Added:||22 April 2004|
|File Size:||10.7 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Broadcom NetXtreme II 1 Gigabit Driver 22.214.171.124 for Windows 64-bit
I found it possible to create the team without uninstalling SEP. Hi All, I also faced this problem and the solution was to same as u guys.
Monday, September 25, 8: This posting is provided “AS IS” with no warranties or guarantees, and confers no rights. Sign in to vote.
Problem adding NIC to Broadcom Team after installation of Symantec Endpoint Protection
This site uses Akismet to reduce spam. In order to get the teaming working again, we uninstalled Symantec Endpoint Protection, then setup the team, then rebooted the server and reinstalled Symantec Endpoint Protection. Notify me of new posts by email. Definitely not something that you want to have to do very often. Please let me know if you would like ndiw assistance.
Saturday, September 23, bcm508c It still recreated the Tefer2 Miniport drivers, but the Team still works. I have since added the Firewall protection back in too — no problems so far.
Broadcom BCMC NetXtreme II GigE (NDIS VBD Client) #
But what if there is a need to create another teaming? We had the exact same problem, and your procedure uninstalling Symantec, set up the team, then reinstall Symantec solved the problem! Your email address will not be published. Hi, How things are going there on this issue? By continuing to browse this site, you agree to groadcom use. Best Regards, Eve Wang Please remember to mark the replies as answers if they help. Sunday, September 24, 1: Might check the “important information” here.
If you have feedback for TechNet Subscriber Support, contact tnmff microsoft.
Not an IT pro? Every time we tried to add the NIC to the existing team we got the following error message: Office Office Exchange Server. I had the same problem and this fixed it right away.
Thank you very much, very useful. Thank you for posting this! Remove From My Forums. I just confirmed this. Saturday, September 23, 4: Something broke the team could have been Symantec, or a Windows Update, or maybe I never configured it properly in the first place.
Had exact the same problem.