- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- RILO2 on new HP ML350G4 with Win2k3
Server Management - Remote Server Management
1752492
Members
5472
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2005 12:43 AM
тАО06-01-2005 12:43 AM
RILO2 on new HP ML350G4 with Win2k3
I have a new ML350G4 with a RILO2 card configured. The card is running 1.16 firmware and all drivers are the latest platform support pack.
When I login to the RILO card, I select Remote Console, the console starts and all I end up with is a black screen with the following error at the bottom -
java.net.ConnectException: Connection timed out: connect
I've tried different browsers, different Java versions etc and it just doesnt work!
When I login to the RILO card, I select Remote Console, the console starts and all I end up with is a black screen with the following error at the bottom -
java.net.ConnectException: Connection timed out: connect
I've tried different browsers, different Java versions etc and it just doesnt work!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2005 01:52 AM
тАО06-01-2005 01:52 AM
Re: RILO2 on new HP ML350G4 with Win2k3
There have been similar issues described that might be related to the name space...
Try these approaches to see if the problem might be related to your name service. Use the following suggestions in the URL that you use in the browser to access the lights-out board:
Assuming your RILOE II is named "ribhost.domain.com" and resolves to 192.168.1.1
A) use the IP address instead: "http://192.168.1.1"
B) use the hostname without suffix: "http://ribhost"
C) use the fully qualified domain name: "http://ribhost.domain.com"
Try these approaches to see if the problem might be related to your name service. Use the following suggestions in the URL that you use in the browser to access the lights-out board:
Assuming your RILOE II is named "ribhost.domain.com" and resolves to 192.168.1.1
A) use the IP address instead: "http://192.168.1.1"
B) use the hostname without suffix: "http://ribhost"
C) use the fully qualified domain name: "http://ribhost.domain.com"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2005 12:35 PM
тАО06-02-2005 12:35 PM
Re: RILO2 on new HP ML350G4 with Win2k3
Thanks
ended up being a combination of things -
1 - Needed to add telnet access as well as http and https through the firewall
2 - Needed to setup DNS and ensure it all resolved correctly
ended up being a combination of things -
1 - Needed to add telnet access as well as http and https through the firewall
2 - Needed to setup DNS and ensure it all resolved correctly
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP