NIC teaming shows no adapters (server 2012 R2)

I think you are almost to the point of nuke and pave to fix the issue. (well not totally yet). 
What I would do is go into the device manager and remove all physical network adapters. Reboot and then let windows redetect and add them. This should fix the network communication issue. 
With that done, you need to answer what Rod-IT asked, how are you teaming these NICs? Are you using the computer manufacturer's program, the network adapter manufacturer's program or something else? Once you get beyond that what type of teaming are you trying to setup fail over (hot spare), LACP, switch assisted load balancing. Some load balancing settings need you to change the switch settings too. 
Also what brand of NICs are these? 

I have a server 2012 R2 system and on the NIC teaming it shows no adapters and windows network and sharing center shows none as well.
I do not want to have to reinstall :( I've tried rebuilding wmi repository and it doesn't work)
This topic first appeared in the Spiceworks Community

Similar Messages

  • NIC Teaming for hyper-v serve.

    I have installed windows server 2012 r2 on server. Server is having network adapters i have given static ip address to both nic's
    LAN1: - 192.168.0.100 & LAN2: - 192.168.0.101 after enabling NIC Teaming server have added one more adapter called
    "Network Adapter Multiplexor" after this above mentioned ip address are not responding to PING or any requests. Then i have given
    192.168.0. 102 ip address to Multiplexor and its started working.
    So my question do i need to give ip address to LAN1 &
    LAN2 or i can just create team and give ip address to Multiplexor
    Also if i installed hyper-v server on it will it give me failover thing for this machine.????
    Akshay Pate

    Hello Akshay,
    In brief, after creating the Teaming adapter (Multiplexor) you'll use it's address for future networking purposes.
    Regarding the lack of ping, I had the same "issue" and it seems like is block by the Microsoft code itself. Still couldn't find how to allow it.
    When digging into W2k12(&R2) NIC Teaming this two pages were very explanative and usefull:
    Geek of All Trades: The Availability Answer (by Greg Shields)
    Windows server 2012 Hyper-V 3.0 network virtualization (if you need more technical detail)
    Hope it helps!

  • Hyper-V Nic Teaming (reserve a nic for host OS)

    Whilst setting up nic teaming on my host (server 2012 r2) the OS recommends leaving one nic for host management(access). IS this best practice?  Seems like a waste for a nic as the host would hardly ever be accessed after initial setup.
    I have 4 nics in total. What is the best practice in this situation?

    Depending on if it is a single and the one and only or you build a Cluster you need some networks on your Hyper-V
    at least one connection for the Host to do Management.
    so in case of a single node with local disks you would create a Team with the 4 Nics and create a Hyper-V Switch with the Option checked for creating that Management OS Adapter what is a so called vNIC on that vSwitch and configure that vNIC with the needed
    IP Setting etc...
    If you plan a Cluster and also ISCSI/SMB for Storage Access take a look here
    http://www.thomasmaurer.ch/2012/07/windows-server-2012-hyper-v-converged-fabric/
    You find a few possible ways for teaming and the Switch Settings and also all needed Steps for doing a fully converged Setup via PowerShell.
    If you share more Informations on you setup we can give more Details on that.

  • Dynamic(Switch Independent) NIC Teaming Mode Problem

    Hi,
    We are using Switch Independent Dynamic distribution NIC Teaming configuration on Hyper-V 2012 R2 cluster. In the following graphs between 19:48 - 19:58 you can see clearly how dynamic NIC teaming mode badly affected the web servers response times.
    We have encountered this problem on the different cluster nodes that use different NIC chipsets Intel or Broadcom and configured with dynamic NIC teaming for VM Network connection.
    If we change the teaming mode as Hyper-V Port or remove NIC teaming for VM network as you can see from the graphic, response times are back to normal.
    Any ideas?
    Regards

    Hi,
    In the heavy inbound and outbound network load, If you are using the “Switch Dependent” 
    mode, you must configure your switch have the same teaming support mode.
    There have two scenario.
    “Switch Dependent” with LACP if your switch supports the aka 802.1ax.
    “Switch Dependent” mode with Static.
    Example of  Cisco® switch configuration when you using the “Switch Dependent” mode with “Static” mode:
    CiscoSwitch(config)# int port-channel1
    CiscoSwitch(config-if)# description NIC team for Windows Server 2012
    CiscoSwitch(config-if)# int gi0/23
    CiscoSwitch(config-if)# channel-group 1 mode on
    CiscoSwitch(config-if)# int gi0/24
    CiscoSwitch(config-if)# channel-group 1 mode on
    CiscoSwitch(config)# port-channel load-balance src-dst-ip
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows Server 2012 R2 RDP access too slow when user access

    HI Team,
    Recently installed Windows Server 2012 R2 Standard edition .
    The above server also promoted as Domain controller.
    I am trying to access the server VIA RDP from Windows 8 client machine access is toll slow and welcome screen shows for 2 to 3 minutes then only i can able to see my server desktop.
    Please advise me.

    We have two applications published on Rdweb.
    1.       MS
    Paint
    2.       Remote
    Desktop with option /v: <fqdn of the terminal server itself>
    MS Paint – can see local drives when logged on to the paint application
    Remote Desktop with parameters /v: <fqdn of the terminal server itself> - cannot see local drives when logged onto the full desktop view
    Mahesh

  • Issue while installing Ms Project Server 2013 on MS Server 2012 R2 with Sharepoint Server 2013

    Hello MS Support Team,
    I installed SQL server 2012 & Sharepoint server 2013 and after that the MS project Server 2013 is not installing on the same server -- pls hv a look the enclosed screenshot. sent at [email protected] and guide me to resolve it on priority.
    A windows poped up - Installation Error - This Project requires MS Sharepont Enterprise edition... (Which is not available on the MSDN Server)..only standard edition available.
    Please reply asap @ [email protected] - Call @ 0120471384
    Kind Regards,
    Vinay Bhardwaj
    Network System Administrator - GREC (IN)
    Rockwell Automation | A-66, Sector 64 | Noida | India
    LISTEN. THINK. SOLVE
    IP : 71384 | E : [email protected] | W : www.rockwellautomation.com

    Hi Siriosus,
    Indeed you do need Sharepoint Server 2013
    Enterprise for Project Server 2013.
    See article below where it is mentionned:
    Project Server 2013 requires the Enterprise edition of SharePoint Server 2013. Prior versions of SharePoint Server and SharePoint Foundation 2013 are not supported.
    http://technet.microsoft.com/en-us/library/ee662114(v=office.15).aspx
    Hope this helps,
    Guillaume Rouyre, MBA, MCP, MCTS |

  • Load Balancing and NIC Teaming

    Hi! i have been looking through lots of links and none of them actually can fully answer my queries.
    I am to do a writeup on load balancing and NIC Teaming, is there any1 that knows what are the commonly used load balancing and NIC Teaming methods, when to use each method, and the advantages and disadvantages of each method and the configuration for each
    method!
    Sorry its lots of questions but i have to do a detailed writeup!
    Many thanks in advance :D

    HI
    NIC Teaming - On a single server, you will have mutiple NIC. You can Team the NIC so that both NIC will act togather to provide better bandwidth and High avaliblity.
    Example : NIC 1 - 1 GB and NIC -2 1 GB so in Team it can act a 2 GB single NIC, If one fails speed will be reduced but it will have HA
    Loadbalancing : Two servers hosting same content:
    Example : Microsoft.com can be hosted in two or even more servers and a loadbalancer will be used to split load to each server based of the current load and traffic.
    No disadvantages

  • Static [Public] IP vs. DHCP Assigned IP [Router IP Allocation] on Server 2012 R2 Setup

    I am deploying a new server specifically for creating and managing VM's with Hyper-V. My testing environment includes a Dell T620 server with 3 each 1 Tb drives configured for Raid 5. My server has 2 Nics. I am installing Server 2012 R2 along with AD
    & Hyper-V Roles. I have a block of public IP's from my provider. My first question is related to how I configure a Nic to use a public IP. One option is to use DHCP to have an internal IP assigned and then once the IP is assigned, I log into my router
    and configure IP Address Allocation to assign the public IP network details to the DHCP assigned IP. I have used this method on a T610 testing server that uses the VMware ESXi Hypervisor with success. Option 2 is to actually input the public IP network details.
    I also have to ask the same question as to which method is better when it comes to the Switch. If any of the experienced engineers want to throw in additional advice or tips, that would be appreciated. My initial deployment has gone well but I feel like I
    can make it easier and more secure. Thanks in advance for the support.
    Gregory Woodruff
    St. Louis, Missouri
    LuckyWoody.com

    1. For servers static IP addresses are used.
    2. It is a good habit to use one nic for communication and one for management.
    3. DC should be single home server (otherwise you may have problems)
    4. Use split brain configuration for DNS if you really need it. Otherwise private subnet is used.
    5. Use firewall to prevent bad guys to enter your infrastructure.
    6. Use DHCP server for client computers only.
    7. DHCP on router is not used for AD clients, because these clients needs information on resouce records (to find DC).
    HTH
    Milos

  • Windows Server 2012 R2 NIC Teaming and DHCP Issue

    Came across a weird issue today during a server deployment. I was doing a physical server deployment and got Windows installed and was getting ready to connect it to our network. Before connecting the Ethernet cables to the network adapters, I created a
    NIC Team using Windows Server 2012 R2 built-in software with a static IP address (we'll say its 192.168.1.56). Once I plugged in the Ethernet cables, I got network access but was unable to join our domain. At this time, I deleted the NIC team and the two network
    adapters got their own IP addresses issued from DHCP (192.168.1.57 and 192.168.1.58) and at this point I was able to join our domain. I recreated the NIC team and set a new static IP (192.168.1.57) and everything was working great as intended.
    My issue is when I went into DHCP I noticed a random entry that was using the IP address I used for the first NIC teaming attempt (192.168.1.56), before I joined it to the domain. I call this a random entry because it is using the last 8 characters of the
    MAC address as the hostname instead of the servers hostname.
    It seems when I deleted the first NIC team I created (192.168.1.56), a random MAC address Server 2012 R2 generated for the team has remained embedded in the system. The IP address is still pingable even though an ipconfig /all shows the current NIC team
    with the IP 192.168.1.57. There is no IP address of 192.168.1.56 configured on the current server and I have static IPs set yet it is still pingable and registering with DHCP.
    I know this is slightly confusing but I am hoping someone else has encountered this issue and may be able to tell me how to fix this. Simply deleting the DHCP entry does not do the trick, it comes back.

    Hi,
    Please confirm you have choose the right NIC team type, If you’ve previously configured NIC teaming, you’re aware NIC teams usually require the assistance of network-side
    protocols. Prior to Windows 2012, using a NIC team on a server also meant enabling protocols like EtherChannel or LACP (also known as 802.1ax or 802.3ad) on network ports.
    More information:
    NIC teaming configure in Server 2012
    http://technet.microsoft.com/en-us/magazine/jj149029.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Server 2012 R2 Crashes with NIC Team

    Server 2012 R2 Core configured for Hyper-V. Using 2-port 10Gbe Brocades, we want to use NIC teaming for guest traffic. Create the team... seems fine. Create the virtual switch in Hyper-V, and assign it to the NIC team... seems fine. Create
    a VM, assign the network card to the Virtual switch... still doing okay. Power on the VM... POOF! The host BSOD's. If I remove the switch from the VM, I can run the VM from the console, install the OS, etc... but as soon as I reassign the virtual
    NIC to the switch, POOF! Bye-bye again. Any ideas here?
    Thank you in advance!
    EDIT: A little more info... Two 2-port Brocades and two Nexus 5k's. Running one port on NIC1 to one 5k, and one port on NIC2 to the other 5k. NIC team is using Switch Independent Mode, Address Hash load balancing, and all adapters active.

    Hi,
    Have you updated the NIC driver to latest?
    If issue persists after updating the driver, we can use WinDbg to analyze a crash dump.
    If the NIC driver cause the BSOD, please consult the NIC manufacture about this issue.
    For detailed information about how to analyze a crash dump, please refer to the link below,
    http://blogs.technet.com/b/juanand/archive/2011/03/20/analyzing-a-crash-dump-aka-bsod.aspx
    Best Regards.
    Steven Lee
    TechNet Community Support

  • Windows Server 2012 R2 - Hyper-V NIC Teaming Issue

    Hi All,
    I have cluster windows server 2012 R2 with hyper-v role installed. I have an issue with one of my windows 2012 R2 hyper-v host. 
    The virtual machine network adapter show status connected but it stop transmit data, so the vm that using that NIC cannot connect to external network.
    The virtual machine network adapter using Teamed NIC, with this configuration:
    Teaming Mode : Switch Independent
    Load Balance Algorithm : Hyper-V Port
    NIC Adapter : Broadcom 5720 Quad Port 1Gbps
    I already using the latest NIC driver from broadcom.
    I found a little trick for this issue by disable one of the teamed NIC, but it will happen again.
    Anyone have the same issue with me, and any workaround for this issue?
    Please Advise
    Thanks,

    Hi epenx,
    Thanks for the information .
    Best Regards,
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows Server 2012/2012R2 NIC Teaming Mode

    Hi,
    Question 1:
    In Windows Server 2012 the following teaming mode was recommended for Hyper-V NIC teams:
    Teaming mode: Switch Independent
    Load balancing mode: Hyper-V Port
    All Adapers Active
    In a session at TechEd 2014 it was stated that Dynamic is the new recommendation for Windows Server 2012 R2. However, a Microsoft PFE stated a few weeks ago that he would still recommend Hyper-V Port for Windows Server 2012 R2. What is your opinions around
    this?
    Question 2:
    We have a Hyper-V Failover Cluster which isn`t migrated to 2012 R2 yet, it`s running 2012. In this cluster we use Switch Independent/Hyper-V Port for the team. We also use converged networking, having 2 physical adapters bound to the NIC team, as well as
    3 virtual adapters in the management OS for management, CSV and Live Migration. Recently one of the team NICs failed, and this incident also caused the cluster membership on the affected node to go offline even though the other team NIC was
    connected. Is this expected behaviour? Would the behaviour be different if 2012 R2 with Dynamic mode was being used?

    Hello,
    As for question number 1:
    For Hyper-V workload it's recommended to use Dynamic with
    Switch Independent mode. Why?
    This configuration will distribute the load based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm will redistribute flows to optimize team member bandwidth utilization so individual
    flow transmissions may move from one active team member to another.  The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets so it takes steps to minimize that possibility.
    The receive side, however, will look identical to Hyper-V Port distribution.  Each Hyper-V switch port’s traffic, whether bound for a virtual NIC in a VM (vmNIC) or a virtual NIC in the host (vNIC), will see all its inbound traffic arriving on a single
    NIC.
    This mode is best used for teaming in both native and Hyper-V environments except when:
    1) Teaming is being performed in a VM,
    2) Switch dependent teaming (e.g., LACP) is required by policy, or
    3) Operation of a two-member Active/Standby team is required by policy. 
    As for question number 2:
    The Switch Independent/Hyper-V Port will send packets using all active team members distributing the load based on the Hyper-V switch port number.  Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port
    is affinitized to exactly one team member at any point in time. 
    In all cases where this configuration was recommended back in Windows Server 2012 the new configuration in 2012 R2, Switch Independent/Dynamic, will provide better performance.
    Microsoft recommend for a clustered Hyper-V deployment
    in Windows server 2012 to use Switch Independent/Hyper-V Port as you mentioned and to configure
    Hyper-V QoS that applies to the virtual switch. (Configure minimum bandwidth in
    weight mode instead of in bits per second and Enable and configure QoS
    for all virtual network adapters 
    Did you apply QoS on the Converged vSwitch after you
    created the team?? However Nodes are considered down if they do not respond to 5 heartbeats. The Switch Independent/Hyper-V Port does not cause the cluster to goes down if one NIC failed. The issue is somewhere else and not in the teaming mode
    that you choose.
    Hope this help.
    Regards,
    Charbel Nemnom
    MCSA, MCSE, MCS, MCITP
    Blog: www.charbelnemnom.com
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if
    a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Using NIC Teaming and a virtual switch for Windows Server 2012 host networking and Hyper-V.

    Using NIC Teaming and a virtual switch for Windows Server 2012 host networking!
    http://www.youtube.com/watch?v=8mOuoIWzmdE
    Hi thanks for reading. Now I may well have my terminology incorrect here so I will try to explain  as best I can and apologies from the start.
    It’s a bit of both Hyper-v and Server 2012R2. 
    I am setting up a lab with Server 2012 R2. I have several physical network cards that I have teamed called “HostSwitchTeam” from those I have made several Virtual Network Adaptors such as below
    examples.
    New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight -NetAdaptername "HostSwitchTeam" -AllowManagement $false
    Add-VMNetworkAdapter -ManagementOS -Name "Vswitch" -SwitchName "MgmtSwitch"
    Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
    When I install Hyper-V and it comes to adding a virtual switch during installation it only shows the individual physical network cards and the
    HostSwitchTeam for selection.  When installed it shows the Microsoft Network Multiplexor Driver as the only option. 
    Is this correct or how does one use the Vswitch made above and incorporate into the Hyper-V so a weight can be put against it.
    Still trying to get my head around Vswitches,VMNetworkadapters etc so somewhat confused as to the way forward at this time so I may have missed the plot altogether!
    Any help would be much appreciated.
    Paul
    Paul Edwards

    Hi P.J.E,
    >>I have teams so a bit confused as to the adapter bindings and if the teams need to be added or just the vEthernet Nics?.
    Nic 1,2 
    HostVMSwitchTeam
    Nic 3,4,5
             HostMgmtSwitchTeam
    >>The adapter Binding settings are:
    HostMgmtSwitchTeam
    V-Curric
    Nic 3
    Nic 4
    Nic 5
    V-Livemigration
    HostVMSwitch
    Nic 1
    Nic 2
    V-iSCSI
    V-HeartBeat
    Based on my understanding of the description , "HostMgmtSwitchTeam and
    HostVMSwitch " are teamed NIC .
    You can think of them as two physical NICs (do not use NIC 1,2,3,4,5 any more , there are just two NICs "HostMgmtSwitchTeam and
    HostVMSwitch").
    V-Curric,
    V-Livemigration , V-iSCSI ,
    V-HeartBeat are just VNICs of host  (you can change their name then check if the virtual switch name will be changed )
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Hyper-V vSwitch on a NIC-Team (Server 2012 R2) has limited connectivity

    Hi,
    I have two servers both running Server 2012 R2. One of these servers is serving as a DC and is working fine. The other is supposed to be a Hyper-V-Host, but I cannot get networking working on this system. Both systems have Hyper-V role installed. Both have
    2 NICs configured as a team. The team is configured as switch-independent, Hyper-V-Port, None (all adapters active). A Hyper-V-Switch using this team as external network is configured and is shared with the host operating system. This should work fine and
    does on one of the servers. On the other I get a warning sign stating limited connectivity. The server seems to sent packages but it receives none. Deleting the switch and simply using the team for network access works fine. So it has to be related to the
    switch. But I do not know what's wrong with it. Any ideas?
    Regards,
    Oliver

    Hi ogerlach_isw,
    Generally please don’t install others role on Hyper-V server, if your DC using NIC teaming, please break the teaming then monitor this issue again.
    More information”
    Everything you want to know about Network Teaming in Windows Server 2012
    http://blogs.msdn.com/b/virtual_pc_guy/archive/2012/12/07/everything-you-want-to-know-about-network-teaming-in-windows-server-2012.aspx
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Network adapters (NIC) doesn't show up in NIC Teaming manager

    We have been running Windows Server 2012 R2 for couple of months now with no major problems, but recently had to swap out one of the NICs. Unfortunately interfaces were not removed from Team before it was swapped out and that appears to have screwed up something
    in Windows NIC Teaming manager - NICs doesn't appear there anymore. Not even the NICs that were not touched.
    Network interfaces appear to be connected, no issues with drivers (screen shot from device manager), but they don't show up in NIC Teaming, any idea how to reset NIC Teaming manager and/or resolve this issue without reinstalling Windows?
    Thanks!

    Thanks for leading me the right direction!
    Looking around I found that one of  "invalid class" error causes is corrupted WMI.  Using this script provided by MS to Rebuild/Re-register WMI (different case/problem, but WMI is WMI...) resolved the issue with NICs not showing up:
    @echo off
    sc config winmgmt start= disabled
    net stop winmgmt /y
    %systemdrive%
    cd %windir%\system32\wbem
    for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
    wmiprvse /regserver
    winmgmt /regserver
    sc config winmgmt start= Auto
    net start winmgmt
    for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

Maybe you are looking for