Request a quote

iDRAC web interface not reachable? Check these in order

· Systems engineer, Fanxi Technology · Updated November 1, 2026 · 6 min read

Short answer

When the iDRAC9 web page will not open, first read the IP the iDRAC really has (front LCD, F2 > iDRAC Settings > Network, or racadm getniccfg from the host OS) and check which port it uses: Dedicated or a shared LOM. Then rule out VLAN mismatch, disabled IPv4, a duplicate IP, IP range filtering and a changed HTTPS port. If iDRAC itself hangs, run racadm racreset from the host or hold the System ID button for 16 seconds; to bypass the network entirely, plug a laptop into the front iDRAC Direct micro-USB port and browse to 169.254.0.3.

Written against: the Dell iDRAC9 User's Guide, the iDRAC9 RACADM CLI Guide (2024, firmware 7.x) and Dell KB articles for PowerEdge 14G to 16G

Rows of server racks in a data centre
Photo: “Datacenter Server Racks” by Carl Lender, via Wikimedia Commons, CC BY 2.0

What IP address does the iDRAC really have?

Most "iDRAC is dead" tickets end here: the controller is fine and sits on a different address than you expect. Read the address from the server, not from an old spreadsheet. On rack servers that were never configured, iDRAC9 uses 192.168.0.120 as its default static address unless DHCP is set.

  • Front LCD (on servers with the LCD bezel): the View menu shows the iDRAC IPv4 or IPv6 address.
  • At boot, press F2 and open System Setup Main Menu > iDRAC Settings > Network. You see Enable NIC, NIC Selection, IPv4 and DHCP on one page.
  • From the host OS with local RACADM (iDRAC Tools package installed):
racadm getniccfg
# check these lines in the output:
#   NIC Enabled     =1
#   IPv4 Enabled    =1
#   DHCP Enabled    =0
#   IP Address      =10.0.20.15
#   NIC Selection   =dedicated
#   Link Detected   =Yes
#   Active NIC      =Dedicated
getniccfg shows the address, the selected port and whether that port has link.

Is the cable in the port the iDRAC is set to use?

iDRAC9 talks either through its own dedicated RJ45 port or through one of the onboard LAN ports (LOM1 to LOM4) shared with the host. If NIC Selection says LOM1 and your management cable sits in the iDRAC port, or the other way round, the controller is unreachable even though everything looks plugged in.

SettingWhat it meansTypical mistake
DedicatedTraffic uses the port marked iDRAC on the rear panelCable is in an onboard NIC port instead
LOM1 to LOM4iDRAC shares that onboard port with the OSPort is on a switch VLAN without the iDRAC subnet
Failover NetworkSecond LOM used if the first loses link (shared mode only)Failover LOM not cabled to the same network
Auto Dedicated NICSwitches from shared LOM to Dedicated when the dedicated port gets linkA patch cable in the iDRAC port moves traffic away from the LOM you were using
racadm get iDRAC.NIC.Selection
racadm set iDRAC.NIC.Selection Dedicated

Does the switch port match the iDRAC VLAN and speed?

A VLAN mismatch gives you link lights and no traffic. If iDRAC has VLAN tagging on and the switch port is an untagged access port, frames arrive tagged and get dropped. If the switch port is a trunk and iDRAC sends untagged frames, they land in the native VLAN. Pick one model and make both sides agree.

racadm get iDRAC.NIC.VLanEnable     # 0 = untagged, 1 = tagged
racadm get iDRAC.NIC.VLanID
racadm set iDRAC.NIC.VLanEnable 0   # use with an access port
racadm get iDRAC.NIC.Autoneg        # 1 = auto-negotiation on (default)

Leave auto-negotiation enabled. A switch port forced to 100 Mb/s full duplex against an iDRAC on auto often ends in a duplex mismatch with heavy packet loss. The dedicated iDRAC9 port is 1 GbE, so a 10G-only switch port without 1G support shows no link at all.

Is IPv4 enabled and is the address unique?

Check that IPv4 Enabled =1. Someone may have disabled IPv4 while testing IPv6. Next, test for a duplicate address: power the server off at the wall, then ping the iDRAC IP. If something still answers, another device owns that address. On a DHCP network, look up the iDRAC MAC (shown on the LCD, in F2 and in getniccfg) in your DHCP leases instead of guessing.

racadm set iDRAC.IPv4.Enable 1
racadm setniccfg -s 10.0.20.15 255.255.255.0 10.0.20.1   # static
racadm setniccfg -d                                      # or DHCP
arping -I eth0 10.0.20.15   # from a Linux host on the same subnet: more than one MAC means a conflict

Why does the iDRAC answer ping but the web page will not load?

When ICMP works, the network path is fine and the cause is in the iDRAC web settings or your browser:

  1. HTTPS port changed. The default is 443. Read it with racadm get iDRAC.WebServer.HttpsPort and browse to https://<ip>:<port>.
  2. IP range filtering. With iDRAC.IPBlocking.RangeEnable set to 1, only addresses inside RangeAddr and RangeMask may log in. Check from local RACADM and widen or disable the range.
  3. Login blocking. After repeated failed logins iDRAC blocks the client IP for a short time. Wait a minute and use the right password.
  4. TLS mismatch. Old iDRAC9 firmware may only offer TLS versions or ciphers a current browser refuses. Very new firmware set to TLS 1.3 only can reject an old browser or RACADM client. Check racadm get iDRAC.WebServer.TLSProtocol and update the firmware.
  5. Browser cache and certificate. Try a private window or another browser and accept the self-signed certificate warning.
