Reference Guide

17 No Restrictions | iDRAC Access via Host Operating System
“The site can’t be reached.”
Reason
The Microsoft Windows service “IP Helper” is required for this feature to function. Ensure this service is
running on your Managed Node, where iDRAC Service Module is installed.
Recovery Action
If the “IP Helper” service is stopped, start the “IP Helper” service on the Managed Node where iDRAC
Service Module is installed.
4.11 Failure to access iDRAC via Host OS as an Active Directory user
over LDAP when iDRAC is not connected
Symptoms
While trying to access iDRAC page via Host OS, it fails to connect to iDRAC page and throws the error
“The site can’t be reached.”
Reason
iDRAC network should be configured for authentication to take place over LDAP.
Recovery Action
Either the iDRAC dedicated port can be configured or can login as local user or guest.
4.12 Failure to access iDRAC via Host OS after performing an iDRAC
factory reset operation such as racadm racresetcfg
Symptoms
While trying to access iDRAC page via Host OS, it fails to connect to iDRAC page and throws the error
“The site can’t be reached.”
Reason
The OS to iDRAC passthru channel will be disabled in factory mode and hence iSM shall stop running
on the Host OS. This should be enabled manually so that iSM service will start and reconfigure the
iDRAC Access via Host OS again.
Recovery Action
Enable the OS to iDRAC Passthru channel in iDRAC.
Example using racadm cli command: racadm set idrac.os-bmc.adminstate 1