661FM-L onboard NIC

I bought yesterday the 661FM-L motherboard and replaced my old HP motherboard with that.
Got the system up and running fine everything works so far execpt the on-board LAN.
the device shows up in the network connections but says network cable unplugged.
I installed a second network card from linksys and that works fine.
I switched cables between the cards to make sure I don't have a bad cable and that is it not either.
I checked the bios and the onboard network card is enabled.
Got the latest driver and reinstalled those too.
I'm running out of ideas.
Anybody an idea what else to check or what it could be?
Did anybody ran into this issue?

Try removing the LAN connection in Windows Device Manager and then let Windows find it again and install the driver it wants to install
Also try jiggling the RJ45 connector in the LAN port. Maybe the cable connector is just not making good contact with the on-board LAN port.

Similar Messages

K7N2 Delta2 :: Onboard NIC Once Flawless, Now cannot find Network

Hello, and thank you for reading my Support Query!
Heres the Deal. For the past Couple of Months, I've had little to no problems with my K7N2D2. Everything worked to my expectations.
Until Last Night, was online, and downloading some Bittorrent Files when all my connections suddenly drop'd from Maximum to Nothing.
First Thought : ADSL Dropped or Router Stalled... So, I Restart ze Modem, Restart the Hub. All their Flashes go Normally, and I wait a few moments for everything to Synch Up. Then Tried refreshing google.com .. to No Avail, its -instantly- reporting it cannot find the address, yadda yadda.
2nd Thought : Oh, maybe Verizon's Service was interrupted... But No, I walk into the other room, where my Bro's Comp is at, and the Net is Fully Functional and Online. [ He also has a K7N2-D2 MB.. The Comp which im typing at right now]
Weirdness : I Cannot Connect to the Routers IP Address. I Cannot even Connect to any other the computers on the Network. [ This all Used to Work Perfectly, Small Home Network of 3 Comps, With Lots of Read Only Shared Folders, for Music / Movies ]
Continued Wierdness : Everything in the Device Manager seems to Say everything is in perfect working Order, and I Can Ping Local Address [ 127.0.0.1 ] With No Problem. I Tried Pinging the Router, but it couldnt find Destination?
ipconfig/all Reports that, DHCP is Enabled, AutoConfig is Enabled, but it cant find the Gateway or DHCP Server.
What is going on? Did I Fry the NIC with too Many Torrents?
I Tried Hooking up a Old D-Link NIC Card I've had around for awhile, Not Sure why but it didnt want to Work.. Maybe cuzz its been sitting in storage for years.
Help is greatly appreciated, Is there anyway I Can run a diagnostic on the Onboard NIC? Yarr.

Hi all.
I'm new here, but have to write, coz I have exactly the same problem, like Nookovski.
I'm using my K7N2 D2platinum for more than 1 years, without any problem, using the onboard LAN for internet (connected to ADSL cable modem), and another Ethernet card for internal LAN.
2 days ago, I was playing network game with friends, when suddenly my connection was lost. I tried to reach homepages, but no avail. Try to ping some common addresses, nothing happens, 100% lost.
I rebooted, and saw, that my ip address for netconnection changed to 163... etc. This is weird, coz originally my ISP always give some 80... etc from DHCP.
I tried renew my ip, no success.
Called my ISP, they said, they can see my modem, but can't see my PC. I have to plug the cable to my another ethernet card for a moment - I did it, and they saw my pc in this case. They adviced to reinstall my onboard NIC driver. OK, perhaps later.
After all, I found an old Ethernet card (Realtek family) in my case, so I installed it. After a quick reboot my netconnection was fine through this new card. So no network problem on ISP side, there is something with my onboard LAN.
I tried to uninstall / remove the driver from hardware settings panel, but the window freezes. If I reboot in safe mode, and try to remove again, windows says : cannot remove, device is needed for operation. (or smth like this)
I tried reinstall LAN components from the latest MSI driverset, but nothing changed. I think it cannot overwrite the old (damaged?) files.
Now I'm using 2 PCI eth.card, one to connect with another PC, and one for internet. I disabled the onboard LAN from bios. But this is annoying, I don't understand what happend from one minute to another, and I would like to use my integrated NIC!
I found some posts here, advising to set the MAC address in bios manually, regarding to a sticker on the mobo, but I don't have such an option in BIOS.
What should I do now? Are there any solution?
Thanx!

