Users Guide

the Default Gateway, whether specified through local configuration or through DHCP. The network administrator
must provide this value.
○ Default Gateway — Use of gateways is optional. Gateways are used to interconnect multiple networks (routing
or delivering IP packets between them). The default gateway is used for accessing the internet or an intranet with
multiple subnets. If no gateway is specified, the thin client can only address other systems on the same subnet.
Enter the address of the router that connects the thin client to the internet. The address must exist on the same
subnet as the thin client as defined by the IP address and the subnet mask. If DHCP is used, the address can be
supplied through DHCP.
c. Select the IPV6 check box, and then click Advanced to select various IPV6 supported setting options from the available
check boxes.
d. Click properties and use the following guidelines:
● Wait DHCP — Selecting this option enables your thin client to wait for IPV6 DHCP before the sign-in, if not selected
the system will only wait for IPV4 DHCP if enabled.
● Dynamically allocated over DHCP/BOOTP — Selecting this option enables your thin client to automatically
receive information from the DHCP server. The network administrator must configure the DHCP server (using DHCP
options) to provide information. Any value provided by the DHCP server replaces any value entered locally on the
Optionstab, however, locally entered values are used if the DHCP server fails to provide replacement values.
● Statically specified IP Address — Select this option to manually enter the IP Address, Subnet Mask and Default
Gateway.
○ IP Address — Must be a valid network address in the server environment. The network administrator must
provide this information.
○ Subnet Mask — Enter the value of the subnet mask. For more information, see various options supported by
IPV4 in this section.
○ Default Gateway — Use of gateways is optional. For more information, see various options supported by IPV4 in
this section.
● DNS Servers — Use of DNS is optional. DNS allows you 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 is rather than DNS is used to
make the connection. Enter the network address of an available DNS server. The value for this box may be supplied
by a DHCP server. If the DHCP server supplies this value, it replaces any locally configured value. If the DHCP server
does not supply this value, the locally configured value is used.
e. Select the check box to enable IEEE802.1x Authentication.
● EAP Type — If you have enabled the Enable IEEEE 802.1x authentication check box, select the EAP Type option
you want (TLS, LEAP or PEAP).
● TLS — If you select the TLS option, click Properties to open and configure the Authentication Properties dialog
box.
○ Select the Validate Server Certificate check box because it is mandatory to validate your server certificate.
NOTE:
The CA certificate must be installed on the thin client. Also note that the server certificate text field
supports a maximum of approximately 127 characters, and supports multiple server names.
○ If you select the Connect to these servers check box, the box is enabled where you can enter the IP address of
server.
○ Click Browse to find and select the Client Certificate file and Private Key file you want.
The following kinds of server names are supported — all examples are based on Cert common name company.dell.com
NOTE:
Using only the FQDN, that is company.wyse.com does not work. You must use one of the options (note that
*.dell.com is the most common option as multiple authentication servers may exist): servername.dell.com
*.dell.com
*dell.com
*.com
f.
LEAP — If you select the LEAP option, click Properties to open and configure the Authentication Properties dialog
box. Be sure to use the correct username and password for authentication. The maximum length for the username or the
password is 64 characters.
12
Wyse 3040 thin client on ThinOS