Filter
Top Products
Appendix D: FAQs
316
How many TCP ports must be open on my firewall in order to
enable network access to the KX II? Are these ports configurable?
Only one. The KX II protects network security by only requiring access to
a single TCP port to operate. This port is completely configurable for
additional security.
Note that, of course, to use the KX II's optional web browser capability,
the standard HTTPS port 443 must also be open.
Does the KX II require an external authentication server to operate?
No. The KX II is a completely self-sufficient. After assigning an IP
address to the KX II, it is ready to use. Its web browser and
authentication capabilities are completely built-in.
If an external authentication server (such as LDAP, Active Directory,
RADIUS, etc.) is used, the KX II allows this as well, and will even failover
to its own internal authentication should the external authentication
server become unavailable. In this way, the KX II's design philosophy is
optimized to provide ease of installation, complete independence from
any external server, and maximum flexibility.
Can the KX II be used with CITRIX?
The KX II may work with remote access products like CITRIX if
configured appropriately, but Raritan cannot guarantee it will work with
acceptable performance. Products like CITRIX utilize video redirection
technologies similar in concept to digital KVM switches so that two
KVM-over-IP technologies are being used simultaneously.
Can the KX II use DHCP?
DHCP addressing can be used, however, Raritan recommends fixed
addressing since the KX II is an infrastructure device and can be
accessed and administered more effectively with a fixed IP address.
I'm having problems connecting to the KX II over my IP network.
What could be the problem?
The KX II relies on your LAN/WAN network. Some possible problems
include:
Ethernet autonegotiation - On some networks, 10/100
autonegotiation does not work properly and the KX II unit must be
set to 100MB/full duplex or the appropriate choice for its network.
Duplicate IP address - If the IP address of the KX II is the same as
another device, network connectivity may be inconsistent.
Port 5000 conflicts - If another device is using port 5000, the KX II
default port must be changed (or the other device must be changed).
When changing the IP address of the KX II or swapping in a new KX II,
sufficient time must be allowed for its IP and MAC addresses to be
known throughout the Layer 2 and Layer 3 networks.