Administrator Guide

Table Of Contents
Network architecture and server
environment
This section contains information about the network architecture and enterprise server environment needed to provide network
and session services for your thin client.
Understanding how to configure your network
services
Network services provided to thin clients can include DHCP, FTP file services, and DNS. You can configure, design, and manage
your network services depending on the availability in your environment.
You can configure your network services using:
Dynamic Host Configuration Protocol (DHCP)
Domain Name System (DNS)
Using Dynamic Host Configuration Protocol
A thin client is initially configured to obtain its IP address and network configurations from a Dynamic Host Configuration
Protocol (DHCP) server. A DHCP server provides the IP address or DNS name of the FTP server and the FTP root-path location
of software in Microsoft.msi form to access the IP address and network configurations through the DHCP upgrade process.
DHCP is recommended to configure and upgrade thin clients as it saves time and efforts needed to complete these processes
locally on multiple thin clients. If a DHCP server is not available, fixed IP addresses can be assigned and it must be entered
locally for each device.
A DHCP server can also provide the IP address of the WMS server.
DHCP options
The DHCP options listed in the following table are accepted by the thin clients.
Table 28. DHCP options
Option Description Notes
1 Subnet Mask Required
3 Router Optional but recommended. It is not
required unless the thin client must
interact with servers on a different
subnet.
6 Domain Name Server (DNS) Optional but recommended
12 Hostname Optional
15 Domain Name Optional but recommended
43 Vendor Class Specific Information Optional
50 Requested IP Required
51 Lease Time Required
7
56 Network architecture and server environment