Sockets....

[Soumitra Banerjee]

Hi,

I came across this wierd situation recently:

One of our cutomers, has dual NIC cards on all of their machines. The NIC
cards are "Teamed" to provide extra bandwidth and fault tolarence. These are
Broadcom NetXtreme Gigabit Ethernet cards running on driver v2.78.

When our software is run on these machines, the machine stops responding
after some time (approx 13-14 mins). The machine cannot be pinged as well.
If our software is run on the same machine without the "Teaming", i.e. only
one nic card is used, it runs fine. The OS was windows 2000 server in both
the cases.

Our software makes use of SOAP and windows socket to comminucate with other
servers.

Is this a know pattern? Does any body have any idea how to resolve this
issue?
Thanks in advance.

Regards,

Soumitra.

 

[Phillip Windell]

"Teaming" is a fairly recent technology and, at least in my opinion, isn't
fully matured and therefore will be problematic. This isn't the first time I
have heard of applications that won't behave properly with it.

Teaming should only be performed on Servers where it is actually justified
to do it. If the Server is hardly even causing a 10/100 NIC to breath hard
then there is certainly no point in "teaming" it.

I doubt SOAP has anything to do with it, but Sockets might, I don't know.
You may just have to have it run on a more "normally" configured server.

 

[Scott Harding - MS MVP]

This certainly sounds like something with your app. Your best bet is to call
Broadcom or whoever sold you the NICs and try to get some help from them.
Obviously something with their teaming software is causing the issue. I have
had lots of issues with this brand of card and usually a driver update fixes
it.