unable to mount samba share on Windows 11
by mfoley from LinuxQuestions.org on (#6M2S0)
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 quadmonThe smb.conf definition for homes is:
Code:[homes]
comment = Home Directory on quadmon
browseable = yes
writable = yes
create mask = 0660The 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
Code:# smbclient -L localhost
Anonymous login successful
Sharename Type Comment
--------- ---- -------
homes Disk Home Directory on quadmonThe smb.conf definition for homes is:
Code:[homes]
comment = Home Directory on quadmon
browseable = yes
writable = yes
create mask = 0660The 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