NIC teaming gone/NIC drivers won't load

Problem:  I am running Windows Server 2008 R2 on an HP Proliant DL185 G5 and both onboard Broadcom NICs are showing the yellow exclamation mark in Device Manager.  When viewing the Device Status in the Properties, each one says "This device is not configured correctly. (Code 1)  The parameter is incorrect.   To find a driver for this device, click Update Driver."  Has anyone seen this issue or know how to resolve it.  I have done some research and cannot find a resolve.

History:  Everything was running fine as I had both NICs setup with NIC teaming (Windows called it MAC Bridge, I believe).  I was trying to remove the team to test a completely different problem and could only remove the team by removing it from Device Manager (I did not remove the Broadcom adapters just the teaming adapter).  After doing so, both Local Area connections disappeared from Network Connections and I noticed the problem in Device Manager.  I spent an hour and a half with HP support and we replaced the drivers for both NICs at least three times with three different drivers (removing the adapters from Device Manager each time) and rebooting.  I have also tried installing another NIC card and the drivers loaded (like with the Broadcom NIC) but the adapter in Device Manager displays the same problem.  When both NICs are plugged into a switch all lights blink and are green but there is no network traffic from server.  Note:  the teaming adapter is no longer showing in Device Manager either.

Any suggestions would be greatly appreciated
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I am not an expert in this field but I will give it a try.
First of all, when you want to change a configuration for testing purposes don't delete devices, just disable them.
I think that after you resolve the teaming configuration the NIC's will work properly.
You should have something on the system called Broadcom Advanced Control Suite (BACS). This is where changes should be made for the teaming configuration. It might not work properly because you deleted the driver so it might have to be reinstalled.
eloredoAuthor Commented:
Thanks for the reply!  Unfortunately there was never any BACS software installed.  This was a clean Windows 2008 R2 install and Windows automatically loaded the drivers for the two NICS as well as a teaming driver.

I have downloaded the latest drivers from Broadcom and installed but the teaming software is not showing up as well as the new drivers have the same problem.

It was mentioned that the problem could be with the original teaming software not being fully removed but I cannot find where or how to completely remove/reinstall it (Registry, etc.).
That is a problem. In Device Manager, right click on one of the NIC's and select Properties. Then select the Details tab. In the drop down menu see if there are any values listed for the upper and/or lower filters.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

eloredoAuthor Commented:
Just checked and cannot find any references to "upper and/or lower filters".   I did notice "Install Error" listed with a value of "The Parameter is incorrect.  00000057"
You didn't see anything in the list called Device Lower Filters or Device Upper Filters?
eloredoAuthor Commented:
Unfortunately no.  See attached screen shots.
Apparently they are not listed there anymore.
I could be way off but the only thing I can figure is that there is a driver file that got deleted when you removed the teaming device. If we knew the name of it then we can replace it. We might find it in the registry.
If you want to give it a try follow these directions to locate them. You are looking for either lowerfilters or upperfilters in the key associated with the NIC's that have a value assigned. Don't make any changes for now anyway, just note the value.
Click Start, type regedit in the Start Search box, and then click regedit in the Programs list.
If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.
In the Edit menu for Registry Editor, click Find..., enter LowerFilters, click to clear the Key and Data checkboxes, click to set the Match whole string only checkbox, and click Find Next.
Observe the registry keys where LowerFilters entries appear, and the data values (lower filter driver names).  
Search for additional LowerFilters entries by repeating step 2 above, or by pressing the F3 key, and observing each match found.
Repeat steps 2 through 5 for the UpperFilters registry value.
eloredoAuthor Commented:
Thanks for the suggestion but unfortunately due to the timing of everything, I just rebuilt the server and everything is up and running (no NIC teaming) now.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.