KT6V 7021 - OnBoard NIC "dead" after BIOS 2.00 update ... any thoughts?

Hi!
Just flashed KT6V BIOS 2.00 and now my onboard nic suddenly stopped working.
The network adapter gets recognized by Windows as usual, but although I do get a dhcp lease from my server I'm unable to connect to any share on it. It's also impossible to surf the web or to simply ping any local/remote host. If I try to connect to the system from any other workstation on the lan it doesn't work either.
The network status only shows a great amount of sent packages - caused by AVAST! as it tries to look for an update on boot - but only "0" received.
I flashed the BIOS from the emergency diskette and did a CMOS clear (Jumper) afterwards. And yes, I did disconnect my PSU from the wall socket.
Since I need network access to the system I tried stepping back to BIOS 1.90 but with no avail - the onboard nic doesn't receive a single paket after it has got it's dhcp lease.
Any clue what might be wrong and how I'm able to get my nic back to work?
Thank you in advance for any useful help.

Hi Fredrik.
Quote
So if you were to downgrade BIOS problems would go away, right?
I have already downgraded to BIOS 1.90 and the problem stayed the same - the onboard nic is still dead beef.
Quote
When clearing CMOS there can be no el. left in your system, so unplug power cable etc.
As mentioned in my first post I _have_ unplugged the power cord from the wall socket.
Quote
If the new BIOS would affect NIC card... Hm, it is hard to see quite how.
I can't think of any reason either, however, the nic went dead after updating to BIOS v2.00. I assume that there must be some kind of "network code" inside the bios which has to do with the onboard nic - otherwise I'm unable to explain why the MAC address suddenly changed to "11:22:33:44:55:66". If I would only have a clue on how to access and/or flash the nic ... ???
Quote
Is there any error marks for the nic in say Device Manager, if you get that far?
Nope, there is no question or exclamation mark on the network card in the device manager. Windows thinks the card is working, but in reality it isn't. As already stated: No traffic from/to the network.

Onboard NIC, KT4V MS-6712

Hi there,
When i try to connect to the internet with the onboard nic of my KT4V MS-6712 i get the error message "one of the networkcables is not connected".
With an sepperate nic i don't have any problems.
Is there some setting i did forget?
Nic is already enabled in the bios !
I have 3 machines behind an Edimax router with a cable connection.
System specs:
KT4V MS-6712
AMD AthlonXP 1600+
TwinMos 256Mb PC2100
Hercules 3D Prophet 128Mb
Creative Live! 5.1
Maxtor 60Gb 7200rpm
Q-Tec PSU 550 watt
OS Win XP pro

I have the same problem on my ms-6712, the onboard LAN doesn't seem to work correctly, if I connect the network cable to the onboard LAN the lights flash on the modem and the board but I can't get an IP address for the LAN. Although it works fine on my PCI NIC. Very strange!
I've tried, in a desperate attempt, to use a cross over cable but that didn't work either. Although it shouldn't work with a cross over cable anyway.
If anyone has an answer for this one I'd sure like to know!

Installing driver for onboard NIC

I'm new to Solaris and have a question as to how to install drivers for my onboard NIC. I found drivers that might work but I don't know what to do with them. Do I use the tar command? Will it put it in the right directory that way or do I need to move it somewhere else first.
If the drivers work, can I then set it up for DHCP? I've read a little bit about it. Will this work: ifconfig <interfacename> auto-dhcp?

