After removing the component and restarted, the driver was identified as NDIS 6. But what if there is a need to create another teaming? Remove From My Forums. Monday, September 25, 8: This posting is provided “AS IS” with no warranties or guarantees, and confers no rights.
|Date Added:||14 June 2006|
|File Size:||21.20 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Please remember to mark the replies as answers if they help.
Notify me of new posts by email. I just confirmed this.
Problem adding NIC to Broadcom Team after installation of Symantec Endpoint Protection
Saturday, September 23, 3: The only drawback was that I lost remote connectivity to the server after the last Teefer2 Miniport was disabled. Sign in to vote.
This is really help full to solve my problem. Best Regards, Eve Wang Please remember to mark the replies as answers if they help.
Might check the bdis information” here. Please let me know if you would like further assistance. But what if there is a need to create another teaming?
Monday, September 25, 8: 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. Sunday, September 24, 1: Saturday, September 23, 4: Thank you for posting this! Thanks for your good information. Leave a Reply Cancel reply Your email address will not be published.
If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. Learn how your comment data is processed.
I found it possible to create the team without uninstalling SEP. Remove From My Forums.
Every time we tried to add the NIC to the existing team we got the following error message:. We had the exact same problem, and your procedure uninstalling Symantec, set up the team, then reinstall Symantec solved the problem!
To continue using , please upgrade your browser.
It still recreated the Tefer2 Miniport drivers, but the Team still works. Notify me of follow-up comments by email.
Hi All, I also faced this problem and the solution was broaadcom same as u guys. Something broke the team could have been Symantec, or a Windows Update, or maybe I never configured it properly in the first place.
Broadcom NetXtreme II 1 Gigabit Driver for Windows bit Driver – TechSpot
I have since added the Firewall protection back in too — no problems so far. Definitely not something that you want to have to do very often. After removing the component and restarted, the driver was identified as NDIS 6. This driver is used for the firewall features in Symantec Endpoint Protection. Hi, How things are going there bcmm5708c this issue? Resources for IT Professionals.