Collecting Network Communication Logs

Collecting Network Communication Logs

Overview

To assist in troubleshooting, LanSchool Support may require you to gather logs from your network to help determine communication issues between the LanSchool Connection Server, Student and Teacher. 

The ability to read and write the Windows Registry is required. It is recommended to contact your local IT Support to setup logging.

Collecting Network Communication Logs when using a LanSchool Connection Server

  1. Download and install WireShark on the teacher, student, and LanSchool Connection Server.
  2. Download  DebugView from Microsoft onto the LanSchool Connection Server 
  3. Launch DebugView in Admin mode by right clicking the executable and selecting "Run As Administrator". 
  4. Select the View menu>>Capture Global Win 32
  5. On the LanSchool Connection Server, launch the LCS status page.   
  6. Once inside the Connection Service status page, click on Logging on the left hand pane.  Enter -1 in the Specific Students box, make sure all of the check boxes below it are checked, and then click Submit Query.  After you do this, you should see debug information in appear in DebugView. 
  7. On the teacher and student workstations, Browse to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\LanSchool for 64bit.  HKEY_LOCAL_MACHINE\SOFTWARE\LanSchool for 32bit.
  8. Click Edit>>New>>DWORD (32-bit) Value
  9. Name the value DebugTrace
  10. Restart both the teacher and student workstations.
  11. After the student and teacher relaunch, launch WireShark and start a capture on the student, teacher, and LCS. 
  12. Reproduce the problem.
  13. Stop the Wireshark packet capture on the LCS, teacher and student and save it. 
  14. Save a copy of the lsktrace.txt from the teacher and student machines. 
    1. To gather the lsktrace.txt from the student open a CMD prompt as Administrator. Type “CD %TEMP%” Then locate and save LskTrace.txt 
    2. To gather the lsktrace.txt from the the teacher, open File Explorer and type in %temp% in the address bar. Then locate and save LskTrace.txt 
  15. Save the output from DebugView on the LCS.
  16. Email all of the following to support@lanschool.com:
  1. Student:
    1. IP address
    2. Machine Name
    3. Username
    4. lsktrace.txt
    5. Wireshark packet capture

  2. Teacher
    1. IP address
    2. Machine Name
    3. Username
    4. lsktrace.txt
    5. Wireshark packet capture

  3. LanSchool Connection Server
    1. IP address
    2. DebugView output
    3. Wireshark packet capture

Once these are emailed, change the DebugTrace key on the teacher and student machines to 0, and reboot the machines.
Restart the LanSchool Connection Service to stop the logging on the server. 

Collecting Network Communication Logs only for Teacher and Student

  1. Download and install WireShark on the teacher, and student. 
  2. On the teacher and student workstations, Browse to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\LanSchool for 64bit.  HKEY_LOCAL_MACHINE\SOFTWARE\LanSchool for 32bit.
  3. Click Edit>>New>>DWORD (32-bit) Value
  4. Name the value DebugTrace
  5. Restart both the teacher and student workstations.
  6. After the student and teacher relaunch, launch WireShark and start a capture on the teacher and student. 
  7. Reproduce the problem.
  8. Stop the Wireshark packet capture on the teacher and student and save it.  
  9. Save a copy of the lsktrace.txt from the teacher and student machines. 
    1. To gather the lsktrace.txt from the student open a CMD prompt as Administrator. Type “CD %TEMP%” Then locate and save LskTrace.txt 
    2. To gather the lsktrace.txt from the the teacher, open File Explorer and type in %temp% in the address bar. Then locate and save LskTrace.txt 
  10. Email all of the following to support@lanschool.com:
    1. Student:
      1. IP address
      2. Machine Name
      3. Username
      4. lsktrace.txt
      5. Wireshark packet capture

    2. Teacher
      1. IP address
      2. Machine Name
      3. Username
      4. lsktrace.txt
      5. Wireshark packet capture
Once these are emailed, change the DebugTrace key on the teacher and student machines to 0, and reboot the machines.