Before this gets completely out of hand, like a recent thread,
let's get a few things out of the way.
What hardware do you have? Brand? Model?
What precise Ethernet chipset do you have?
Integrated to the systemboard? Add-on card ?
If this is some sort of a PC, have you checked the
Solaris Hardware Compatibility List (HCL)
http://www.sun.com/bigadmin/hcl/data/sol/
and have you compared your hardware to what's on that list ?
Generally speaking, there is no such thing as "maybe" or "might work"
when you are speaking of driver software packages.
They would be correct or they would be wrong.
What driver software are you considering?
If you downloaded it, provide the link.
There should be a README file with the software, even if it's not named "readme".

Onboard NIC (realtek) 785GT-E63

As many in newegg have noticed about this mainboard - the onboard NIC will lose connection (timeouts) every so often, and it's quite frustrating. Finally , i just popped in an old Linksys PCI NIC and it's doing great, but i would love to have the extra room by using the onboard NIC. It appears, from what I have read, that only the original driver for W7_64 bit actually works correctly, and every subsequent driver after that has the same timeout issues, and it does not only affect this MSI board - it has also affected a few others (AMD AM2+/AM3). I guess my question is, since i lost the original disk lol, is there anyone that can point me to the original driver included with the mainboard CD (W764 bit) ? I have been out of the PC building scene for about 2 years, but i do know what i'm doing, how to read manuals etc.... and search known issues, and indeed - this is a very well known issue with this particular board, and it is my first MSI, usually using Giga or Asus, other than this issue, I love the board.
Basic Specs AMD PHII 840/8GB Patriot DDR2_1066/ 600W PSU/ nvidia GTX260/W764

Well, as i suspected - a reformat, with W7 using an older driver as default, about two years old, likely a Vista driver works fine now. I just need to remember to not allow MS update or DL any new drivers for this NIC. :D

K8n neo2-f nf3 ultra board - onboard nic problem? Please post your experiences

I just ordered the k8n neo2-f nf3 ultra board, with a venice 3500+ chip, from newegg. I saw various posts on the mobo, however, from people who said the onboard nic doesn't work right out of the box, that they had to go in and manually enter the mac address in Windows that they retrieved from a sticker on the parallel port.
I can deal with a problem like that easily, but I find it hard to believe MSI would ship such a defective board design as that. Is this really the commonplace experience with this board? Please post your experience with this board if you've used it or had experience with it

Quote from: Scubahard on 15-September-05, 13:22:52
Okay I typed my address under the "network addapters" and I still do not have any internet access. I even tried to reboot...and nothing. My computer knows when I have a cable hooked up to the port. It will tell me "network cable connected" or "network cable unplugged." I hooked up my netgear network card and I was able to get online.
Should I be messing with the "authentication" tab and/or the IEEE 802.1x setting?
My windows 2k computer has a broadcast "node type" while me K*N Neo2 board does not have a line for node type (under ipconfig). Also my XP computer does not have a line that will tell me the values for: DHCP Server and DNS Servers. It also has a no value for the default gateway line. It DOES have a value for the "Connection Specific DNS Suffix". It is for comcast.
I hope all this is not too confusing. I was trying to list all the questionable settings. What should I try next?
Thanks!
Well, if you're wondering about the 'dhcp server', 'dns servers', 'default gateway', etc., that is all in the 'Network Connections' folder which can be reached from the Control Panel. To get to those settings, you right-click on the 'local area connection' that corresponds to the onboard lan, and click 'properties'. Then, select 'network protocol(tcp/ip)' in the list of networking components and click the 'properties' button. That will bring up the set of tabs where you can set those properties (although there is no 'dhcp server' address setting, just the option to either specify an address or use dhcp to automatically assign an address).
I get the impression, though, that you're saying if you slap in a pci network card, it connects right away, so I doubt any of those settings are needed (unless you left out the part about going into the tcp/ip settings for the pci nic and specifying an address, etc., which I doubt you did). Have you considered contacting msi tech support on the problem? If it's a new board, I'm sure you're entitled to free tech support. It seems like, with all of the chatter on these boards over this issue, they should be well aware of it and be familiar with the ways to 'fix' it.

