 |
Why do I get the error "Raritan Device
was not found" when I double click on the
IP profile of RRC to access the IP Reach?
This
error message indicates that RRC and IP-Reach
are not communicating on the same port. The Factory
default port is 5000 and can be found under network
configuration. Right click on RRC profile and select “Modify
profile” to verify which port is configured.
Then, contact your administrator to obtain current
port number being used by IP-Reach and make appropriate
change to your profile. |
 |
Why do I get the error “Unexpected
communication error” when I try to access
the IP-Reach using web browser/RRC?
This error message can occur for 3 possible reasons.
- The IP-Reach is configured with a private
key which is not matching the local RRC profile.
Contact the system administrator to verify private
key status and configure it accordingly on your
local RRC profile.
- The IP-Reach is under control
of a Command Center. As a result, direct access
is disabled. Contact administrator to verify
this status.
- Access Control List (ACL) is activated
and you are trying to access the unit from a
restricted IP/subnet. Contact administrator to
verify if this is the case.
|
 |
Why is there a large amount of UDP broadcast
activity on port 5000 and 5001?
When RRC is launched, it sends out UDP broadcast
on port 5000 to discover Raritan devices. If there
is a Raritan device on the network, it will respond
back with broadcast on UDP 5001. While this happens,
you will see browsed (sphere like icon) profile.
To prevent the UDP Broadcast, click on the globe
like icon on RRC icon menu to turn off browsing.
Note that this action will work only for this session.
The Next time a user launches RRC, it will send
out broadcast again because this function is on
by default. |
 |
When connecting to the IP-Reach remotely,
the two mouse cursors do not line up (are not
synchronized). How do I synchronize the mouse
cursors?
There are several steps you can take to optimize
mouse synchronization.
- Mouse acceleration must
be disabled. On Windows Server 2003 and Windows
XP, this option is called "Enhanced
Pointer Precision mode" and is located under
Mouse Properties. Windows NT, however, does not
have this option. Most other Operating Systems
refer to this option simply as "mouse acceleration."
- Mouse speed must be adjusted to 50%. The
only exception is Windows NT, where you must
set the mouse to the minimum mouse speed available.
- The video resolution and refresh rate should
be adjusted. High supported refresh rates (70-75
Hz) improve your synchronization. The optimum
setting is 1024x768 at 75 Hz.
- Perform the 'Auto-Sense
video' on the RRC toolbar to resync the two cursors.
|
 |
What remote access connection methods
can IP-Reach accommodate?
IP-Reach provides network administrators with
a choice of remote access via Internet, LAN/WAN,
or dial-up modem. That means servers can be accessed
both in and out of band, so remote access to mission-critical
target servers is always available--even if the
network is down. |
 |
Can I customize IP-Reach to enhance performance
relative to my specific KVM configuration?
Yes. A variety of fine-tuning procedures are available.
Automatic Color calibration, KVM On-Screen Display
tuning, and Target Mouse Pointer adjustments all
serve to enhance IP-Reach performance. |
 |
Can I customize IP-Reach to enhance performance
with regard to different remote access methods
and situations?
Yes. IP-Reach offers a variety of performance
enhancements to optimize a chosen connection method.
Color Depth, Progressive Update, and Internet Flow
Control are just a few of the adjustment options
available to speed response time. Color Depth,
for example, can be adjusted all the way down to
black and white to decrease the data load during
an emergency midnight modem connection to mission-critical
servers over low-bandwidth. |
 |
Can I perform a dial-up modem connection
to IP-Reach over a PBX line?
No. Modems require an analog telephone line. |
 |
How Is IP-Reach administration carried
out?
Administrators access IP-Reach through a connected
IP-Reach Admin Console. A simple keyboard driven
interface of menus offers straightforward access
to IP-Reach setup and control. User profiles,
security settings, configuration and diagnostics
are just a few of the options available. The
IP-Reach Admin Console can be removed from the
server room once IP-Reach setup is complete.
Or for constant, clutter-free access to IP-Reach
administrative menus from any location, IP-Reach
can be designated as a Target to its KVM configuration.
|
 |
Remote Access Software has been available
for a long time. What makes IP-Reach different?
With IP-Reach, the software runs only on the IP-Reach
unit itself, not on each individual Target Server.
Traditional Remote Access Software solutions require
software to be loaded and running on each Target
Server, which must offer a supporting Operating
System. This can create compatibility, performance,
and reliability issues on mission critical Target
Servers. |
 |
