Questions[smbclient](server)

I am trying to set up a Samba server in Docker. I tried using dperson/samba image from docker hub at https://hub.docker.com/r/dperson/samba. I followed the instructions and tried to connect to it using smbclient to see if I could access the SMB terminal and download things from the shares. Although I can see a listing of the shares, I cannot open the SMB terminal. I get the message SMB1 disabled -- no working group available.

This is the command I'm using to start my Samba container:

-u "example1:badpass" \
-u "example2:badpass" \
-s "public;/share" \
-s "users;/srv;no;no;no;example1,example2" \
-s "example1 private share;/example1;no;no;no;example1" \
-s "example2 private share;/example2;no;no;no;example2"

This is the command I'm using to try to access the container:

smbclient -I <IP address of docker container> -L <ID of container> -U example1%badpass -m SMB3

my Windows Server 2016 Remote Desktop Servers SMB client, randomly stops working for 1 to 10 minutes, then restarts with no user intervention. The Windows SMBClient event log marks the problem with events 30805 and 30807 upon disconnection. Events 30806 and 30808 are fired when the service comes back on.

In the fault interval:

• I can PING my fileservers / NAS
• I cannot browse SMB shares using Windows Explorer (using \fileserver or \ip_address). I get a waiting cursor and a blank window.
• net view \fileserver (or net view \ip_address) given from a command line just waits with no result.

The problem is not related to a single RD server, as it shows on all of them at different times

Thanks in advance for any suggestion!

As we know, latest windows 10 upgrade has made samba client refuse to sue guest account. Some organization even make it impossible to disable this bug. This make it impossible to create a public samba share on Linux for win10 clients.

You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.

I have tried several solutions, like forcing client to use SMBv3 (not working), mapping * to an existing unix user (check_sam_security: Couldn't find user xxx in passdb.). I also searched the Internet, but didn't get anything for Linux.

I have a idea like this: Make smbd server always tell windows "login success", rather than "login failed, please use guest account". But I don't know how to configure smbd to do this.

If you know something about bypassing this win10 limit, please give me a tip. thanks)

I tired to mount a Windows SMB share in Linux using autofs, but I kept getting 'access denied'

I decided to test it using smbclient, but I am just getting 'session setup failed: NT_STATUS_CONNECTION_RESET'.

sudo smbclient //myfileserver/myshare$ -U windows_service_account -W MYDOMAIN

There shouldn't be a firewall and the errors aren't very helpful.

Any idea what to check next?

I have a Windows 2016 SMB share mounted on a Debian 10 box. I am using qemu-img to convert an image file the target of which I wish to store on the SMB mount. When I run the command I get this error:

error while converting qcow2: Failed to get "resize" lock

This suggests that either qemu-img is misinterpreting the lock on the mount or that there is something incorrect with the mount itself. I note that qemu-img does not seem to support stdout, which is extremely frustrating!

Are there any tunables I can use to bypass this error?

Thanks!