Unable to achieve Gigabit speeds with onboard NIC (iMAC Intel based)

Hi,
I've recently noticed that my iMAC's built in 10/100/1000 NIC is only negotiating up to 100mb. I have a direct (cat5e straight through) connection from the iMAC to a 10/100/1000 port on an Airport Extreme Base station.
I've tried several different (known good) straight through ethernet cables and I either get NO link or at most 100mb. I'm starting to think that the NIC might be flaky of failing because during a few tests with different cables, I got link after a very long delay. Close to a minute or more after plugging in the cable.
Before I call Apple tech support, I figured I'd check the forum to see if this is a known issue or if anyone else has seen this.
- Some more specs of my system....
20" iMAC (Intel based)
3 gig DRAM
OS 10.5.2
Thanks...

I'm seeing (within the Network Utility) when I select the onboard ethernet adapter that the speed is 100mb.
I've been trusting this output mainly because if I leave the Network Utility screen open and unplug or re-plug the cable back in, the speed <value> disappears and then re-appears once the speed (I'm assuming) has been negotiated.
Additionally, I've just checked the Network Utility on my Powerbook G4 (here at work), and it shows the wired ethernet speed to be (1G) as opposed to (100mb). I can think of no logical reason why my iMAC's ethernet port would be negotiating to 100mb unless either the NIC is truly flaky or the AEBS needs to somehow be configured accordingly.
Thanks. Let me know if you have any other thoughts..

Problem with NIC and Firewire on MSI 865PE NEO2-PFISR

Hi, I have lots of trouble getting the network adapter on the MSI 865PE NEO2-PFISR to work.
The NIC's LED indicators doesnt even light up when I plug in a network cable,
and in windows (win 2003 server) it doesnt find the adapter at all.
The NIC is displayed in the bios, and I have the option to disable it,
but it is enabled.
I have even reinstalled windows 2003 server to try to get the NIC to work.
I have upgraded the bios to v3.8 via live update, with no problems, although the
firewire-option on the same page in the bios is still gone, it doesnt detect the
firewire at all(!).
I have also tried several other NIC's (a 3COM 3C905B TX and a 3C905B TX XL
PCI adapter). The 3C905B TX worked fine for a while, and then it started saying in
windows that a network cable was unplugged, and began to try 10mbit, 100mbit
lots of retries, now it doesnt work at all.
I swapped tp-cables and changed the ports on the network switch (which there is
also other computers attached to which doesnt have any problems) and that didnt
made any difference.
It seems that the whole pci bus is long gone, and maybe the onboard NIC is
attached to this same pci bus?
Strange also about the firewire-controller which isnt detected anymore.
The USB devices work, and even a 3com usb wlan adapter works well.
I have tried to reset the bios several times without that making a difference.
Anybody have a clue to point out here?
Cheers!

Quote
Originally posted by Raven
you could try and flash to an older bios
I tried most anything on flashing bios, both to a lower and a higher version.
I returned the motherboard to the reseller and got a new motherboard as a replacement. This doesnt have all the same problems. At first it didnt post at all, indicating to red lights on the diagnosis.
Then I was so pissed I hadnt touched the computer in a week, and just tried to use it a few days ago, and it seemed to work all ok. I used it for a few hours, and then it locked up.
When I powered it up again, the lights on the integrated adapter was out. At first it seemed to work to take the agp card a little out of its slot, as if it was unaligned or something. Used it for a few more hours.
Then I plugged in the sound cables (5.1 sound with 3 cables), and with the last cable, the network darkened out AGAIN!!
In the bios it still indicates that the network is enabled, firewire is enabled etc.
I twisted the network cable, and for a few microseconds I get a orange light, not the usual green light. Now this has stopped too.
I see other also have problems with these symptoms so I guess I've got another black monday card.
I will return this card too, and ask the reseller to get a card of another brand.

