TYAN S4992, Руководство пользователя

Страница: 88 / 148

82
http://www.TYAN.com
Remote console is unable to connect and displays a timeout error.
Have a look on your hardware. If there is a proxy server between KVM-over-
IP Sever Management and your host, then you may not be able to transfer
the video data using RFB. Establish a direct connection between
KVM-over-IP Sever Management and the client. Furthermore, check the
settings of KVM-over-IP Sever Management and choose a different server
port used for RFB transfer. If you use a firewall then check the according
port for accepting connections. You may restrict these connections for the IP
addresses used by theKVM-over-IP Sever Management and your client.
The Remote Console does not open with Opera in Linux.
Some versions of Opera do not grant enough permission if the signature of
the applet cannot be verified. To solve the problem, add the lines grant
codeBase "nn.pp.rc. Remote Console Applet" { permission
java.Lang. RuntimePermission "access Class In Package. sun.*"; to the java
policy file of opera (e.g./usr/share/opera/java/opera.policy).
The video data on the local monitor is surrounded by a black border.
This is not a failure. The local monitor is programmed to a fixed video mode
that can be selected in the video settings of KVM-over-IP Sever
Management.
The local monitor displays video data but the remote screen remains
blank.
If the Remote Console is connected (look at the status line of the Remote
Console) you should verify that video chip DVO interface is not switched off
by the video driver of your operating system. Normally, video chip onboard
has 2 interfaces. One is analog and connected to local monitor. The other is
DVO and wired to KVM-over-IP Sever Management slot. Some video driver
will switch off the DVO output by default.
For example, RHEL 4.5 and 5 default XGI driver will disable the DVO
interface. It’s to say, when screen is switch to X window, remote screen will
be blank. You have to use text mode or upgrade driver. RHEL4.5 need driver
R1.12.02 and RHEL5 use R1.12.03.
4. Mouse and Keyboard
The mouse does not react correctly in the applet screen. The mouse is
not in sync with the mouse of the host.
Navigate your mouse pointer into the upper left corner of the applet screen
and move it slightly forth and back. Thus the mouse will be resynchronized.
If re-synchronizing fails, disable the mouse acceleration and repeat the
procedure.
I have a crazy mouse.
Verify your mouse settings. Disable the mouse acceleration. For instance in
Windows 2000 this can be done in ’Settings -> System control -> Mouse’.
Make sure that your mouse settings match your mouse model, i.e. PS/2 or
wheel mouse.