I recently had to access a server via DRAC (Dell Remote Access Controller) for the first time in a very long time and I expected it to be very simple these days but it actually ended up being more of a pain than I remember due to a number of gotchas.
For the most part the issues are due to increased security in browsers and the Java platform which can only be a good thing in my opinion.
I’ve detailed the various snags I hit here in the hopes they will help others!
Note: If you’re server doesn’t have DRAC or you’d like to update it, add in boards are available separately and quite cheap (see here) – in other words it’s not onboard or nothing.
Default Login Details
In case you don’t know the default login details for a Dell DRAC card are generally root and a password of calvin – modern versions of DRAC require you to change the default login details when setting it up.
Install Java
Make sure you have Java installed on your computer and enabled in your browser if you want to use the virtual console (you can get it from www.java.com/en/).
Add Address to Java’s Exception Site List
In the recent versions of Java security was tightened up and unless your DRAC ticks all the right boxes, Java won’t connect until you add the connection address to your Exception Site List in the Java control panel:
- Select Configure Java from your start menu
- Click the Security tab
- Click the Edit Site List and in to it enter the address of the DRAC you are trying to connect to, I added both with and without the SSL port just to be sure, for example:
http://173.194.41.142
http://173.194.41.142:443
Clicking ‘Launch Virtual Console’ Downloads a Strange File
Depending on your browser, clicking on the Launch Virtual Console link in the web console doesn’t launch anything, instead starting a download of a tiny file with a very long file name similar to this:
http://173.194.41.142/viewer.jnlp([email protected]@idrac-DVSNMW1%2C+PowerEdge+R420%2C+User%[email protected]@ST1=71049c009aea2c777b889d23038723ad)
This is actually the Java connectivity package meant to invoke Java and start the connection but in some cases the browser perceives it as a download. To get around this, save the file but delete everything after the primary file name – so save it as viewer.jnlp and double click it, that should invoke Java correctly.
Login Failed, Possibly Due to Slow Network Connection
Despite the error message, this is often a problem not with connectivity or network speed but rather with security. I recommend downloading the SSL certificate you see in your browser and adding it to your Trusted Root Certification Authorities container on your PC, then restart your browser.
Firefox is the Answer
Having done all of the above and getting incrementally further along each time, in the end I still had to resort to using Firefox rather than my usual browser (Chrome).
You are my new best friend. Thanks a billion for posting saved me from going insane.
Hi Pete,
No worries and thanks for the thanks!
Thanks for this. Baffled why Firefox has to be used to download the Java file.
They get some flak for being cheap and cheerful, but SuperMicro’s ILO is head and shoulders above the crap that Dell and HP turn out.
I have added the certificate in Trusted Root Certification Authorities container, still I am getting this error “Login Failed, Possibly Due to Slow Network Connection”.. any thoughts??
Hey Rajesh,
Thanks for the comment – unfortunately if you’ve followed all the steps and also tried Firefox I’m at a loss!
As much as I hate to say it, if firefox/java fails try setting the type of console from java to “direct” aka activeX and then use IE.
Thanks! This was really helpful! I ended up using IE, but changing the type of console from native to Java.
thanks, the firefox also fixed mine.
Going insane having already tried all the other steps you suggested (from posts elsewhere) your recommendation to use Firefox saved the day. Big thx.
Glad it helped JB!
I got windows 10 and internet explorer IE-11 to work with Dell r910 iDRAC by selecting the ‘gear’ at the top right and then ‘compatibility view settings’, add the idrac ip to the list, then it worked.
Don’t bother with adding this and that to the new Java, it will still refuse connection, the best thing is to uninstall the new Java, look for and install Java 7, and use chrome.
As Bob mentioned, chrome will ask to download the little file, sure allow it to download, and when it opens the little box at the bottom left of chrome saying download complete, right click the little arrow next to the filename, and select ‘Always open this type of file’. then find the file you just downloaded, then delete it, and try to open the virtual console again, and this time, chrome will open it using Java instead of downloading it. because when Java 7 is installed it also associates .jnlp files with Java, so that chrome when opening the file that iDRAC sends will open it instead of downloading it.
I have a Dell PowerEdge T710 and use iDRAC6 Enterprise, and I found the solution on the net, and a lot of people are complaining that no matter what they do with the new Java it just will not allow connection to iDRAC, so installing Java 7 is recommended, oh, and after installing Java 7, go straight to the Windows control panel and open Java, and look for the Update tab and uncheck the box to update.
So, until Oracle have released a better version of Java that does allow iDRAC connections, Java 7 is the only way to go.
Hi Michael,
Many thanks for the detailed comment and extra info!