The iDRAC web interface comes up nicely now but that's as far as I can get. I guess the next option is to create a VPN to the router and from that point one would assume the redirection will work correctly. I'm going to ping a Dell server guy I know to see if he can backdoor an answer on this.
I have had no luck in accessing an iDRAC through a Bellsouth, and I use the term loosely, router. Customer has DSL through Bellsouth with the typical nat based modem they install. I have setup the following ports to forward to the iDRAC and although I get a login screen (sometimes) I can never get any further. Am I missing some ports?443 (ok I have it on another port but you get the idea)6235590The connection over the DSL stinks but even being as slow as it is I should be getting the login screen each and every time and I'm not and I have never got the full web interface even after getting logged in. Locally it's all good. I am going from two sources:22. SSH23.
Telnet80. HTTP443. HTTPS623 RMCP/RMCP+5900. Virtual Console keyAndThere has been no change in the connection problems. Even a crappy connection should be able to bring up the login page each time and it won't let alone actually get into the web interface for the hardware.Speed test on their DS DSL came back with 406kbps by 222 kbps but pings ranged from 76 to 350ms. I was testing with Visualware, they seem to show a more honest rate and give you some feedback on the connection quality.
![Network Network](/uploads/1/2/5/3/125352406/430236159.jpg)
That speed should be allowing the pages to load but they don't.Edited May 20, 2013 at 04:10 UTC. 443 is enough for web interface. Refreshing the page after login is helpful for me on DSL. James, you may check what happens after login with developer tools integrated in browsers (Ctrl+Shift+I for Chrome and FF, F12 - IE).
In Network tab you can see all conversation between your browser and DRAC. Just checked: System Summary page of iDRAC6 (about 1MB) after pressing Submit button on Login Page was loaded in:40 s over DSL connection (Chrome in linux), ping 50 ms16 s into LAN (IE9 on 2008R2), ping. FIXED!I got away from trying to make this work and decided tonight to give it another shot and the fix was very simple but I'm not sure why it's required.You must open two ports not one and apparently for at least some firewalls/routers/nat devices you have to do two ports and not one port range.As mentioned before you need 5900 however you MUST forward 5901 as well. Even though the web interface shows only 5900 as the default port it is using both:5900 TCP and UDP Keyboard and mouse connection5901 TCP and UDP Video connectionWorse still was at least on the firewalls I worked with I had to enable both ports individually and not a port range.I have another site to setup with 3 servers behind the firewall which I may test to see if it acts the same way. That site isn't as big a deal as I am connected into their network a half dozen ways so I can provide a host of support services. I had exactly the same problem as Taron Asatryan.
And using worked for me as well. Note that for connections on the same subnet this is not a problem and it works correctly if you simply go toOnly when you want to access iDRAC through a router using port forwarding (PFSense) in my case this happens and you have to explicitly point to login.html.This still happens in iDRAC 8. I can't believe that DELL is still insisting on 'just open port 443 and everything is fine'. While it is not if you just purchased multi-thousand dollar server hardware.jlinkels.