This post is more than 5 years old
17 Posts
0
316644
iDRAC6 Virtual Console (Connection Failed)
I'm at the point of pounding the keyboard and tossing it across the room with not being able to
get the Virtual Console to successfully connect. Here is the situation...... I'm able to access the iDRAC remotely via GUI or SSH and login and/or make changes without any issue. When I attempt to run the Virtual Console, it simply fails to connect. I get the error message in my Java Console of "Connection Failed".
Now I've read other posts and recommended fixes and none of them had made any difference. Here is what I've done to date:
1) Added the DRAC IP into the Java Exception List
2) Changed the Java Network Setting from Browser to Direct Connect
3) Disabled Encrypted Video on the DRAC
4) Upgraded the Firmware to v2.85
5) Confirmed using tcpdump that my host and the DRAC can talk on port 5900
6) Cycled the DRAC Plug-in Type between Java and Native
7) Run the Virtual Console (viewer.jnlp) both through the browser and downloaded the .JNLP and used javaws on it.
I'm completely out of options and of what else I could do to make the Virtual Console connection stop failing. Does anybody have any other theories that might be causing me problems?
Hoffman316
1 Message
1
October 26th, 2018 13:00
I have Java8 Update 181. The workaround is to modify C:\Program Files (x86)\Java\jre1.8.0_181\lib\security\java.security file
Comment out
#jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
replace with
jdk.tls.disabledAlgorithms=MD5withRSA, DH keySize < 1024, \
reboot and it should work.
Denis4DELL
6 Posts
0
October 29th, 2018 06:00
AbfSailor
6 Posts
0
November 4th, 2018 15:00
This works for me also. Thank the heavens! Finally, something that works!!!!
Thank you Thank you Thank you!
GVRATech
1 Message
0
November 5th, 2018 11:00
Like many others in the thread, we encountered this issue with some older R710's using the latest iDRAC firmware available at the time, v 2.85 (looks like 2.91 has been released). Modifying the various Java settings didn't seem to work, and port 5900 was confirmed open to the iDRAC VLAN.
The only solution was to go back to 64 bit Java v7u79. Far from optimal from a security perspective, but it's sandboxed within a VM and only enabled when server access is required.
Very frustrating.
BrunoMuniz
1 Message
0
January 11th, 2019 04:00
Gave it a try and just worked fine! - - -
To solve this problem just update your JAVA to the latest version and comment the line "jdk.tls.disabledAlgorithms=SSLv3" activating SSLv3.
Thx for help, guys!
regctx
2 Posts
0
January 29th, 2019 06:00
James Harper, This worked perfect, it is the RC4 causing these issues! Thank You!
spgsitsupport
42 Posts
0
April 5th, 2019 08:00
That was so extremely helpful. In the end I can again get to my servers (in case I need to do so)
Seb
zukes
20 Posts
0
August 8th, 2019 05:00
Eventually solution for Windows 7 64bit OS is:
1. install firefox 32bit 52esr version (it can be done with any current firefox x64 version).
2. install java jre-7u79-windows-i586 (if you have younger it must be uninstalled first)
So iDRAC 6 virtual console just works.
zukes
20 Posts
0
August 8th, 2019 05:00
I've check Firefox 60.8.0esr version (after update 52esr) and it also works
SpJam
1 Message
1
August 16th, 2019 00:00
Hello!
We have more than a dozen R430 servers in a distributed Geo infrastructure, and we have the same problem with some of them.
We tried any version of JRE, browsers, OS, console type: Native, Java, HTML5; Video encryption disabled, Java security changes, cold restarting of servers, etc.
All ports were open on FW.
BIOS and firmware have the latest version, updates were installed directly from iDRAC: 2.9.1 and 2.63.60.61.
Does not work! This is some mystic
But today I took the following steps and voila! -)
1. Changed the port to 4900
2. Turned off the Virtaul Console
3. Enabled the virtual console
4. And got a connection from my admin statioin through 2 firewalls
Maybe this post will help someone.
Regards!
OC_JasonFW
1 Message
0
October 4th, 2019 08:00
changing to port 4900 saved me. without this post i would have never guessed. I tried EVERYTHING!
Thank you OP!!
squigley
16 Posts
0
October 24th, 2019 06:00
I'll just chime in on this thread with my 2c, since I have wasted a bunch of time on this recently.
I'm running Ubuntu 18.10, which includes "IcedTea" instead of Java. It's a good alternative, for the majority of things, but not old iDRACs/virtual consoles.
It gives the identical connection failed issue, which reviewing the console will show it's due to the jar file being treated as "SIGNED_NOT_OK", because the crypto methods have been blacklisted, and it requires modifying the security file, as identical for Java, as reported multiple times earlier in this thread, to re-enable SSLv3, MD5, RC4. There are 3 places in the security file this needs to be modified (possibly not all of them, or to re-enable all of those cryptos, but doing that works..).
Anyway, once you get this working, you will be able to connect, and everything, including virtual media, works, except the keyboard..
Maybe getting a connection where you don't need to be able to type will be sufficient for some people, as you can still use the keyboard macros (eg ctrl+alt+del) in case you just need to see the console, or be able to reboot a system, or perhaps you are using Windows and you can turn on the onscreen keyboard and click on the letters to type (I am not sure if mouse support works either though).
I tried multiple ways to fix this, so I could type, apparently it is to do with the way keyboards/scancodes are handled in linux now, and I found a "hack" which claims to fix this (though targeted at keys like arrows and SysRq), which didn't work.
In the end I had to use a "real" version of Java, vs IcedTea, and I found this bundled in a copy of the Arduino IDE I had downloaded, as they include it. I just specified the full path to the javaws binary. This is an easier way than trying to shoehorn an install of Java into a deb/pkg managed install, since Java is no longer in the package repositories.
Also, to save having to log in to the iDRAC, and download the .jnlp file and then manually launch it each time you want to connect, you can edit the .jnlp file and replace the numbers that are in the username and password values, with your proper iDRAC login credentials. That way you can just use javaws from your real Java directory to just launch this .jnlp file whenever you need to connect.
hkabuubi
1 Message
0
November 9th, 2019 02:00
How can I obtain the license my server has Idrac Express.
Could you help and show the step to obtain the license?
Thanks in advance
spgsitsupport
42 Posts
1
December 24th, 2019 06:00
You need to buy hardware for the unit to be Enterprise
See the comment:
AbfSailor
6 Posts
0
January 7th, 2020 06:00
Thank you for sharing this.