Establishing a Server Environment 19
Configuring DNS
Thin clients accept valid DNS names registered on a DNS server available to the
enterprise intranet. In most cases, DNS is not required but may be used to allow hosts to
be accessed by their registered DNS names rather than their IP addresses. Every
Windows DNS server in Windows 2000 and later includes Dynamic DNS (DDNS) and
every server registers dynamically with the DNS server. There are also DDNS
implementations available for *NIX environments. However, the thin client does not do
dynamic registration, and therefore, requires a static or non-variant IP address and
manual DNS registration in order to provide LPD support by name (for example, in the
case where the thin client is used as an LPD printer server or if DHCP is not available).
For DHCP entry of DNS domain and server location information, refer to "Configuring
Configuring WINS
The thin client does not do dynamic registration and therefore, requires a static or
non-variant IP address and manual Windows Internet Naming Service (WINS)
registration. Use the network address of an available WINS name server. WINS allows the
thin client user to specify remote systems by their host names rather than IP addresses. If
a specific IP address (instead of a name) is entered for a connection, it rather than WINS
will be used to make the connection. These entries are supplied through DHCP, if DHCP is
You may use two WINS server addresses, separated by a semicolon,
comma, or space. The first address is for the primary WINS server and the
second address is for a backup WINS server.
Configuring Wyse Device Manager Servers
Wyse Device ManagerTM (WDM) servers provide network management services to the
thin client (complete user-desktop control—with features such as remote shadow, reboot,
shutdown, boot, rename, automatic device check-in support, Wake-On-LAN, change
device properties, and so on). Use the IP addresses or host names with optional TCP port
number for WDM servers. Each entry with optional port number is specified in the form
IP:port or name:port, where :port is optional (if not specified, port 80 is used).
Configuring Wireless Access
Thin clients running Wyse ThinOS can support 802.11b/g/n wireless connections. WEP is
used as the encryption method in 802.11b wireless access. WEP, WPA-Personal,
WPA2-Personal, WPA-Enterprise and WPA2-Enterprise are used as the encryption and
authentication methods in 802.11g/n wireless access. For a wireless access point, Cisco,
TP-Link, and D-Link products are recommended. For a Radius server used in EAP-TLS,
the IAS, FreeRadius and Cisco ACS are recommended.
Internet Authentication Service (IAS) is the Microsoft implementation of a
Remote Authentication Dial-in User Service (RADIUS) server and proxy. As
a RADIUS server, IAS performs centralized connection authentication,
authorization, and accounting for many types of network access; including
wireless and virtual private network (VPN) connections.
The FreeRADIUS Server is a daemon for unix and unix-like operating
systems which allows you to set up a radius protocol server (which can be
Terms of Use | Privacy Policy | DMCA Policy
2006-2020 Rsmanuals.com