Table of Contents
Advertisement
Topics:
•
Using Dynamic Host Configuration Protocol (DHCP)
•
Using Domain Name System (DNS)
Using Dynamic Host Configuration Protocol (DHCP)
A thin client is configured to obtain its IP address and network configurations from a DHCP server. The DHCP server provides
the IP address or DNS name of the FTP server and the FTP root-path location of the software in Microsoft.msi. This can be
used to access the FTP server by using the DHCP upgrade process.
It is recommended that you configure and upgrade thin clients by using DHCP, as it saves time and effort to complete the
processes locally on multiple thin clients. If a DHCP server is not available, fixed IP addresses can be assigned, which must be
entered locally for each thin client.
A DHCP server provides the IP address of the WDM server. For more information on remote administration, see
for remote administration
Using Domain Name System (DNS)
Thin client devices accept valid DNS names registered on a DNS server that is available to the enterprise intranet. The thin
client device sends a query to the DNS server on the network to resolve hostnames into IP addresses. DNS allows hosts to be
accessed by using the registered DNS names.
The Windows DNS server in Windows 2000 and later versions includes Dynamic DNS (DDNS), and each server registers
dynamically with the Windows DNS server. For information on DHCP entry of DNS domain and server location, see
Dynamic Host Configuration Protocol
60
Networks
(DHCP).
7
Networks
WDM software
Using
Advertisement
Table of Contents
