1 Rookie
•
2 Posts
0
61
August 5th, 2025 16:48
iDRAC Direct setting wrong IP on Mac
I am attempting to connect to one of our R740xd PowerEdge Servers using iDRAC Direct and a MacBook Pro 15 2019. When I connect to the server using the USB-C to Micro-USB cable and turn off WIFI the network interface gets assigned a 169.254.x.x address but it is never 169.254.0.4 as it should be according to the documentation.
Things we have tried so far:
Different Cable
Different Server
Setting a Static IP (169.254.0.4)
Deleting the Interface & Re-adding it
Resetting Mac NVRAM
None of these things have resolved the issue and the iDRAC Direct works with newer Macs. Does anyone have any ideas what the issue could be?
Thanks!
No Events found!
DELL-Joey C
Moderator
•
4K Posts
0
August 12th, 2025 02:06
Hi,
There are occasions that if the system is unable to obtain an IP address, hence it will also automatically assign themselves an IP address, which you are seeing, 169.254.x.x. I think it's called APIPA, if I'm not mistaken. Hence, this can be resulted from lack of driver in the OS system.
DELL-Joey C
Moderator
•
4K Posts
0
August 6th, 2025 07:01
Hi,
At first, I thought iDRAC direct might not be compatible with macOS, but you did manage to try newer Macs, and it's working fine. I'm leaning towards on the OS requirement level. I've very little knowledge on Macs, what's the OS version that you're on the Pro 15?
In the device list, iDRAC did add a USB network adapter in the laptop right? Is the LED on the iDRAC direct lid when it is connected to the laptop? Have you tried using Micro-USB to USB type A?
For Windows, the driver of RNDIS. I've tried googling, MacOS did not release the driver for RNDIS. This probably why the newer Macs can connect whilst the older Pro 15 couldn't.
adsmall
1 Rookie
•
2 Posts
0
August 11th, 2025 21:13
I'm running Sequoia 15.5.
Yes the iDRAC did add a USB network adapter and the LED on the iDRAC direct did light up when connected to the laptop. I tried using a micr-usb to usb-a with the same result.
It does sound like it could be a driver issue. What's strange though is that it assigns the device an IP, just not the right one. Almost like there is a race condition.