racadm get iDRAC.WebServer.HttpsPort
racadm get iDRAC.IPBlocking
racadm set iDRAC.IPBlocking.RangeEnable 0
racadm get iDRAC.WebServer.TLSProtocol

How do you reset a hung iDRAC without rebooting the server?

If the settings look right and iDRAC still does not answer, the controller may be stuck. Each of these restarts iDRAC without touching the host OS or your saved iDRAC settings. Allow one to two minutes before you test again.

  1. From the host OS: racadm racreset with local RACADM.
  2. With iDRAC Service Module installed: Invoke-iDRACHardReset on Windows (PowerShell) or Linux, for a controller that no longer answers RACADM.
  3. At the server: press and hold the System ID button (marked i) for at least 16 seconds, until the fans spin up to full speed and the LCD turns off.
  4. Last resort: shut the OS down, pull both power cords for a few minutes and power on again.

Do not run racadm racresetcfg as a fix. It returns iDRAC to factory defaults, which clears the network configuration and user accounts you are trying to reach.

How do you reach iDRAC with no network at all?

iDRAC Direct turns the front management USB port into a private network link to your laptop. On PowerEdge 14G, 15G and 16G (iDRAC9) it is the micro-USB port on the front panel; on 17G (iDRAC10) it is a USB-C port next to a wrench icon.

  1. Connect a USB to micro-USB data cable between the laptop and the front iDRAC Direct port.
  2. Wait for the laptop to get the address 169.254.0.4. No driver install is needed on current Windows or Linux.
  3. Browse to https://169.254.0.3 and log in with the iDRAC credentials from the pull-out information tag.
  4. Fix the network settings in iDRAC Settings > Connectivity > Network, then unplug.

If the laptop gets no link, check that the port mode is set to iDRAC Direct Only or Automatic under iDRAC Settings > Media and USB Port Settings, and turn off the laptop Wi-Fi so it does not route 169.254.x.x elsewhere.

Questions people ask

Why can I ping iDRAC but not open the web interface?

The network path works, so look at iDRAC itself: a changed HTTPS port, IP range filtering, a temporary block after failed logins or a TLS version your browser rejects. Check racadm get iDRAC.WebServer.HttpsPort and racadm get iDRAC.IPBlocking from the host OS.

Should iDRAC use the dedicated port or a shared LOM?

Use the dedicated port whenever you can. Management traffic stays off the production network, and you keep access when the OS driver or a LOM firmware update takes the onboard ports down.

Does racadm racreset reboot my server?

No. It restarts only the iDRAC controller and keeps its configuration. The host OS keeps running. iDRAC needs up to two minutes to come back.

What is the default iDRAC9 IP address?

On rack and tower servers the factory default is 192.168.0.120 if DHCP is not enabled. Over the front iDRAC Direct USB port the iDRAC is always 169.254.0.3 and your laptop gets 169.254.0.4.

Sources

  1. Dell KB: How to configure iDRAC9 and Lifecycle Controller network settings
  2. Dell KB: PowerEdge, how to use the iDRAC Direct feature
  3. Dell KB: How to reset the iDRAC on a PowerEdge server
  4. Dell: Integrated Dell Remote Access Controller 9 User's Guide
  5. Dell: Integrated Dell Remote Access Controller 9 RACADM CLI Guide (2024)

Read next

Need a server set up this way?

We set the iDRAC address and NIC mode you ask for before shipping and confirm it answers on the network, so the server is reachable when it arrives. If a unit from us is not reachable, send us the `getniccfg` output and we will work through it with you.

Request a quote

About Fanxi Technology, server supplier from China

Fanxi Technology (Dalian Fanxi Technology Co., Ltd., 大连梵西科技有限公司, Unified Social Credit Code 91210204MAE048TT6J, licensed for import and export) is a Dell Technologies Platinum Partner (Dell Technologies Partner Program, 2026) and an HPE Business Solution Provider for HPE and HPE Networking (2026). It is a China-based supplier of enterprise server hardware, exporting to Europe, the Americas and Africa from its base in Dalian. The company carries Dell PowerEdge, HPE ProLiant, Lenovo ThinkSystem, Huawei and xFusion systems, alongside rack and tower servers, enterprise storage and components such as PCIe graphics cards. Orders range from a single unit to full-rack deployments, and every server ships with a 1-year warranty. Fanxi sells on EXW Dalian terms. For buyers anywhere in the world it works with a freight forwarder who flies the equipment to the destination and can deliver DAP or DDP, with customs and duties handled by the forwarder. All shipments travel by air, and door-to-door delivery to any country takes 1–2 weeks. Fanxi replies to quote requests within 1 hour during business hours (Mon–Fri 09:00–19:00 Beijing time, UTC+8) and gives configuration advice to buyers who need help matching hardware to workloads. The company stays in contact with the buyer and the forwarder from the first quote until the order is delivered.