Teaming NICs and NLB often don't work together very well.
See 278431 INFO: Using NIC Teaming Adapters with Network Load Balancing May
Cause
http://support.microsoft.com/?id=278431
--
Thanks,
Marc Reynolds
Microsoft Technical Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Peter W." <(E-Mail Removed)> wrote in message
news:E7F0EF8A-266C-4E68-99D6-(E-Mail Removed)...
> I am running two Microsoft Windows 2003 Servers with both
> an Intel PRO/1000 dual port server and dual port network
> adapter (four ports in all). I also have two Cisco 2621
> switches that are divided into two segments. One segment is
> internal and one is external.
>
> I have configured Teaming on the adapters such that port
> one of the server adapter is Teamed with port one of the
> network adapter and port two to port two. I have also
> configured the preferred primary adapters such that there
> is a preferred primary running on each physical adapter.
> On the internal team I am running Adaptive Load Balancing
> Mode and on the external team I am running Adaptive Fault
> Tolerance Mode. IN PREVIOUS TEST MS NLB WORKED IN THE
> Adaptive Fault Tolerance Mode, BUT WOULD NOT WORK PROPERLY
> IN Adaptive Load Balancing Mode with our configuration. By
> the way, I am running the 10/28/03 adapter drivers and
> PROSet 8.3.0.0.
>
> MS NLB has been configured for the external adapter as
> follows: THESE ARE NOT THE ACTUAL IP ADDRESSES - SUBNET
> MASK FOR ALL IPs 255.255.255.192
>
> Also, cluster operation mode is set to multicast.
>
> 68.251.25.85 - Dedicated Server #1 - No Load Balancing
> 68.251.25.86 - Dedicated Server #2 - No Load Balancing
> 68.251.25.89 - Cluster Master
> 68.251.25.90 - Multiple Host w/Affinity set to None
> 68.251.25.91 - Single Host w/Preferenced to Server #2
> 68.251.25.92 - Single Host w/Preferenced to Server #2
> 68.251.25.93 - Multiple Host w/Affinity set to None
> 68.251.25.94 - Single Host w/Preferenced to Server #2
> 68.251.25.96 - Multiple Host w/Affinity set to None
> 68.251.25.97 - Multiple Host w/Affinity set to None
> 68.251.25.98 - Multiple Host w/Affinity set to None
> 68.251.25.99 - Multiple Host w/Affinity set to None
>
> For completeness the following IPs are also running on the
> external adapter, but are not load balanced.
> 172.18.8.x - 255.255.254.0
> 172.18.9.x - 255.255.254.0
>
> PROBLEM: Initially the configuration works properly. You
> can remotely connect to any or all of the NLB addresses.
> But, at some later time, I don't know how much later, none
> of the NLB addresses can be reached remotely.
>
> I have been at this for weeks. Does anyone have an idea of
> what the problem might be. Could it be something with the
> switches or mac address problems?
>
> Thanks in advance.
>
> Peter W.
>
>
> Upon further reading, I realized that Adaptive Load Balancing
> was not the correct team type for my configuration. I have two
> sites Production and Development or Test. In Production I have
> two switches and in Development I have one. NLB was tested in
> the Development environment. I changed my Production team
> type to Switch Fault Tolerance and the problem still exists.
>
> If anyone has any ideas feel free to chime in.
>