Dell ThinOS 2402 Administrator’s Guide

Troubleshooting your thin client

1. From the desktop menu, click Troubleshooting.
   The Troubleshooting dialog box is displayed.
2. Click the General tab, and use the following guidelines:
   • Click Extract CMOS to extract the CMOS settings and certain BIOS settings to the USB drive or file server that is based on your target device selection.
   • Click the Restore CMOS option to write the CMOS settings and BIOS settings from the USB drive to the target thin client.
   • 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. When you play videos using MMR or HTML5 in a Citrix session, FPS is displayed on the performance monitor graph under the CPU tab. VMware Horizon Blast does not support this function in ThinOS version 9. 3112.
   • Click the Force Coredump option to forcibly generate the debug information for technical investigation when your system is not responding. Both the coredump file and the trap information image are saved to the local drive. After you restart the thin client, both coredump file and trap issue screenshots are uploaded to the /wnos/troubleshoot/ directory of the file server or a USB drive.
   • Click the Export System Setting option to export the system settings file to the USB drive that is connected to the thin client. The 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.
     NOTE:From ThinOS 9.1.5xxx onwards, you can export logs to a USB drive with NTFS format.
   • 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.
     NOTE:From ThinOS 9.1.5xxx onwards, you can import files to a USB drive with NTFS format.
   • Click the Clear Log option to delete all logs. After you clear logs, you must reboot the client to generate the logs again.
3. Click the Capture tab, and do the following:
   • Capture Network Packets—Use this option to capture network-related logs.
     1. To start logging the unexpected error messages, enable the Capture Network Packets option, and click OK.
     2. To stop logging the unexpected error messages, disable the Capture Network Packets option, and click OK.
     3. Connect a USB drive to the thin client.
     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/log/netmng/..
   • Capture Wireless Packets—Use this option to capture wireless network-related logs.
     1. To start logging the unexpected error messages, enable the Capture Wireless Packets option, and click OK.
     2. To stop logging the unexpected error messages, disable the Capture Wireless Packets option, and click OK.
     3. Connect a USB drive to the thin client.
     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/log/netmng/..
   • If you want to capture the network-related logs for a long time, insert the USB drive, and enable Capture Network/Wireless/Packets option. The captured network-related log is directly stored in the U disk ./wnos/trouble_shoot/ folder. If you want to capture network-related logs for a long time, follow these steps:
     1. Connect a USB drive to the thin client.
     2. Enable the Capture Network/Wireless/Packets option.
     3. Disable the Capture Network/Wireless/Packets option.
     4. Remove the USB drive as a personal device is required to read it.
     5. The network captures should be in ./wnos/trouble_shoot/.
   • 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/.
   • Capture User Coredump—Use this option to capture coredump files.
     1. Connect a USB drive to the thin client.
     2. To start logging the unexpected error messages, enable the Capture User Coredump option, and click OK.
     3. To stop logging the unexpected error messages, disable the Capture User Coredump 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/.
   • Capture Debug Logs—Use this option to capture the debug logs.
     1. Connect a USB drive to the thin client.
     2. Enable the Capture Debug Logs option to set all log levels to the highest debug level.

        Capture Debug Logs is displayed at the bottom-right corner.

     3. Reboot the thin client.
     4. Disable Capture Debug Logs to set all log levels to default debug levels.
     5. Set the log file. The log file is automatically stored in the root folder of the USB drive—system_log_201910107_125610.tgz.
4. Click the Ping tab, and do the following:
   NOTE:If you want to ping IPv6, you must first obtain the IPv6 address, and then enter the IPv6 address in the Ping input box. If you are entering the FQDN of IPv6, add -6 to the end of the FQDN.
   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:
   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 systems) 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:
   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 the Network tab, and view detailed information that is related to your network connection.
   • Click the Diagnostics button to run a diagnostic test on your network connection.
   • Click the Export log button to export the network logs to the target device.
8. Click OK to save your settings.