Knowledge Base

DRAC - How to Determine if an iDRAC Shared Physical NIC 1 is Connected on Remote Windows Server

This article provides information on how to determine if an iDRAC shared physical NIC 1 is connected on remote Windows Server


In some scenarios where a server is located in a remote facility (cannot get a hands-on view of server), the customer has access to the console of the system via RDP or Webex, but needs to verify if the Shared iDRAC port has a network cable plugged into it. Network Connections may state that Local Area Connection (LAC) is plugged in, but due to NIC enumeration issues, LAC may not actually be Physical NIC 1 on the server. In this situation, iDRAC connectivity will fail.


The root problem is that a NIC cable is not plugged into Physical NIC 1, not allowing iDRAC connectivity to the server.

To resolve this:

  1. Open Device Manager and check the Network Adapters container.
  2. Double-click each of the Network Adapters listed (Intel or Broadcom) to view the Properties of each NIC Device.
  3. Under the General tab, check "Location:" item to get the Bus:Device:Function of each NIC.
  4. Identify the Device with "PCI Bus 0" & "Function 0", this is Physical NIC 1 on the motherboard, which is sharing the iDRAC connection.
  5. Note the actual Device Name in Device Manager (e.g. Broadcom BCM5709C NetXtreme II GigE #3)
  6. Go to Network Connections and change the View to "Details"
  7. Find the Device Name and it's corresponding Local Area Connection assignment and if it is indeed plugged in. You may have to expand the Device Name column to view the whole Device Name.
  8. Verify that the port is attached to an active network by checking the "Status" column.

This is valid for Windows Server 2003 and Windows Server 2008. The release of Windows Server 2012 should resolve the issue of NIC enumeration and Local Area Connection 1 being connected to Physical NIC1.

Need more help?
Find additional PowerEdge and PowerVault articles

Visit and ask for support in our Communities

Create an online support Request

Article ID: SLN266203

Last Date Modified: 10/11/2017 08:15 AM

Rate this article

Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.