Using virtual console, Network connection has dropped

Same problem for me.

My last action before it stops working was updating Java on my macbook...

Any solution ?

Same here. It's definitely a Java security issue. However, not sure who is responsible to fix it...Dell or Oracle?

I used to be able to find older versions of Java and re-install them as a workaround, but it seems they have made this nearly impossible. 

found it. try this: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-javase8-2177648.html

i installed jre 8 update 162 and now the iDRAC virtual console is working again!

of course, this version won't have the latest security updates.

i noticed that my windows firewall needed access again, so perhaps that's the problem with the latest version? maybe it changed executable names or something? i might look into that further.

I ran into this issue last night, this thread helped get me out of a jam.

I did have to login to an oracle account (after first creating one) to download them, but the link you provided worked wonderfully.

Thanks

The issue was definitely caused by the Java update.  They've added a disablement of the 3DES_EDE_CBC TLS algorithm.  I was able to determine this by comparing the java.security files between a known working client system on an older version (161) and an up to date system (171).

Older (161):
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
 EC keySize < 224, DES40_CBC, RC4_40

Newer (171):
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
 EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC

If you search for the java.security files located in lib/security for each installation, you can comment the existing section then copy/paste without the algorithm:

Example Code:
#jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
# EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
EC keySize < 224, DES40_CBC, RC4_40

Note: You may have to update multiple files if you've installed Java for 32 and 64-bit platforms.

Save your file(s), close and re-open your browsers, and everything tests out fine.

Enjoy, and be sure to tip your waitress!! :-)

-C-GO

Hello,

The newest iDRAC update solved my problem: 2.60.60.60

Regards,
Csabi

Kudos!!! 
It worked like charm:Smile:

@C-GO

Thank you sooooooooooooooooooooo much for this!!!  I have three R420's that I keep on iDRAC 1.66.65 because I use them in my office and the fan curves changed when Dell upgraded to iDRAC 8 2.xx.  They are much, much louder on newer versions.  That latest Java update made it where I had a dedicated VM with an older version of Java installed just so I could run iDRAC.  You have just made my life a lot easier!

WORKING!!!!

Hi,

I got the same problem when I launched the Virtual console, after the iDRAC8 update to 2.60.60.60 and Bios 2.8.0 of my 4 Dell R630 servers:

'The viewer has terminated
 The network connection has been dropped.'

I installed Jre 8 update 172 and now the iDRAC virtual console work again.

These problems are because more recent versions of Java do not accept the less secure encryption methods supported by the older iDRAC 7 firmware versions. IIRC the setting is in, on Windows: 

C:\Program Files\Java\jre1.8.0_181\lib\security\java.security

And the controlling line is:

jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC

You can play with that if you'd like, to see what affects your Virtual Console usage. I forget which one is the offender, sorry.

The latest (as of this date) iDRAC fixes the problem by I assume using more state-of-the-art encryption:

 iDRAC-with-Lifecycle-Controller_Firmware_2GFC7_WN64_2.60.60.60_A00.EXE

---

@C-GO wrote:

The issue was definitely caused by the Java update.  They've added a disablement of the 3DES_EDE_CBC TLS algorithm.  I was able to determine this by comparing the java.security files between a known working client system on an older version (161) and an up to date system (171).

Older (161):
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
 EC keySize < 224, DES40_CBC, RC4_40

Newer (171):
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
 EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC

If you search for the java.security files located in lib/security for each installation, you can comment the existing section then copy/paste without the algorithm:

Example Code:
#jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
# EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC
jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \
EC keySize < 224, DES40_CBC, RC4_40

Note: You may have to update multiple files if you've installed Java for 32 and 64-bit platforms.

Save your file(s), close and re-open your browsers, and everything tests out fine.

Enjoy, and be sure to tip your waitress!! :-)

-C-GO

---

This worked for me. Thanks!

Thank you so much. It worked!

Thank you, @C-GO . I'm coming from the year 2019 where this solution still works.

Editing java.security as you described solved this for us! The proper solution would be to update the DRAC to support the latest encryption versions, of course, but we still need this workaround to connect remotely in order to update the DRAC. I really appreciate this.

Hello, My self Jyoti Sharma I have the same problem-related server issue  I need help so kindly help me, please