We do not have PROSet software that is used for teaming for Intel PRO 1000 MT dual port adapter in Windows 2008, there is only built-in driver provided by Microsoft for this network adapter. You can refer to this website for reference:
That's weird because by installing either the 19.5 driver or the 18.4 driver I get teaming.
I can configure a team.
All works except the connection will NOT accept a static IP address, nor will the team work consistently, though it claims it's connected to the internet. One minute it's working and connected, responding to pin, allowing file transfer, then the next minute it's down.
Nic won't take a static IP with w/o the team either so I think it's a fundamental problem.
Whatever it is, I do not believe it's a lack of support on this item. I think it's screwy drivers.
I will also note that this machine had the 'old' un-upgradable and un-uninstallable drivers in it that had to be hacked out. It's possible I regedited something I shouldn't have - though I did follow the Intel directions.
At this point I've tried
Now running 17.4 drivers.
Turns out all this hoopla was because adaptive load balancing does not work.
Set to Fault Tolerance and it works. Even static IP works. Unfortunately this does nothing for performance.
Static Link Aggregation also fails is flaky. One second it's responding to ping, the next it's not.
IEEE dynamic link aggregation also fails.
So I guess teaming is fault tolerance or nothing.
The teaming may or may not be possible, as mentioned in our FAQ " This depends on the selected ANS functions enabled in the team. Because there are a number of possible combinations, and they change constantly, adding an adapter with only in box support may or may not be possible."
Well, to the best of my ability, this card will not support any kind of performance teaming. If you know how to get it done I'm all ears, but I've tried every combination I can conceive of.
Fault tolerance is OK.
Other than that, no other options will work - get the card(s) online and/or apply a static IP. Allowing the team to get it's ip thru a DHCP reservation gives a flaky connection. It'll respond to ping 5-15 times then falls off. Applying a static IP (like should be done) gives no response and it's reporting connectivity to the internal network only.
At this point I've given up and will leave this old server on fault tolerance...the new server is taking over all it's roles anyway, the old dog is just going to be a backup.