Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Dell Wyse ThinOS Release 8.3.1 Administrator’s Guide

PDF

Using the Trouble Shooting Options

Use the Trouble Shooting dialog box to configure Trace and Event log settings, performance monitor graphs that display client CPU, Memory, and Networking information, and CMOS management extract and restore cmos settings as described in CMOS Local Management: Extracting CMOS Settings to a USB Key for Distribution . It also allows you to view wnos.ini cached information for troubleshooting purposes.

To use the trouble shooting options:
  1. From the desktop menu, click Trouble Shooting. The Trouble Shooting dialog box is displayed.

  2. Click the General tab, and use the following guidelines:
    1. Click either USB or File Server to select your target device you want to use for CMOS management.
    2. Extract CMOS — Click this option to extract the CMOS settings to the USB Key or file server based on your target device selection.
    3. Restore CMOS — Click this option to write the CMOS settings from the USB Key to the target thin client.
    4. Performance Monitor — Click this option to display your thin client CPU, Memory, and Networking information. The graphs display on top of all windows.
    5. Force Coredump — Use this option to forcibly generate the debug information for technical investigation when your system is not responding.
  3. Click the Trace tab to configure the trace actions and Delay on Trace. The available options for Trace action are None, Capture, and Playback.

  4. Click the Capture tab to configure the Export Event Log, Network Capture to USB, Wireless Capture to USB, and USB DEV Trace.

    If you want to enable the error messages, use the following guidelines:

    • Click either One-time or Persistent option to enable logging the unexpected error message.

    • Turn off logging and then check the log file under the folder ftp:/wnos/trouble_shoot.

    • Be sure to enable the Enable Trace option of the Privilege parameter in a wnos.ini file. For more information, see Dell Wyse ThinOS INI Guide.

    • Use the Network capture to USB option to enable the capture of network information, that is, a network trace of all traffic coming in and out of the thin client to a USB drive that is inserted into the thin client.

      After login and use of the XenDesktop server or network, you will see a ThinOS_WS.pcap file in the USB drive which you can analyze using software such as a packet analyzer used for network troubleshooting, and analysis.
      • NOTE:

        Ensure that you have inserted the USB drive into the thin client before selecting the Network capture to USB option. The Network capture to USB option is automatically cleared, if there is no USB drive inserted and you exit the dialog box, or after restarting the thin client; if needed, you must select the option again.

  5. Click the Ping tab, and use the following guidelines to execute the ping diagnostic utility and display response messages:

    1. Enter Hostname or IP — Enter the IP address, DNS-registered host name, or WINS-registered host name of the target to be pinged.
    2. Data area — Displays ping response messages. The ping command sends one echo request per second, calculates round trip times and packet loss statistics, and displays a brief summary upon completing the calculation.
    3. Start — Executes the ping command. If the host is operational and on the network, it responds to the echo request. By default, echo requests are sent until interrupted by clicking Stop.
    4. Stop — Terminates the ping request and leaves the Ping dialog box open, so you can read the summary posted in the data area.
    • NOTE:

      Ping sends an echo request to a network host. The host parameter is either a valid host name or an IP address. If the host is operational and on the network, it responds to the echo request. Ping sends one echo request per second and calculates round trip times and packet loss statistics. It displays a brief summary upon completion of the calculation.

      The ping utility can be used to:
      • Determine the status of the network and various foreign hosts.

      • Track and isolate hardware and software problems.

      • Test, measure, and manage networks.

      • Determine the IP address of a host if only the host name is known.

    • IMPORTANT:

      Not all network equipment will respond to ping packets, as this is a common mechanism used in denial-of-service attacks. Lack of response does not necessarily indicate that the target of the ping is unusable for other purposes.

  6. Click the Trace Route tab to execute the tracert diagnostic utility and display response messages. Use the following guidelines:
    1. Enter Hostname or IP — Enter the IP address, DNS-registered host name, or WINS-registered host name of the target to be traced.
    2. Data area — Displays round-trip response time and identifying information for each device in the path.
    3. Start — Executes the tracert command.
    4. Stop — Terminates the tracert command and leaves the Trace Route dialog box open, so that you can read the information posted in the data area. The tracert utility traces the path from your thin client to a network host. The host parameter is either a valid host name or an IP address. The tracert utility sends out a packet of information three times to each device (routers and computers) in the path and displays the round trip response times and identifying information in the message box.
  7. Click OK to save the settings.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\