Lindy Switch User Manual page 23

Addressing
When the LINDY KVM IP is situated within the local network, you will
need to give it an appropriate local IP address and IP network mask. This is
achieved most easily using the DHCP server option which will apply these
details automatically. If a DHCP server is not available on the network, then
these details need to be applied manually in accordance with the network
administrator.
The firewall/router must then be informed to route incoming requests to port
5900 or port 80 (if available) through to the local address being used by the
LINDY KVM IP.
LINDY KVM IP has a local
address and net mask, i.e.
IP
IP address: 192.168.0.3 Access Switch Plus
LOC REM VNC 100 LNK PWR
Net mask: 255.255.255.0
Remote user with VNC
viewer accesses IP
address: 129.7.1.10 and
Internet
automatically uses port
5900.
Firewall/router address:
...0
The firewall routes the
request from the VNC viewer
on port 5900 through to the
LINDY KVM IP at local address
192.168.0.3
To discover a DHCP-allocated IP address
Once a DHCP server has allocated an IP address, you will need to know it in
order to access the LINDY KVM IP via a network connection. To discover the
allocated IP address:
local
1 In the Network configuration screens, set the 'Use DHCP' option
to 'Yes' and select 'Save'. Once the page is saved, the LINDY KVM IP will
contact the DHCP server and obtain a new address.
2 Re-enter the same 'Network configuration' screen where the new IP address
and network mask should be displayed.
DNS addressing
As with any other network device, you can arrange for your LINDY KVM IP to be
accessible using a name, rather than an IP address. This can be achieved in two
main ways:
• For small networks that do not have a DNS (Domain Name System) server,
edit the 'hosts' files on the appropriate remote systems. Using the hosts file,
you can manually link the LINDY KVM IP address to the required name.
• For larger networks, declare the IP address and required name to the DNS
server of your local network.
The actual steps required to achieve either of these options are beyond the
scope of this document.