Specifications
143
Preparing the DHCP server (Linux)
The 2X ThinClientServer is shipped with DHCP Helper application
as standard. This is included in both the Standard and Enterprise
editions. The use of such a utility is sometimes not desired due to
various reasons:
• The 2X ThinClientServer was installed on the DHCP
Server/Domain Controller
• The DHCP server is already handling PXE booting for other
software in your network and the admin policy is to use the
3
rd
party software
• The PXE stack installed on the Thin Client is prior to version
2.0 or else has some incompatibilities.
It is IMPORTANT that if you are serving settings directly via your
DHCP server, that you do NOT send out conflicting settings by the
bundled ThinClientServer. It is important that you accordingly
disable the service or use the Whitelist/Blacklist functionality to
avoid conflicting multiple broadcasts which can give sporadic
errors.
If your thin client will be booting via PXE or Etherboot, you have to
configure your DHCP server to tell the thin clients where the TFTP
server is located in order to download 2X ThinClientOS. To do this
you will need to add the highlighted settings in the configuration file
for your DHCP server. We are providing a sample configuration
which you can use as a template. The text in gray is required to
enable PXE booting with 2X ThinClientServer. The text in red
should be replaced with the IP address of where the 2X
ThinClientServer is installed. The text in blue should be replaced
with the IP address of where the TFTP server is installed. All IP
addresses and ranges should be changed appropriately for your
network.
option domain-name "2x.com";
option domain-name-servers 192.168.0.1;
option routers 192.168.0.1;
option thinsrv code 193 = array of ip-address;
ddns-update-style none;
default-lease-time 3600;
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.128 192.168.0.254;
default-lease-time 3600;
max-lease-time 172800;