Troubleshooting Guide - Belkin OmniView Manual De Instrucciones

Ocultar thumbs Ver también para OmniView:
Tabla de contenido

Publicidad

Idiomas disponibles
  • ES

Idiomas disponibles

  • ESPAÑOL, página 323

5-0 Troubleshooting Guide

The remote mouse does not work or is not synchronous.
First, check the VGA connection. Both the RIPM and the local monitor must
support the same video resolution. Make sure that your mouse settings match
your mouse model, i.e., PS/2 or USB. Also, the mouse model must be set on
both the RIPM and the host (the computer connected to the RIPM) operating
system. In some circumstances, the mouse synchronization process can
produce errors. Please refer to the "Mouse, Keyboard, and Video Configuration"
section in Chapter 3 for further explanation.
The video quality is bad and/or grainy.
Use the menu entry "Reset" to set the RIPM to its default values. Then, click
the "Auto-Adjust" button to select an appropriate video output. Check that the
video cables are securely connected.
Login on the RIPM fails.
Verify both your user login and your password. The default username is
"administrator", and the default password is "belkin". Make sure that your web
browser is configured to accept cookies.
The RIPM's Remote Console window does not open.
Verify that Java has been loaded. A firewall may prevent access to the Remote
Console. The TCP ports #80 (for HTTP) and #443 (for both HTTPS and RFB)
must be open (the server providing the firewall must accept incoming TCP
connections on these ports).
The Remote Console is unable to connect and displays a
time-out error.
Verify your hardware and network setup. If there is a proxy server between
the RIPM and your host, then you may not be able to transfer the video data
using RFB. Establish a direct connection between the RIPM and the client. In
addition, check the settings of the RIPM and choose a different server port for
RFB transfer. If you use a firewall, check the appropriate port for accepting
connections. You may restrict these connections to the IP addresses used by
the RIPM and your client.
No connection can be established to the RIPM.
Inspect your hardware. Is the RIPM attached to a power supply? Verify your
network configuration (IP address, router). Send a "ping" request to the RIPM to
find out whether the RIPM is reachable via network.
Special key combinations (e.g., ALT+F2, ALT+F3) are intercepted by
the console system and not transmitted to the host.
Define a so-called "button key". This can be done in the Remote Console
settings (see the "Remote Console Control Bar" section on page 23.
73
P75075ea_F1DE101Hea_man.indb 73
8/16/2006 11:33:30 AM

Publicidad

Tabla de contenido
loading

Tabla de contenido