The problem you describe sometimes happens if the drivers and PROSet are not the versions that belong together. There is an article at http://www.intel.com/support/network/sb/CS-016722.htm that might help get you to the point where you can use PROSet to remove the virtual adapters and get teaming to work again.
I can see you tried removing the PROSet and/or ANS software. You might try to use add/remove programs and then install the drivers, PROSet, and ANS from scratch. You should use the PROSet software to remove the old teams if you can.
Although the listed symptom is different than your problem, there is a trick listed at http://www.intel.com/support/network/sb/CS-020087.htm for finding and getting rid of old ANS driver files. You could do this after the uninstall from add/remove programs and before you install the new software.
Depending on what version of software you had the problem with, you might want to try the latest software download available at http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=880. I would recommend completely removing the old software before you install the new version.
If all else fails, you can call or email customer support. The links for contacting support are on the page at http://www.intel.com/support/feedback.htm.
Once this is fixed, please post what you did. Thanks.
I have inherited a system with multile servers, each server has Intel nics and all are teamed
but I am noticing poor performance, mix of Windows, Linux, VMWare servers
can anyone point me in the right direction
I have the following
3Com Switch 4200G 3CR17662-91
Software Version: 3.01.00s56
2.) two NICS
Intel Pro PM 1gb nic
Intel Pro PL 1gb nic
most recent drivers and Intel ProSet with ANS installed
-have setup aggregated ports on switch
-have tried team setup as SLA (Static) for aggregate bandwidth
-have tried team setup as DLA (Dynamic) for aggregate bandwidth
1.) as SLA I run the test utility on Intel ProSet DeviceManager plugin and it explains that switch is not configured properly
2.) as DLA it seems to be teamed fine, Windows shows it as 2gb NIC, but my performance is slower then when on a single NIC
I can help you out with some hints on the NIC side, but I don't have any information about configuring the switch to deal with problem #1. I hope some of the following will help you with problem #2.
Link aggregation provides extra bandwidth when multiple link partners are connecting to your system. Although you gain bandwidth, the speed of each adapter is still a gigabit per second. If you test one adapter versus the team adapters with a connection between two link partners, you will be adding some overhead to the connection, so the performance might suffer a bit.
In some cases, depending upon your ultimate goal, you might be better off using load balancing teams instead.
Some of my colleagues collaborated on a document that includes an explanation about performance on teams using link aggregation. The Link aggregation part starts about half way down the page at http://www.intel.com/support/network/sb/CS-025829.htm.
You might also get some ideas from teaming section in the User Guide. That section is a fairly quick read. You can download a copy at http://support.intel.com/support/network/sb/cs-009715.htm.
Let us know if you have more questions or need clarification on any of this information.
I tried your suggestions and unfortunately they did not work. I did however manage to remove the adapters after some careful system tinkering. Here's how I did it...
First I removed the team that I successfully setup with the proper version of PROSET that my adapters required (this whole problem started because I was using a version that was too new for my adapters). I then rebooted the server in safe mode. Open regedit and navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\IANSMINIPORT key. Inside of the IANSMINIPORT key is where all of the virtual adapters' information is stored. Before deleting any of this information, BACK UP YOUR REGISTRY. There were subkeys located within this key ( the first one named 0000, the second 0001 and so on), one for each virtual adapter that was installed. Once I deleted the IANSMINIPORT key and rebooted the system, all was back to normal. I then reinstalled the correct PROSET version and reconfigured my team. All is good to go.