Network drive not showing up in Wireshark File dialog
Hello, I have an really odd issue on my main PC. On my home network I have a Samba server for file sharing. I can open the share just fine in windows file explorer and every other application with wireshark being the exception. I've done some captures and it seems that wireshark isn't sending an SMB file request. It works without issue on every other computer in my home so I've ruled out the server. I've checked versions, turned firewall off, enabled network discovery, etc etc etc. Has anyone ever ran across an issue like this with wireshark that seems to be application specific?
You've a Samba server for file sharing, which you can access from applications on workstations on your home network. So far nothing out of the ordinary. But you can't open a file on the Samba server from Wireshark, is that what you're saying? So File | Open... doesn't allow you to browse to the Samba share? What does that have to do with the title of the question: Network Devices not showing up? What network interfaces are you talking about then in this context? Wired Ethernet, WiFi?
Using Wireshark 3.0, saving a file from Wireshark to an SMB share using a unc path, e.g.
\\host\path\to\fileworks for me. Note the remote host is running Windows, so no Samba involved.Do you possibly mean that the Samba server doesn't appear under the "Network" option in the file save\open dialog?
Can you elaborate in a more detail what you are trying to do (step by step guide)?
This is what I am doing step by step.
If I open file explorer from any other application network devices is listed as an option. On other machines in my home the network devices are listed with two drives when I do the same thing in wireshark.
Grahamb, putting \host\path\to\file in the filename seems to work as a work around. I was putting the drive letter in front of it before with no success.
So the Samba file server is a "mapped" network drive? I just mapped a drive letter to my other Windows host, and now that shows up as you said under "Network locations" in the "This PC" section.
What I have noticed is that odd things happen on Windows 10 depending on how the remote server is mapped. I created the mapping from "File Explorer".
Yes it is a mapped network drive. I have tried mapping it with both the IP and the server name. When I open up wireshark I don't even have network devices as an option after clicking on My PC. I can see the drives and access them just fine in other applications however.