Nic transfers out but can't receive packets. Need (IRQ?) help.

The other day, I was having trouble with an Intel board with an on board Realtek nic. (see http://forum.java.sun.com/thread.jspa?threadID=5282653&tstart=0)
I'm having a similar problem now with a Gigabyte 8i865GME-775 with an Intel 8550 onboard nic.
The interface is plumbed, up, running and properly configured as iprb0 once I added the appropriate line in /etc/driver_aliases which was irpd "pci8086,1051"
I did some snooping around in logs and I noticed that packets are going out but there are no packets coming in according to kstat iprd.
I tried apci_user_options = 0x2 as well as 0x4, 0x8 and 0. Didn't seem to make a difference. Is there something else besides just rebooting to do? I also tried the two set pcplusmp:apic_forceload = -1 and set pcplusmp:apic_use_apci = 0 separately without any luck.
I administer the machines I use to test and develop on so my administrative talents are obviously lacking and I'm in need of help with this.
There seems to be a shared resource conflict indicated by this line in dmesg
pcplusmp: [ID 637496 kern.info] pcplusmp: pci8086,1051 (iprb) instance 0 vector 0x14 ioapic0x2 intin 0x14 is bound to cpu 1
The first time I saw it I was pretty sure it was cpu0 with the same vector.
According to the POST messages, the IRQ assigned to the nic card is 10, which doesn't seem to conflict with any of the other pci devices listed at that time. Is there a way to resolve this conflict from within Solaris? Or at least a way to view the currently assigned IRQ addresses? What's the relationship between vectors and irq's?
I'm going to disable some of the devices that are not needed to see if that helps. But I didn't find any way to change the irq of the nic or the cpu in this Award Bios.
There are a lot of great cutting edge features in Solaris 10, but these types of problems seem to have been plaguing people since at least 2003 from what I've seen. The last time I even worried about IRQ's, Intell processors came in two flavors SX and DX, and 9600bps was really fast. This seems to be a problem with the way Solaris 10's PnP code and not with the drivers.
Is there anything else that can be done to get this resolved?

Had to post this first thing in the morning because I'm all confused.
First, mother board is actually GA-8i865GME-775-RH. The onboard nic is EP82562G chip (10/100Mbit) which I believe is also referenced as just 82562G by Intel.
From prtpicl for the device I get:
pci1458,e000 (obp-device, 70000001c4)
:DeviceID     0x0
:UnitAddress     1
:device_id     0x1051
:vendor-id     0x8086
:revision-id     0x2
:class-code     0x2000
:unit-address     8
:subsystem-id     0xe000
:subsystem-vendor-id     0x1458
:min-grant     0x8
:max-latency     0x38
:interrupts     0x1
:devsel-speed     0x1
:fast-back-to-back
:power-consumption     01 00 00 00 01 00 00 00
:model     Ethernet controller
:compatible     (70000001cfTBL)
| pci8086,1051.1458.e000.2 |
| pci8086,1051.1458.e000 |
| pci1458,e000 |
| pci8086,1051.2 |
| pci8086,1051 |
| pciclass,020000 |
| pciclass,0200 |
:reg
From http://www.pcidatabase.com/ I found,
8086 is Intel
1051 is PRO/100 VE Network Connection
/boot/solaris/devicedb/master lists iprb when I grep for "PRO/100 VE". iprb plumbed but isn't working. From here http://blogs.sun.com/coolzephyr/date/200704 it's listed as ife
On another Sun Blog and a couple other sites I saw the pci1458,e000 part refered to Syskonnect and the skge driver. On other's that id series was also linked to nge, rtls, rge and gani. So I'm not even sure if I'm using the correct driver. Intel no longer seems to have Solaris drivers for the Pro/100 VE chips, the link to Syskonnect is old and broken and I'm not sure what their actual product is.
In /etc/driver_aliases and /boot/solaris/devicedb/master for pci8086,1005
But if that's the case, why wasn't it detected during the installation?
I tried loading the nge, rtls, rge and even e1000g drivers just in case. devfsadm failed to attach them.
I went back to iprb. Made sure /etc/driver_aliases and /boot/solaris/devicedb/master reflected the correct pci8086,1051 location.
iprb0 gets plumbed but "no MII link detected" still shows up on boot.
I'm at a complete loss.

Replaced NIC and cannot run Windows update

Greetings - I disabled the onboard NIC and installed a Intel Gigabit CT PCI-E Network Adapter EXPI9301CTBLK. On reboot, Win7 found the NIC and everything appeared to function normally.
However, when I try to run Windows Update or update Windows Defender, which worked the previous day, I get the error code: 0x80248007.
I updated the NIC driver to Driver_Version: Driver ver 12.7.27.0 date: 5/15/2013 - No help.
I ran the fixit tool from - http://support.microsoft.com/kb/958046/en-us - No help.
I renamed the folder SoftwareDistribution/Download folder to Download.old - No help.
I asked Intel Support if they were aware of this - They suggested contacting Microsoft.
OS: Win7 Pro 64bit
I suspect the NIC is causing the the problem obviously and hate to remove the NIC. Anyone have a suggestion on how to resolve this?
Thank you

Hi,
According to the error code, this problem occurs when some files in the Windows Update are missing, or when the Microsoft Software License Terms cannot be located by Windows Update.
Microsoft already provide a fixit tool to fix this problem and you can refer to the link below to download and intall it to fix this problem for test.
Windows Update error "0x80248007":
http://support.microsoft.com/kb/958046
Roger Lu
TechNet Community Support

VMM 2012 sp1: unable to create a logical switch on team with different nics (bug?)

Hyper-V Host is HP Proliant G7 with 4 onboard nics and additional (different) 4-port adapter, all 1Gbit. Server 2012 with latest updates.
VMM 2012 is sp1 with latest updates, server 2012 running in a vm.
When I create a logical switch with teamed uplink port profile in VMM, the job builds the team but fails to create the vswitch when ports from both onboard nics and adapter is used.
I am able to create a vswitch manually on the team if I do it directly on the host.
If the team is created on either purely onboard nics or purely adapter nics, the logical switch creation succeeds.
In short terms: I am able to create a vswitch based on a server 2012 team with different nics, but not a logical switch. Why?

I have tried assigning both nics in one step, and one by one. When I create the logical switch team with only one nic it succeeds, but then fails when I add the second (unless it is similar to the first).
Error in VMM is
Error (2912)
An internal error has occurred trying to contact the dkfuzhv01.mia.local server: : .
WinRM: URL: [http://dkfuzhv01.mia.local:5985], Verb: [GET], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/ErrorInfo?ID=1010]
Unknown error (0x80041001)
Recommended Action
Check that WS-Management service is installed and running on server dkfuzhv01.mia.local. For more information use the command "winrm helpmsg hresult". If dkfuzhv01.mia.local is a host/library/update server or a PXE server role then ensure that
VMM agent is installed and running.
If I add the second non-similar team member from the host itself, I get this error from nic teaming wizard
Validation failed and changes to the system are rolled back
It is not a question of losing connection (been there), management interface is on a different team. And it also fails when second team member is added directly on the host...
So far I will stick to the conclusion that my problem is with logical switch and different nics :)
Oh, by the way nics are HP NC382i (Broadcom) and NC365T (Intel)

3-Com NIC Card Networking Problems on Solaris 10 (x86)

Hi,
I have Solaris 10 OS installed on a PC. I am having trouble getting my machine to ping other machines on the same network. I have executed the following commands:
#ifconfig elxl0 plumb
#ifconfig elxl0 192.168.100.181 netmask 255.255.255.0 up
When I try to ping another machine on the same lan, I don't get a response. I have even did a the sysconfig command and reconfigured my networking and it still does not work. I have tried different network cable as well. I have looked in the master file. I see the driver for my NIC, so I know it is supported by Solaris 10. Can anyone help me?

Here is some more info on my problem and a couple of things I have tried to do to resolve the issue :
I executed the command "prtconf-pv". I found information on my NIC Card, which is a 3-Com 3C905B-TX Etherlink XL 10/100. I found my vendor id - 10b7 and my device id - 9055. I then checked "driver_aliases" file to see if I could find an entry in this file and I did see my vendor id and device id. I would then conclude that Solaris knows my PCI vendor/device-id combination and maps them to elxl driver.
I have also tried a different cable that i know works and still nothing.
I also found from research in Sol. 10 that there is file in addition to hosts, hostname.elxl0, defaultrouter that has to be modifed. That file is ipnodes. I checked the file, and my ip address / hostname is noted in the file. Is it possible I have a bad NIC? I thought about swapping it out for another one that I know works, but it is an onboard NIC. Well, if anyone has and additional info, I would greatly appreciate it.

Installing FA311 NIC in Solaris 10

Since my onboard NIC won't work I've installed a Netgear FA311 NIC PCI card. I downloaded the suggested driver (SFE-2.2.0) which is on the compatibility list and added the associated links. Now when I go to "/usr/ccs/bin/make install" it comes back with "make: Fatal error: Don't know how to make target 'install' ".
Does this look familiar to anyone?

I actually got the driver from Sun Tech Support but that's as far as they would help me. It's available from http://homepage2.nifty.com/mrym3/taiyodo/sfe-2.2.0.tar.gz.
Yes there is makefiles in the directory where I'm running it.
Ecurb
Message was edited by:
ecurb

PS Script to Automate NIC Teaming and Configure Static IP Address based off an Existing Physical NIC

# Retrieve IP Address and Default Gateway from static IP Assigned NIC and assign to variables.
$wmi = Get-WmiObject Win32_NetworkAdapterConfiguration -Filter "IPEnabled = True" |
Where-Object { $_.IPAddress -match '192\.' }
$IPAddress = $wmi.IpAddress[0]
$DefaultGateway = $wmi.DefaultIPGateway[0]
# Create Lbfo TEAM1, by binding “Ethernet” and “Ethernet 2” NICs.
New-NetLbfoTeam -Name TEAM1 -TeamMembers "Ethernet","Ethernet 2" -TeamingMode Lacp -LoadBalancingAlgorithm TransportPorts -Confirm:$false
# 20 second pause to allow TEAM1 to form and come online.
Start-Sleep -s 20
# Configure static IP Address, Subnet, Default Gateway, DNS Server IPs to newly formed TEAM1 interface.
New-NetIPAddress –InterfaceAlias “TEAM1” –IPAddress $IPAddress –PrefixLength 24 -DefaultGateway $DefaultGateway
Set-DnsClientServerAddress -InterfaceAlias “TEAM1” -ServerAddresses xx.xx.xx.xx, xx.xx.xx.xx
Howdy All!
I was recently presented with the challenge of automating the creation and configuration of a NIC Team on Server 2012 and Server 2012 R2.
Condition:
New Team will use static IP Address of an existing NIC (one of two physical NICs to be used in the Team). Each server has more than one NIC.
Our environment is pretty static, in the sense that all our servers use the same subnet mask and DNS server IP Addresses, so I really only had
to worry about the Static IP Address and the Default Gateway.
1. Retrieve NIC IP Address and Default Gateway:
I needed a way to query only the NIC with the correct IP Address settings and create required variables based on that query. For that, I
leveraged WMI. For example purposes, let's say the servers in your environment start with 192. and you know the source physical NIC with desired network configurations follows this scheme. This will retrieve only the network configuration information
for the NIC that has the IP Address that starts with "192." Feel free to replace 192 with whatever octet you use. you can expand the criteria by filling out additional octects... example:
Where-Object
$_.IPAddress
-match'192\.168.' } This would search for NICs with IP Addresses 192.168.xx.xx.
$wmi
= Get-WmiObject
Win32_NetworkAdapterConfiguration
-Filter "IPEnabled = True"
|
Where-Object {
$_.IPAddress
-match '192\.' }
$IPAddress
= $wmi.IpAddress[0]
$DefaultGateway
= $wmi.DefaultIPGateway[0]
2. Create Lbfo TEAM1
This is a straight forward command based off of New-NetLbfoTeam. I used "-Confirm:$false" to suppress prompts.
Our NICs are named “Ethernet” and “Ethernet 2” by default, so I was able to keep –TeamMembers as a static entry.
Also added start-sleep command to give the new Team time to build and come online before moving on to network configurations.
New-NetLbfoTeam
-Name TEAM1
-TeamMembers "Ethernet","Ethernet 2"
-TeamingMode SwitchIndependent
-LoadBalancingAlgorithm
Dynamic -Confirm:$false
# 20 second pause to allow TEAM1 to form and come online.
Start-Sleep
-s 20
3. Configure network settings for interface "TEAM1".
Now it's time to pipe the previous physical NICs configurations to the newly built team. Here is where I will leverage
the variables I created earlier.
There are two separate commands used to fully configure network settings,
New-NetIPAddress : Here is where you assign the IP Address, Subnet Mask, and Default Gateway.
Set-DnsClientServerAddress: Here is where you assign any DNS Servers. In my case, I have 2, just replace x's with your
desired DNS IP Addresses.
New-NetIPAddress
–InterfaceAlias “TEAM1”
–IPAddress $IPAddress
–PrefixLength 24
-DefaultGateway $DefaultGateway
Set-DnsClientServerAddress
-InterfaceAlias “TEAM1”
-ServerAddresses xx.xx.xx.xx, xx.xx.xx.xx
Hope this helps and cheers!

