[Samba] Unable to mount samba share on Windows 11

[Rowland Penny]

On Mon, 15 Apr 2024 14:33:10 -0400
Mark Foley via samba <samba at lists.samba.org> wrote:

> I am using Samba 4.18.9, not in a Windows domain environment.  I
> recently upgraded a Windows computer on the LAN to Windows 11.  This
> is the first time since either the Samba or Windows upgrade I have
> tried to map a drive which is a Linux Samba share to a Windows 11
> computer.  The samba share is (was):
> 
> Code:
> 
> # smbclient -L localhost
> 
> Anonymous login successful
> 
>         Sharename       Type      Comment
>         ---------       ----      -------
>         homes           Disk      Home Directory on quadmon
> 
> The smb.conf is:
> 
> [global]
> workgroup = WORKGROUP
> server string = QUADMON Samba Server
> security = user
> unix password sync = yes
> kernel oplocks = false
> log file = /var/log/samba.clients
>    max log size = 50
>    socket options = TCP_NODELAY 
> 
> local master = no
> domain master = no
> preferred master = yes
>    dns proxy = no 
> 
> ;[homes]
> ;   comment = Home Directory on quadmon
> ;   browseable = yes
> ;   writable = yes
> ;   create mask = 0660

Try it like this:

[homes]
  comment = Home Directories
  browseable = no
  read only = no
  create mask = 0700
  directory mask = 0700
  valid users = %S

Then (after reloading the config or restarting smbd) see if you can
connect to the 'mfoley' share.

> 
> [mfoley]
>    comment = Home Directory on quadmon
>    path = /home/mfoley
>    valid users = mfoley
>    browseable = yes
>    writable = yes
>    create mask = 0660
> 
> The Windows host can ping and ssh to the Linux by hostname quadmon.
> When trying to map to \\quadmon\homes on Windows I get, "Windows
> cannot access \\quadmon\homes.". 

You are supposed to connect to the users share and not to 'homes'

> I've also tried using the IP. When
> I click on the browse button in the 'Map Network Drive' dialog it
> does not see quadmon.  I do have wsdd.py running on Linux which is
> supposed to facilitate discovery by Windows computers. 

Have you checked that Network Discovery is running on the Windows
computer ?

Rowland