netsh trace with report=yes

ตอบทั้งหมด

• 23 เมษายน 2553 7:45

   

   
  

  0

  Hi Detlef,

  Thanks for the post.

  Please understand that the report.html file that includes additional information about the trace events and the other information collected is included in the Cab file. Please extract the Cab file and check it.

  For more information about Netsh Trace, please refer to the following article:

  http://msdn.microsoft.com/en-us/library/dd569142(VS.85).aspx

  Hope this helps.

  Miles

  • ทำเครื่องหมายเป็นคำตอบโดย Miles Zhang 7 พฤษภาคม 2553 2:28
  •  
   
• 23 เมษายน 2553 9:21

   

   
  

  0

  Hi Miles,

  that is not the file I want to. This file is standard output without "report=yes" Standard is:

  NetTrace.etl

  NetTrace.cab

  Inside cab is report.html which which is the "starter" for all other files and inside cab is a report.etl which is a copy of NetTrace.etl.

  With "report=yes" there should be a file called NetTrace.html. So far the documentation. But this file I'm not able to produce.

  And evaluating this answer:

  Netsh Command for Network Trace

  brought a lot more differences between documentation and real world. If you follow the doc the standard should not be like I said above.

  Kind regards

  Detlef

   

  Here are some pictures I try to follow:

  1st statement about output files

  2nd statement about output files

  files in output directory

   

   

   

   

   

   
• 23 เมษายน 2553 9:43

   

   
  

  0

  Hi Detlef,

  Thanks for the update.

  Please understand that the report.html file will not include additional information if the "report=yes" parameter is not added. The "report.html" file is exactly the HTML file you are looking for.

  At this point, we may test them and compare the results.

  Thanks,

  Miles

   

   

   
• 23 เมษายน 2553 10:54

   

   
  

  0

   

  ThanQ, Miles.

  I will test a little bit more. But what is NetTrace.html?

  Detlef

   

  I did it:

  netsh trace start scenario=wlan

  • expected: The diagnostic results will display, but neither the ETL nor CAB files are created. (MS)

  • reality: no display, but both files ETL and CAB are created

  netsh trace start scenario=wlan report=yes

  • expected: The diagnostic results will display, and both ETL and CAB files are created. Only events are saved in the ETL file; no packets are saved. (MS)

  • reality: maybe (did not check etl file), but more xml files are included in CAB file

  netsh trace start scenario=wlan report=no

  • expected: The diagnostic results will display, ETL file is created with trace events only. The CAB file is not created. (MS)

  • reality: both files ETL and CAB are created (the same like without the report parameter)

  netsh trace start scenario=wlan capture=yes

  • expected: The diagnostic results will display, and only ETL file is created. The ETL file is created with both traces and packets. (MS)

  • reality: no display, but both files ETL and CAB are created

  netsh trace start scenario=wlan capture=no

  • expected: The diagnostic results will display, ETL file is created with trace events only. The CAB file is not created. (MS)

  • reality: no display, but both files ETL and CAB are created

  SUMMARY:

  the documentation for this new command is totally wrong.

  Detlef

   

  • ทำเครื่องหมายเป็นคำตอบโดย Detlef Knut 7 พฤษภาคม 2553 10:22
  •