How to capture packets with Wireshark

If you face some problem, especially, if you can access to your file server from your client machine (mainly, Windows) normally, but you cannot access to the file server with File System for Windows on your Chromebook, the File System for Windows absolutely has a problem. And, other users also may have the same problem which you faced. You can contribute to help such users.

First, you can collect the debug output log from a console tab on DevTools by How to Capture the Console Log of DevTools. I can understand each response detail from the log, but I cannot know why the target server returned the error code from the log. When some users posted an issue to Github, I replied that "Please give me a server log". Then, I received the server log, but unfortunately, I could not find the reason of the error code.

Most users said that "I can access to the server from other machines". To improve the File System for Windows app, please send packets communicated between the client and the server to me. That is, the packets represent a correct way. When I get them, I can find the difference from my implementation. Then, you and other users would be able to use a new File System for Windows for the target server.

To capture packets, you can use a tool named "Wireshark".