the cache tab of the Java™
RILOE II.
Login name and password problems
If you have connected to the board but it does not accept your login name and password, you must verify that your login information is configured correctly. Connect to the RILOE II using your browser, log in with a user name that has administrative access, and reenter the login name and password that are not being accepted.
NOTE: The login name and password are case sensitive. The RBSU F8 can also be used to correct login problems. After five login attempts, the board times out and it may take a minute for it to reset.
Remote Console mouse control issue
While using Remote Console on a server running Microsoft® Windows® Server 2003, mouse movement can be slow, and it might be difficult to navigate to each of the four corners of the screen. When trying to reach a far corner of the screen, the mouse can disappear completely.
NOTE: This mouse behavior is more pronounced when the Remote Console session is running in a browser applet window that is smaller than the size of the server screen, and scrolling is required to see the full contents of the screen, which are not displayed.
To resolve this issue:
1.Select Start>Settings>Control Panel>Mouse Properties from the Windows® Server 2003 desktop applet.
2.Disable the Enhance pointer precision parameter.
If mouse movement is still sluggish:
1.Select Start>Settings>Control Panel>Display>Settings>Advanced>Troubleshooting> from the Windows® Server 2003 desktop applet.
2.Set the slider control to full hardware acceleration.
For more information, refer to the "Optimizing performance for graphical Remote Console (on page 37)" section.
Resetting the RILOE II to Factory Default Settings
1.Log into the RILOE II web agents.
2.Select Tasks>Remote Management>Remote Insight Options.
3.Click Reset RILOE II.
Resetting RILOE II to the factory defaults erases all existing user account, password, and security settings. Be sure the default user account and password information is available.
Virtual Floppy media applet is unresponsive
RILOE II Virtual Floppy media applet can become unresponsive if the physical floppy diskette contains media errors.
To prevent the virtual floppy media applet from becoming unresponsive, run CHKDSK.EXE (or a similar utility) to check the physical floppy diskette media for errors. If the physical media contains errors, reload the floppy diskette image onto a new physical floppy diskette.
Troubleshooting the RILOE II 180