Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I don't suppose anyone could share IPMIView 2.24.1 again? I got the 3.66 update for this old X9 server (I help to run it for a local non-profit, completely out of any warranty obviously) and that's updated the port 5900 cert, but the IPMIView half is needed too.
The ones I've got access to are these, if anyone has both Linux and Windows of 2.24.1 ?
The ones I've got access to are these, if anyone has both Linux and Windows of 2.24.1 ?
Got it thankspls tell if you downloaded. i need to free space after.Dropbox
www.dropbox.com
Oddly still getting 'Connection failed' when clicking 'Launch KVM Console' despite the newer IPMIView version and 3.66 firmware
i don't know because i don't run it.
afaik, IPMIView installs its own tunnel. you need rip of that. maybe you need to allow unsafe connections....
You can still connect to the old version by simply replacing the certificates in the BMCSecurity folder.
Nah it doesn't seem to matter what I do.
If I upgrade to 3.66... use IPMIView 2.24.0 or 2.24.1... if I do or do not replace the server.crt/client.crt/.key files in BMCSecurity... if I blank all the jdk certpath/jar/tls disabledAlgorithms variables in java.security... or even if I run the damn program as root.
I still just get 'Connection error'.
If I upgrade to 3.66... use IPMIView 2.24.0 or 2.24.1... if I do or do not replace the server.crt/client.crt/.key files in BMCSecurity... if I blank all the jdk certpath/jar/tls disabledAlgorithms variables in java.security... or even if I run the damn program as root.
I still just get 'Connection error'.
Last edited:
OK so I tried uploading the firmware again, factory resetting it again (unticking all the preserve config options), none of that helped.
So I downloaded...
jre-8u501-linux-i586.tar.gz
jre-8u501-linux-x64.tar.gz
from java.com
If I use javaws from the i586 on a launch.jnlp file it works...
if i use javaws from the x64 on a launch.jnlp file then I get "Unable to load resource: https://10.42.1.4:443/liblinux_x86_64__V1.0.7.jar" like I mentioned before
However this has **never** been an issue until now.
All the versions of IPMIView I've successfully used with this (going all the way back to 2.21.1 at the very least) have been bundled with 64-bit versions of Java JRE. So it has been running fine under 64-bit JRE all this time. It's just recently that IPMIView has been giving the cryptic 'Connection error'.
So I downloaded...
jre-8u501-linux-i586.tar.gz
jre-8u501-linux-x64.tar.gz
from java.com
If I use javaws from the i586 on a launch.jnlp file it works...
if i use javaws from the x64 on a launch.jnlp file then I get "Unable to load resource: https://10.42.1.4:443/liblinux_x86_64__V1.0.7.jar" like I mentioned before
However this has **never** been an issue until now.
All the versions of IPMIView I've successfully used with this (going all the way back to 2.21.1 at the very least) have been bundled with 64-bit versions of Java JRE. So it has been running fine under 64-bit JRE all this time. It's just recently that IPMIView has been giving the cryptic 'Connection error'.
Last edited:
I've replaced the certificates in the BMCSecurity folder, but it doesn't work, do I have to upgrade the server's firmware? I'm looking for the new firmware for X11 too.
I think I have my answer (putting it here for anyone else using X9)... I must have been coming from 3.55 or older. It seems later firmware lack BOTH Windows AND Linux support for 64-bit (x86_64). I have asked Supermicro why on earth they've done this (and left support for macOS 64-bit working?)
user@pc:~$ strings SMT_X9_355.bin |grep -i pack.gz
SOL__V0.5.11.jar.pack.gz
iKVM__V1.69.21.0x0.jar.pack.gz
liblinux_x86_64__V1.0.5.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libsun_SPARC__V1.0.5.jar.pack.gz
libwin_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_357.bin |grep -i pack.gz
SOL__V0.5.11.jar.pack.gz
iKVM__V1.69.38.0x0.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_362.bin |grep -i pack.gz
SOL__V0.5.15.jar.pack.gz
iKVM__V1.69.39.0x0.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_364.bin |grep -i pack.gz
SOL__V0.5.15.jar.pack.gz
iKVM__V1.69.39.0x0.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_366.bin |grep -i pack.gz
SOL__V0.5.17.jar.pack.gz
iKVM__V1.69.41.0x0.jar.pack.gz
liblinux_x86__V1.0.7.jar.pack.gz
libmac_x86_64__V1.0.7.jar.pack.gz
libwin_x86__V1.0.7.jar.pack.gz
I've just realised something else too.
I think IPMIView stores a cache of the libraries it gets from previous connections.
So I probably was on firmware 3.64 with IPMIView 2.21.1 perfectly working earlier this year. But that is likely only because previously I had used the same copy of IPMIView to connect to the same server when it was running 3.55 or older. This would have cached liblinux_x86_64__V1.0.5.jar which is compatible with the x86_64 JRE bundled with IPMIView (all versions that I've ever used).
However
The 3.66 version hands out a JNLP file which references liblinux_x86_64__V1.0.7.jar (different version number). So this file is not cached by existing IPMIView installations which has previously cached liblinux_x86_64__V1.0.5.jar.
This explains why my IPMIView 2.21.1 was working with 3.64... despite 3.64 also lacking Windows & Linux 64-bit libraries in the firmware.
So this workaround no longer works...
Also this FAQ...
Where it says " If you connect to only ATEN and AMI X9 firmware, 64 bit JRE should be workable (for KVM). "
Is completely false now... and has been for anyone using a freshly installed copy of IPMIView on a firmware newer than 3.55.
I've raised this with Supermicro but all I've got back is... "I will forward your feedback, but as i mentioned, the firmware fix works for the vast majority of users still using this old platform. Due to its age it's highly unlikely further updates are provided."
user@pc:~$ strings SMT_X9_355.bin |grep -i pack.gz
SOL__V0.5.11.jar.pack.gz
iKVM__V1.69.21.0x0.jar.pack.gz
liblinux_x86_64__V1.0.5.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libsun_SPARC__V1.0.5.jar.pack.gz
libwin_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_357.bin |grep -i pack.gz
SOL__V0.5.11.jar.pack.gz
iKVM__V1.69.38.0x0.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_362.bin |grep -i pack.gz
SOL__V0.5.15.jar.pack.gz
iKVM__V1.69.39.0x0.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_364.bin |grep -i pack.gz
SOL__V0.5.15.jar.pack.gz
iKVM__V1.69.39.0x0.jar.pack.gz
liblinux_x86__V1.0.5.jar.pack.gz
libmac_x86_64__V1.0.5.jar.pack.gz
libwin_x86__V1.0.5.jar.pack.gz
user@pc:~$ strings SMT_X9_366.bin |grep -i pack.gz
SOL__V0.5.17.jar.pack.gz
iKVM__V1.69.41.0x0.jar.pack.gz
liblinux_x86__V1.0.7.jar.pack.gz
libmac_x86_64__V1.0.7.jar.pack.gz
libwin_x86__V1.0.7.jar.pack.gz
I've just realised something else too.
I think IPMIView stores a cache of the libraries it gets from previous connections.
So I probably was on firmware 3.64 with IPMIView 2.21.1 perfectly working earlier this year. But that is likely only because previously I had used the same copy of IPMIView to connect to the same server when it was running 3.55 or older. This would have cached liblinux_x86_64__V1.0.5.jar which is compatible with the x86_64 JRE bundled with IPMIView (all versions that I've ever used).
However
The 3.66 version hands out a JNLP file which references liblinux_x86_64__V1.0.7.jar (different version number). So this file is not cached by existing IPMIView installations which has previously cached liblinux_x86_64__V1.0.5.jar.
This explains why my IPMIView 2.21.1 was working with 3.64... despite 3.64 also lacking Windows & Linux 64-bit libraries in the firmware.
So this workaround no longer works...
FAQ Entry | Online Support | Support - Super Micro Computer, Inc.
Frequently Asked Questions
www.supermicro.com
Also this FAQ...
FAQ Entry | Online Support | Support - Super Micro Computer, Inc.
Frequently Asked Questions
www.supermicro.com
Where it says " If you connect to only ATEN and AMI X9 firmware, 64 bit JRE should be workable (for KVM). "
Is completely false now... and has been for anyone using a freshly installed copy of IPMIView on a firmware newer than 3.55.
I've raised this with Supermicro but all I've got back is... "I will forward your feedback, but as i mentioned, the firmware fix works for the vast majority of users still using this old platform. Due to its age it's highly unlikely further updates are provided."
Last edited:
My message above was a response from Lantizia. I added that a new version of IPMIView is optional. You can replace the certificates in the existing version without downloading the new version.
You need to update the firmware on the server anyway, because you need to update the CA certificate.
As a workaround (I didn't check it), roll back the time in BMC to the date before 05/17/2026 and do the same on the device from which the connection is being made. Perhaps the connection will work. But this is not a solution.
Or use HTML5. I need Java specifically, so I'm still hoping for X11 firmware.
Unfortunately, I haven't found the firmware yet.
Hi! I’m having the same problem: I can’t connect to the KVM console of the X10SLM-F motherboard using IPMIView_2.24.0_build.251224.
I also can't mount a drive via Samba.
I contacted Supermicro technical support, and they sent me a new BMC firmware (version 04.08), but that didn't solve the issue. I still can't access the console via IPMIView_2.24.0.
I think I need version IPMIView_2.24.1, but they didn't send it to me.
Could you please share IPMIView_2.24.1?
Thank you!
I also can't mount a drive via Samba.
I contacted Supermicro technical support, and they sent me a new BMC firmware (version 04.08), but that didn't solve the issue. I still can't access the console via IPMIView_2.24.0.
I think I need version IPMIView_2.24.1, but they didn't send it to me.
Could you please share IPMIView_2.24.1?
Thank you!