Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell Wyse ThinOS Version 9.0 Administrator’s Guide

PDF

Troubleshooting your thin client

About this task

You can use the troubleshooting options on the ThinOS desktop to troubleshoot your device.

Steps

  1. From the desktop menu, click Troubleshooting.
    The Troubleshooting dialog box is displayed.
  2. Click the General tab, and use the following guidelines:
    Figure 1. General
    General
    • Click the Performance Monitor option to display the CPU usage history with the Memory, and Networking information. The graphs display on top of all windows.
    • Click the Export System Setting option to export the system settings file to the USB drive that is connected to the thin client. Password is mandatory for the exported file. The file is stored in the /wnos/trouble_shoot/ folder of the USB drive.
    • Click the Export Screenshot option to export the system screenshots to the USB drive that is connected to the thin client. The file is stored in the root folder of the USB drive.
    • Click the Export logs option to export the system log files to the USB drive that is connected to the thin client. The file is stored in the root folder of the USB drive—system_log_201910107_125610.tgz.
    • Click the Import System Setting option to import the system settings file from the USB drive that is connected to the thin client. The file is stored in the /wnos/trouble_shoot/ folder of the USB drive.
  3. Click the Capture tab, and do the following:
    Figure 2. Capture
    Capture
    • Capture Network Packets—Use this option to capture network-related logs.
      1. Connect a USB drive to the thin client.
      2. To start logging the unexpected error messages, enable the Capture Network Packets option, and click OK.
      3. To stop logging the unexpected error messages, disable the Capture Network Packets option, and click OK.
      4. Open the Troubleshooting window, and click Export Logs on the General tab. The log file is stored in the root folder of the USB drive—system_log_201910107_125610.tgz.
      5. Extract the tgz file. The log files are available at ./var/log/netmng/.
    • Capture Wireless Packets—Use this option to capture wireless network-related logs.
      1. Connect a USB drive to the thin client.
      2. To start logging the unexpected error messages, enable the Capture Wireless Packets option, and click OK.
      3. To stop logging the unexpected error messages, disable the Capture Wireless Packets option, and click OK.
      4. Open the Troubleshooting window, and click Export Logs on the General tab. The log file is stored in the root folder of the USB drive—system_log_201910107_125610.tgz.
      5. Extract the tgz file. The log files are available at ./var/log/netmng/.
    • Capture USB Packets—Use this option to capture USB packets.
      1. Connect a USB drive to the thin client.
      2. To start logging the unexpected error messages, enable the Capture USB Packets option, and click OK.
      3. To stop logging the unexpected error messages, disable the Capture USB Packets option, and click OK.
      4. Open the Troubleshooting window, and click Export Logs on the General tab. The log file is stored in the root folder of the USB drive—system_log_201910107_125610.tgz.
      5. Extract the tgz file. The log files are available at ./compat/linux/var/usbdump/.
  4. Click the Ping tab, and do the following:
    Figure 3. Ping
    Ping
    1. Enter the IP address, DNS-registered hostname, or WINS-registered hostname of the target.
    2. Click Start.
      The data area displays the 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. 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.
    NOTE

    Ping sends an echo request to a network host. The host parameter is either a valid hostname 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.

    NOTE Not all network equipment responds to ping packets, as it is a common mechanism that is used in denial-of-service attacks. Lack of response does not necessarily indicate that the target of the ping is unusable for other purposes.
  5. Click the Trace Route tab, and do the following:
    Figure 4. Trace Route
    Trace Route
    1. Enter the IP address, DNS-registered hostname, or WINS-registered hostname of the target.
    2. Click Start.
      The data area displays round-trip response time and identifying information for each device in the path.

    The tracert utility traces the path from your thin client to a network host. The host parameter is either a valid hostname or an IP address. The tracert utility sends out a packet of information three times to each device (routers and computers) in the path. The round-trip response time and the identifier information are displayed in the message box.

  6. Click the Telnet tab, and do the following:
    Figure 5. Telnet
    Telnet
    1. Click Telnet.
    2. Enter the hostname.
    3. Enter a port number.
    4. Select a color theme.
    5. Click Connect to connect to a remote host or device.
  7. Click OK to save your 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: <>()\