The funniest thing is happening, when I input my IP address and subnet mask and Gateway in the TCP/IP properties, it goes in fine and I apply and close. When I reopen it it is back to "Automatic setings". When I check the Ipconfig everything is there and I can ping, all my apps run okay and it seems fine. This happens whether I use teaming software and put my ip setings in the virtual team or in the NIC properties individually. Is there a registry setting not changing or has anyone seen this before?Scott Cummins

From experience using Teaming software, once the Teaming software creates the Virtual NIC, that is the NIC that you use to apply the TCP/IP settings. The real NICs should not have an IP configured and will be left to "automatic" settings.When teaming either using a fault-tolerant or load balancing scheme, the IP settings are shared for both NICs. The teaming software will take care of binding the IP properties to the NIC (on the primary if running fault-tolerant, or shared on both if runing load balancing) Visit my blog: anITKB.com, an IT Knowledge Base.

ScottCummins, Jorge is right on the money, as usual. The physical interfaces will likely lose their static config, but you can typically (depending on what vendor's teaming software you are using) still see it in the registry at: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces I will take a second and add my two cents (though you may value it more or less) to say that I would suggest you seriously weigh out the benefits of network teaming, in my experience it causes more problems than it fixes. See: http://cbfive.com/blog/post/Considering-Network-Teaming.aspx If you need extra help, you can reach us at: InitialAssist@cbfive.com See my blogs at http://www.cbfive.com/blog / Jared

I agree with Jared on the benefits of teaming. We no longer use teaming in the organization as we saw very little benefit with high cost in regards to configuration, troubleshooting, and of course actual $$$ costs related to switch ports, cabling, and patch panel ports. When you are working with several hundred servers, and very expensive switches, this is sustantial in terms of money. Visit my blog: anITKB.com, an IT Knowledge Base.

GentlemenAs usual you all are correct. But I may have mistated the issue. after I have input my static settings and applied them and then closed the TCP/IP properties window. If I open it back up. The window has reverted to "automatic settings" even though the Static is bound and when I check it IS what I put in. I am just concerned because The window is actually displaying falsely. But I have another server configured exactly the same with the same teaming and If I check the property settings there it shows all my static entries. I was just wanted to find out if perhaps there was an easy way to fix this, I have unistalled the NICs, uninstalled The 'client for microsoft Networks" and it still reverts. I'd hate to do something more drastic, just for this. I thought maybe somewhere in the registry this was not being savedScott Cummins

Ok, understood your scenrio now. This is the downside to adding more layers to any solution. The extra complexity has now created uncertainty in what the actual cause is. I assume what you mean is that you know for sure that IP is bound because you have verified that via IPCONFIG or another method, but when you view the properties, it shows "automatic settings". Hmm...I have not personally had encountered this situation, but similiar ones related to network adapters. As a matter of fact, I was assisting someone else with a NIC problem that was resolved by deleting the NIC from device manager and allowing Windows to re-install it. I hate it when this has to be done to resolve an annoying problem.http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/75826deb-e0f3-4a56-a8b8-c85cc3d5f6afSo to answer your question, it is possible that you may have to uninstall the Teaming Software and/or uninstall the NICs and reload one step at a time. Of course, i would leave that as a last option as Jared or someone else may post some other ideas. Visit my blog: anITKB.com, an IT Knowledge Base.

Scottcummins, I agree with Jorge on this (and most things). Reinstalling the NIC/teaming may help to resolev the issue. Truthfully though this may also be a function of the NIC teaming software itself. What version are you using BTW? In either case though, if you reinstall and start over you will either fix the issue, or know that the teaming has something to do with it. One curiosity that I have is if you can find the config for this in the registry here (which is where ipconfig pulls it information): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces You should be able to find the registry and the IP info under the interface GUID. If you have any problems identifying the NIC this article may help: http://cbfive.com/blog/post/How-to-Find-a-Network-Adapter-in-the-Registry.aspx. If you fidn the data there it means that some application, likely to be teaming, is not preventing the write, but is spoofing the read of these registry settings. If you need extra help, you can reach us at: InitialAssist@cbfive.com See my blogs at http://www.cbfive.com/blog / Jared

GentlemenThanks so much fopr your input, I believe I will at least have to try and remove and re-onstall the teming software and team. I just want to make sure I also understood another bit of information. It sounded like a concensus that no one likes teaming?I am using that HP software that comes with every new HP DL-380 and DL-580. I don't really need the team, But if it is an issue or could cause network pronblems I would certainly go single nic with a standby.Scott Cummins

My recommendation regarding teaming or any other technology is that if the business does not require it, then it should probably not be installed. Everything we do in IT has a cost associated so while implementing new technologies are always exiting, there is a cost involved. This is not to deter you from learning about it and possibly finding a need in your business that teaming could fill. My experience has been that over a 10 year period, I beleive there was only one occurrence in which we had a link failure and it was very nice that teaminig was enabled so that services where not impacted. With a network of over 1000 servers (all of them werent teamed of course), implementing teaming accross the board is very costly.We no longer team our server's NICs. Visit my blog: anITKB.com, an IT Knowledge Base.