Page 1 of 1

S5000VSA teaming problem

Posted: Mon Feb 27, 2012 6:04 pm
by bigjohn888jb
I have used teaming on this motherboard for several years. Recently the team appears to be broken and just one of the nics is being used. When I look at the device manager, there does not appear to be any problem with either nic. When I click on the one not being used or on the virtual nic it says that tcpip is not enabled. I try and enable it and it refuses. I did some Googling and found a number of discussions about a ongoing problem with Symantec Endpoint Protection and teaming. My question is, is it still a problem and is there a fix recommendation?

Re: S5000VSA teaming problem

Posted: Tue Feb 28, 2012 9:48 am
by symthomas
Hi,

What version of SEP are you currently running? Are you running the latest drivings for your NIC?

See - Connectivity loss after installing SEP with Network Threat Protection on a machine with Teaming enabled - http://www.symantec.com/business/suppor ... TECH171402

Re: S5000VSA teaming problem

Posted: Tue Feb 28, 2012 10:14 am
by Scrotos
Holy crap, talk about being proactive!

Re: S5000VSA teaming problem

Posted: Tue Feb 28, 2012 11:30 am
by bigjohn888jb
Symantec version 11.0. I'm also only running antivirus and antispyware on the server. I just downloaded the latest nic drivers but have not installed them yet. That is on the agenda for this week once I decide whether it's all right to recreate the team.

Re: S5000VSA teaming problem

Posted: Mon Mar 05, 2012 6:56 pm
by bigjohn888jb
Installed the newest drivers. Recreated the team. Good for 3 days - then system crash. Server frozen. Had to do a hard reboot. Came up all right. Deleted the Team. Now what? Hardware problem? Software problem. Nothing in the event log to give me any hints.

Re: S5000VSA teaming problem

Posted: Wed Mar 07, 2012 10:21 am
by symthomas
If you feel this is an Endpoint Protection issue, I would open a case with Symantec support. You will need to be able to provide a full memory dump, so that the engineers can get to root cause.

http://www.symantec.com/support/contact ... static.jsp