How does IP-Reach work?
IP-Reach connects to the keyboard, video,
and mouse ports of a server or KVM switch. Using
Raritan's powerful frame-grabber and compression
technology, it captures, digitizes, and compresses
the video signal before transmitting to a. |
 |
Is IP-Reach simple to install?
IP-Reach is very easy to install. Just connect
it to a user port on an existing KVM configuration,
and assign an IP address and/or telephone number
for modem access. Run the short installation
wizard for the Raritan Remote Client on your
Remote PC, and you are ready for IP-Reach remote
access. |
 |
What level of control does an IP-Reach
remote user have over attached Target Servers?
The remote user has direct access and total control
of target servers for maintenance, administration,
and troubleshooting, from running GUI applications
to BIOS-level troubleshooting, and even rebooting. |
 |
Can I continue to access my KVM configuration
locally?
Yes. IP-Reach features a special Direct Analog
User port for direct access to the KVM configuration.
This pass through port provides an additional
local access point, which is especially important
for single-user switches or for providing critical
access to servers if the network is down. |
 |
Can I use IP-Reach within my local network?
IP-Reach can be used in any computer network that
supports TCP/IP (and UDP). |
 |
Can IP-Reach accommodate multiple remote
connections at the same time?
IP-Reach TR364 and TR362 models enable 4 and 2
multiple user connections, respectively. In addition,
up to 5 multiple users can remotely connect to
IP-Reach and concurrently share control on a first
active keyboard/mouse input status on each available
channel. |
 |
Will other KVM switch brands work with
IP-Reach?
Nothing complements IP-Reach better than a Raritan
KVM Switch--especially Paragon. In theory, however,
IP-Reach can also be used with any KVM switch that
features an On-Screen User Interface menu for access
to switching functions. |
 |
Are there security features to protect
my Target Servers from an unauthorized remote
connection?
Yes. IP-Reach provides many layers of security.
IP-Reach can be configured to provide high-level
connection authentication and video data transfer
security during a remote session. User names, passwords,
private-keys, and Secure Socket Layer (SSL) 128-bit
encryption are all available. IP-Reach can also
function as a RADIUS client. In addition, all Raritan
KVM Switches that feature an On-Screen User Interface
(OSUI) come with a complete security scheme, requiring
user name and password access to Servers as designated
by the network administrator. |
 |
What is the slowest connection IP-Reach
can handle?
IP-Reach offers scalable performance based on
bandwidth available, down to 20kbps.
|
 |
Is special software required for the remote
PC?
Each IP-Reach ships with one copy of Raritan Remote
Client software. This remote access software runs
on any Remote PC with a Windows 98+ operating system
and communicates over Internet, LAN/WAN, or dial-up
modem with Raritan software on the IP-Reach unit.
With this installed, the Remote PC is like any
other user console in your KVM configuration, but
it can be located anywhere 3/4 around the corner,
or around the world.
|
 |
What types of computers can IP-Reach remotely
control?
IP-Reach works independently of a Target Server's
hardware, operating system, or application software,
accessing the Target Server's main input/output
devices--keyboard, video, and mouse. Consequently,
any hardware that supports standard PC keyboard
interfaces, standard PC mouse interfaces, and standard
PC video (VGA) can be used with IP-Reach. Currently,
IP-Reach support is strongest for Windows-based
Intel 86 servers, including HP, Dell, and Compaq.
Sun support for certain Raritan KVM Switches is
available with the proper Raritan converter products.
ASCII devices can also be connected via Raritan's
line of conversion products. IP-Reach does not
support Macintosh.
|
 |
Can IP-Reach be used without a KVM switch?
Yes. IP-Reach can be used to directly access individual
computers, connected to the keyboard, video, and
mouse ports of an independent computer. However,
its convenience and value is leveraged through
the use of a KVM switch.
|
 |
What is IP-Reach?
IP-Reach is the easiest, fastest, most reliable
way to remotely access and manage multiple servers
connected to a Raritan KVM Switch--no matter where
you are or where your servers are located.
|
 |
Which Raritan KVM Switches will work with
IP-Reach?
Currently Raritan supports the use of IP-Reach
with all Raritan KVM Switches that feature On-Screen
Display; Paragon, MasterConsole MX4, and MasterConsole
II.
|
 |
Can I use IP-Reach in a VPN?
Yes. IP-Reach fits into most any network configuration
utilizing standard TCP/IP. The network administrator
simply adds IP-Reach as a node on the network
via the IP-Reach Admin Console.
|
 |