Hey Joey C and other Dell professionals. I double checked my iDRAC network settings, the gateway was proper (192.168.1.254). I also searched fro and verified that the iDRAC can ping the gateway ("racadmin ping 192.168.1.254" when I logged into the iDRAC web GUI on the intranet). I also checked the port pinhole configuration of the router, which seemed also fine. I tried to access the Web GUI remotely a few times and I verified that the router's firewall logs didn't yeet those packets and recognized as pinhole access. Not sure what changed, but maybe my browser tries http protocol by default when it sees an IP address (I'm accessing the iDRAc remotely only with a static IP address, no DNS name), when I manually put https protocol, I got to an error message instead of a timeout: "Bad Request Your browser sent a request that this server could not understand Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle file request." This was both with Firefox and Chromium based browsers. Then I search for this specific error message and in a Knowledge Base article I found a solution which helped: HTTP/HTTPS FQDN Connection Failures On iDRAC9 firmware version 5.10.00.00 | Dell US " By default, iDRAC9 will check the HTTP / HTTPS Host Header and compare to the defined 'DNSRacName' and 'DNSDomainName'. When the values do not match, the iDRAC will refuse the HTTP / HTTPS connection. In iDRAC9 5.10.00.00, this Host Header enforcement can be disabled with the following RACADM command.  " Now I wonder if this poses any security risk. We access the iDRAC from not fixed IPs and address it with an IP address. I can only think of a REST Client only which would inject required HTTP Headers. But at least I can access the iDRAC web GUI now.
I have a Dell PowerEdge T350 with an iDRAC9 Basic. The server is connected to a switch which is connected to a router upstream which is connected to the internet. Very simple. Both the server's NIC1 is connected to the switch and also the iDRAC's own UTP LAN card. I enabled the iDRAC and I can access the web GUI from another host connected to the same switch (a.k.a. intranet). Both LAN interfaces of the server have static intranet IPs configured (on the 192.168.1.x range) and not DHCP-d, since the port translations on the router we better have a fixed IP. I configured the port translations on the router so two service could be accessed remotely: RDP and the iDRAC. The RDP is the server OS itself. Here comes the interesting part: I configured the iDRAC port redirection (or we can call it firewall pin hole) the same way as I did with the RDP. Although the RDP needs both TCP and UDP 3389 port redirection. The iDRAC only needs TCP 443 port redirect. Questions: Related ServerFault issue: [URL]
Why I cannot access iDRAC9 remotely?