LinuxQuestions.org - [SOLVED] unable to mount samba share on Windows 11

- Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)

- - unable to mount samba share on Windows 11 (https://www.linuxquestions.org/questions/linux-server-73/unable-to-mount-samba-share-on-windows-11-a-4175736026/)

unable to mount samba share on Windows 11

I recently upgraded to Windows 11. This is the first time since doing so I have tried to map a drive which is a samba share on a Linux host. The samba share is:

Code:

# smbclient -L localhost



Anonymous login successful



        Sharename      Type      Comment

        ---------      ----      -------

        homes          Disk      Home Directory on quadmon

The smb.conf definition for homes is:

Code:

[homes]

  comment = Home Directory on quadmon

  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.". 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.

There are no messages on the Linux /var/log files related to this problem.

Any idea what is going wrong here? Do I need something in PAM? Different settings in /etc/samba/smb.conf?

Global settings in smb.conf are:

Code:

[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

It isn't a Windows problem. I am running debian 12 samba 4.17.12 and I see a similar bug. I would expect as in the past that [homes] should automatically create a home share for all regular users regardless but if the homes share is browseable, with anonymous login you see only [homes], if you login as your regular user you see both homes and the user's share. With anonymous login I also see a nobody share which is strange. I guess I should go look at the release notes for that version and see if there is anything relevant. You should be able to manually access the user's actual home from Windows i.e

\\linux_hostname_or_IP_address\username

Windows does not allow anonymous logins anymore so you need to create a samba password for your user if it does not exist.

Well, something is very wrong. Your suggestion of \\host\username did not work. Same results. I removed the [homes] share and created one with my username and path to /home/mfoley. That didn't work either. I changed the samba pw with 'smbpasswd mfoley'. Nada. Still no messages in /var/log/samba.client. In fact none of my shares are working. All give the message "Windows cannot access ...".

Interestingly, on another LAN, with the Linux host also being part of a Windows Active Directory domain, I have no problem mapping drives. This problem child is not a domain members, so authentication is via normal means (smbpasswd). Surely there are people out there with a Slackware 15.0 samba server and Windows 11 clients!

OK, I'm an idiot! Firewall was blocking connection. After I enabled ports 139 and 445 on Linux, everything worked. Duh!