I've done this before, and because of that I've run into something you may find valuable.
Namely two challenges:
There are "n" number of adapters in the server.
Adapters with multiple ports should be labeled in order.
MS only supports making a LBFO Team out of "like speed" adapters.
To solve both of these challenges I standardized the name based on link speed for each adapter before creating hte team. Pretty simple really! FIrst I created to variables to store the 10g and 1g adapters. I went ahead and told it to skip
any "hyper-V" ports for obvious reasons, and sorted by MAC address as servers tend to put all thier onboard NICs in sequentially by MAC:
$All10GAdapters = (Get-NetAdapter |where{$_.LinkSpeed -eq "10 Gbps" -and $_.InterfaceDesription -notmatch 'Hyper-V*'}|sort-object MacAddress)
$All1GAdapters = (Get-NetAdapter |where{$_.LinkSpeed -eq "1 Gbps" -and $_.InterfaceDesription -notmatch 'Hyper-V*'}|sort-object MacAddress)
Sweet ... now that I have my adapters I can rename them into something standardized:
$i=0
$All10GAdapters | ForEach-Object {
Rename-NetAdapter -Name $_.Name -NewName "Ethernet_10g_$i"
$i++
$i = 0
$All1GAdapters | ForEach-Object {
Rename-NetAdapter -Name $_.Name -NewName "Ethernet_1g_$i"
$i++
Once that's done Now i can return to your team command but use a wildcard sense I know the standardized name!
New-NetLbfoTeam -Name TEAM1G -TeamMembers Ethernet_1g_* -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false
New-NetLbfoTeam -Name TEAM10G -TeamMembers Ethernet_10g_* -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false

661FM-L onboard NIC

Similar Messages

Maybe you are looking for