HP Integrated Lights-Out 3 - Manual (Page 223)

.NET IRC failed to connect to server
iLO might display the message Failed to connect to server when it attempts to establish
a .NET IRC session.
The iLO .NET IRC client waits a specified amount of time for a connection to be established with
iLO. If the client server does not receive a response in this amount of time, it displays an error
message.
Possible causes for this message include the following:
•
The network response is delayed.
•
A Shared Remote Console session is requested, but the session leader delays sending an
acceptance or denial message.
Solution 1: Retry the .NET IRC connection.
Solution 2: If possible, correct the network delay and retry the .NET IRC connection.
Solution 3: If the request was for a Shared Remote Console session, attempt to contact the session
leader and retry the request. If the Remote Console Acquire feature is enabled, use the Acquire
feature rather than requesting a Shared Remote Console session. For more information, see
“Acquiring the Remote Console” (page 118) .
File not present after copy from .NET IRC virtual drives to USB key
If a user copies files from the target server to a mounted iLO virtual drive (USB key connected to
a client computer running any Windows OS), the files are not visible in Windows Explorer on the
client computer.
File changes on the iLO Virtual Media USB key are never seen in Windows Explorer by the user
on the client computer.
Windows Explorer keeps a cached copy of the files on the USB key, and the iLO Remote Console
does not notify the Windows Shell when the USB key is updated with file changes. The file changes
exist on the USB drive, but if the user refreshes the Explorer window, the cached copy of the files
is flushed back to the USB key, and the user will never see the file changes in Windows Explorer.
Any kind of file change made on a mounted iLO Virtual Media USB key drive from a Windows
client via the Remote Console can trigger this issue.
Solution:
1.
Install a USB key drive on a Windows client computer.
2. Using .NET IRC, connect the client USB key to the iLO Virtual Media drive on the target server.
3. Make file changes to the connected iLO Virtual Media drive (copy, delete, and so on).
4. Safely unmount the iLO USB Virtual Media drive on the target server so that all data is updated
to the Virtual Media drive.
5. Disconnect the client USB key by using the .NET IRC.
CAUTION: Do not use Windows Explorer to refresh the contents of the USB key.
6. Safely remove the USB key from the client computer by clicking the Safely Remove Hardware
icon in the Windows notification area. Follow the onscreen instructions.
7. Remove the USB key from the client computer.
When you connect the USB key to any computer, the file changes will be visible in Windows
Explorer.
.NET IRC takes a long time to verify application requirements
When you start the .NET IRC from the iLO web interface, the following dialog box ( Figure 124 )
appears and remains on the screen for a long time.
Troubleshooting Remote Console issues 223