Bug:
SMB Client does not autoconnect. My setup includes a TP-Link TL-WR802N N300 WLAN Nano Router.
It does work when i connecting manually.
I did not reproduce this issue. I connected through an Ethernet cable and after a power outage and restart, I was able to directly open the remote mounting path directory.
It may be due to differences in the network environment.
I have the same problem as eTobey: Auto-connect for the SMB
Client does not work. After power-cycling the scope, it has remembered all the SMB details (path, user, password), but I need to open the Utility > Menu > Service > SMB File Share > Client dialog and press "Connect" to manually re-establish the connection.
The SMB
Server will restart automatically. This is my preferred way of exchanging data anyway: I can save files locally at any time, even when the computer is not running or the scope is not on the network, and pick them up later when I am at my computer.
So the client auto-connect is not a big deal for me personally, but it seems to have a problem under some boundary conditions which we have not figured out yet.
EDIT: My scope is also connected via a WiFi bridge. But I kept the bridge powered on while power-cycling the scope, so the network connection was present right at boot time. @eTobey, @electronics hobbyist: Are you using SMB with user credentials or anonymous? I have a username and password assigned since my server requires them. Maybe that plays a role in getting a successful auto-connect or failing to do so?