Trouble with Remote Console on HPE ML350 Gen9 Server

0
7
Asked By TechieTide92 On

I'm working with an HPE ML350 Gen9 server that has dual E5-2680v4 processors, and I'm facing some strange issues when trying to use the remote console. Both the HTML5 and Java consoles exhibit the same problems. While everything seems to function properly, randomly, the display freezes momentarily when I'm typing. This results in the letters I type being repeated multiple times. We've tested various operating systems including Proxmox, Windows Server 2022, and Debian. We've also completely ruled out any network devices between the iLO interface and the computer used for the console. We've tried different firmware versions for both the system board and iLO, but still no luck. The server isn't throwing any errors; we just can't figure this out. Any insights would be greatly appreciated!

3 Answers

Answered By WebDevKid On

If you're using multiple browsers like Firefox and Chrome without any luck, it might be worth checking your system settings. Sometimes, security settings or ad blockers can interfere with the console's functionality. Just a thought!

TechieTide92 -

That’s a good point! I’ll look into the security settings and see if anything stands out. Thanks for the tip!

Answered By ServerGuru7 On

First off, make sure you're using the latest iLO firmware. Have you tried restarting the iLO processor? It won't reboot the server but might help clear up any glitches. Also, using an incognito window could rule out any browser-related issues. Just to be safe, here are the links for the latest firmware updates if you haven't checked them out yet.

TechieTide92 -

We've kept everything up to date, including the latest firmware, and we did restart iLO. We even tried all the usual troubleshooting steps like changing cables and reseating RAM, but the issue persists.

Answered By BrowserWizard On

Have you given the .NET thick client a shot? Sometimes switching to a different client can work out well for these weird iLO issues. Just curious if you noticed any differences with it.

TechieTide92 -

Yeah, we tried the .NET thick client too, but it didn’t solve the problem either. It’s been frustrating trying to pin this down.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.