Dell Wyse ThinOS Version 8.6 Administrator’s Guide

Configuring the ENET settings

1. From the desktop menu, click System Setup, and then click Network Setup.
   The Network Setup dialog box is displayed.
2. Click the ENET tab, and use the following guidelines:

   

   

   1. Ethernet Select—Allows you to select the wired network connection. For Wyse 5070 thin client without SFP or RJ-45 module, the ENET0 option is selected by default. For Wyse 5070 thin client with SFP or RJ-45 module, select either ENET0 or ENET1 based on your network preference.
   2. Ethernet Speed—The default value is Auto-Detect. If your network equipment does not support the automatic negotiation, select any of the available options—10 MB Half-Duplex, 10 MB Full-Duplex, 100 MB Half-Duplex, 100 MB Full-Duplex, or 1 GB Full-Duplex.
      The 10 MB Full-Duplex option can be selected locally. However, this mode can be negotiated through Auto-Detect.
   3. The IPv4 check box is selected by default. Click Properties to configure the following options:
      • Dynamically allocated over DHCP/BOOTP—Select this option to enable your thin client to automatically receive information from the DHCP server. The network administrator must configure the DHCP server by using DHCP options to provide information. Any value that is entered locally in the Options tab is replaced by the DHCP value. If the DHCP server fails to provide replacement values, the locally entered value is used.
      • Statically specified IP Address—Select this option to manually enter the IP address, subnet mask, and default gateway.
        • IP Address—Enter a valid network address in the server environment. The network administrator must provide this information.
        • Subnet Mask—Enter the value of the subnet mask. A subnet mask is used to gain access to machines on other subnets. The subnet mask is used to differentiate the location of other IP addresses with two choices—same subnet or other subnet. If the location is a different subnet, messages that are sent to that address must be sent through the default gateway. This does not depend on the value that is 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.
   4. Select the IPv6 check box, and then click Advanced to select various IPv6 supported setting options from the available check boxes.
      The following check boxes are displayed in the IPv6 Advanced Settings dialog box:

      • Allow IPv4 to be disabled when IPv6 is enabled
      • Prefer IPv4 over IPv6 when both are available
      • Disable Stateless Address autoconfiguration (SLAAC)
      • Disable Duplicate Address Detection (DAD)
      • Disable ICMPv6 Echo Reply
      • Disable ICMPv6 Redirect Support
      • Use Standard DHCPv6 timers
      Click Properties, and use the following guidelines:

      • Wait DHCP—Select this option to enable your thin client to consider IPv6 DHCP before you log in. If you do not select this option, and DHCP is enabled, the system still waits for IPv4 DHCP.
      • Dynamically allocated over DHCP/BOOTP—Select this option to enable 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 that is entered locally in the Options tab is replaced by the DHCP value. If the DHCP server fails to provide replacement values, the locally entered value is used.
      • Statically specified IP Address—Select this option to manually enter the IP address, subnet mask, and default gateway.
        • IP Address—Enter a valid network address in the server environment. The network administrator must provide this information.
        • Subnet Prefix Len—Enter the prefix length of the IPv6 subnet.
        • Default gateway—Use of gateways is optional. For more information, see various IPv4-supported options 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 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 provides this value, it replaces any locally configured value. If the DHCP server does not provide this value, the locally configured value is used.

      NOTE: If you enable IPv6 for both ENET0 and ENET1, IPv6 routes through the Ethernet connection that fetches the IPv6 address first.
   5. Select the Enable the IEEE802.1x authentication check box, and from the EAP type drop-down list, select TLS, LEAP, PEAP or FAST.
      • TLS—Select this option, and click Properties to 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. The server certificate text field supports a maximum of approximately 255 characters, and supports multiple server names.
        • Select the Connect to these servers check box, and enter the IP address of server.
        • Click Browse to find and select the client certificate file and the private key file you want.
          NOTE: Ensure that you select the PFX file only.
        • From the Authenticate drop-down list, select either user authentication or machine authentication that is based on your choice.

          The following kinds of server names are supported—all examples are based on Cert Common name company.dell.com:

          • *.dell.com
          • *dell.com
          • *.com
        NOTE: Using only the FQDN, that is, company.dell.com does not work. Use one of the options, for example servername.dell.com (*.dell.com is the most common option as multiple authentication servers may exist).
      • LEAP—Select this option, and click Properties to 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 31 characters.
      • PEAP—Select this option, and click Properties to configure the Authentication Properties dialog box. Be sure to select either EAP_GTC or EAP_MSCHAPv2, and then use the correct username, password, and domain. Validate Server Certificate is optional.
      • FAST—Select this option, and click Properties to configure the Authentication Properties dialog box. Be sure to select either EAP_GTC or EAP_MSCHAPv2, and then use the correct username, password, and domain. Validate Server Certificate is optional.

        To configure EAP-GTC, enter the username only. The password or PIN is required during the authentication process. To configure EAP-MSCHAPv2, enter the username, password, and domain.

        NOTE: The domain\username in the username box is supported, but you must leave the domain box blank.
        The CA certificate must be installed on the thin client, and the server certificate validated forcibly. When EAP-MSCCHAPV2 is selected for PEAP or FAST authentication, an option to hide the domain is available. Username and Password boxes are available for use, but the domain text box is disabled.

        When EAP-MSCHAPV2 is selected for PEAP or FAST authentication, a check box to enable the Single Sign-On feature is available.

        From ThinOS 8.3, EAP-FAST authentication is supported. During the initial connection, when there is a request for a Tunnel PAC from the authenticator, the PAC is used to complete the authentication. The first-time connection always fails, and the subsequent connections succeed. Only automatic PAC provisioning is supported. The user/machine PAC provisioning that is generated with CISCO EAP-FAST utility is not supported.

3. Click OK to save the settings.
   NOTE: From ThinOS version 8.5, client reboot is not required to change the network settings. All the changes take effect immediately.
   For example, ThinOS connects to the new wireless SSID immediately without reboot.