I just upgraded to v6.12.13 (from v5.0.5) and now can't access the "tower" shares or webgui by name on two computers, but two other computers are unaffected. On the two computers that cant use the name, using the IP address works fine. As far as I'm aware there shouldn't be any network or sign in credentials. All computers are Win10, and a mix of hardwired and wifi. Not sure what other relevant information is required. Thanks

I assume windows...
Can you access the share by going to \\192.168.x.x <the ip address of the unraid tower machine?
what is the output of terminal command:
testparm

this is the running samba server. as their has been quite a bit done to OS and how unraid does samba in upgrades to the smb server...

The name address issues may also be a windows side client connect issues. You may need to go into control panel > credentials manger
and remove and saved logins for tower or the unraid IP address.

Please review this forum post.
 

 

Edited October 23, 20241 yr by bmartino1

2 hours ago, bmartino1 said:

I assume windows...

All computers are Win10

 

 

2 hours ago, bmartino1 said:

Can you access the share by going to \\192.168.x.x <the ip address of the unraid tower machine?

On the two computers that cant use the name, using the IP address works fine.

 

 

2 hours ago, bmartino1 said:

what is the output of terminal command:
testparm

Please see attached text file.

 

 

2 hours ago, bmartino1 said:

You may need to go into control panel > credentials manger
and remove and saved logins for tower or the unraid IP address.

There are no credentials relating to "tower", unraid, or the IP address in credentials manager.

testparm output.txt

Thank you for this information. It looks like you may have made a few smb extra options.

I would have you review this:

As you do have a conflict in testparm in how a windows samba session may break and why name resolution from default windows won't connect.

I usually define this as the netbios dns name issues. as Unraid uses a prepackaged binary for smb samba and nmbd netbios.

the conflict in the testparm are some unraid default options.

 

your smb config per testparm:

 disable netbios = Yes
 disable spoolss = Yes
 host msdfs = No
 ntlm auth = ntlmv1-permitted
 server min protocol = SMB2
 

there is a conflict of interest here that is preventing samba form sharing smb access via its host name and how the session is to be handled.

here is an example fix you could run, as this is what is working for me.

step 1
adjust unraid default settings.

*The array may need to be off to edit and apply some settings. With recent unraid betas, some services may require a reboot and a stop start command to function...

Settings > SMB:


In windows 10 you want wsd as this is the service that is generating the name to ip resolution by going to network tower to access samba shares...

You want to ensure that netbios and wsd are enabled here. That you are considered the local master as unraid will then be used for name calls and checks.

step 2: (optional if that above didn't fix the issue):

Update smb with a working smb conf... (following simlar steps in the forum posted above)
this requires the plugin user scripts to run a script.

#!/bin/bash

sleep 10
/etc/rc.d/rc.samba stop
rm /etc/samba/smb.conf
cp /boot/config/smb-override.conf /etc/samba/smb.conf
/etc/rc.d/rc.samba start

sleep 1
/etc/rc.d/rc.nfsd stop
/etc/rc.d/rc.rpc stop
sleep 1
/etc/rc.d/rc.rpc start
/etc/rc.d/rc.nfsd start

and use a smb overide conf as example:

 

root@BMM-Unraid:~# cat /etc/samba/smb.conf 
[global]
# Configurable identification disabled as we need to make other edits.
# include = /etc/samba/smb-names.conf

# Generated names
netbios name = tower
server string = Unraid NAS Server
workgroup = WORKGROUP
security = USER
map to guest = Bad User
guest account = nobody
null passwords = Yes

# Network settings
wins support = yes
name resolve order = lmhosts wins bcast host
multicast dns register = Yes
disable netbios = No
bind interfaces only = yes
interfaces = 192.168.2.23/24 127.0.0.1


# Master browser settings
server role = standalone server
local master = yes
domain master = yes
preferred master = yes
os level = 200
nmbd bind explicit broadcast = no

# Logging
logging = syslog@0
# log level = 3

# File and directory permissions
create mask = 0777
directory mask = 0777
acl allow execute always = Yes

# Printer settings
show add printer wizard = No
disable spoolss = Yes
load printers = No
printing = bsd
printcap name = /dev/null

# Performance settings
aio read size = 0
aio write size = 0
use sendfile = Yes
server multi channel support = yes
max open files = 40960

# Miscellaneous settings
invalid users = root
fruit:encoding = native
fruit:zero_file_id = false
fruit:nfs_aces = No
rpc_server:mdssvc = disabled
rpc_daemon:mdssd = disabled
fruit:time machine max size = 0 # Unlimited
fruit:time machine = True
fruit:resource = stream
fruit:metadata = stream
vfs objects = catia fruit streams_xattr
server role = standalone server
dns proxy = no
winbind request timeout = 5
server signing = auto
strict locking = no
#ntlm auth = ntlmv1-permitted
ntlm auth = mschapv2-and-ntlmv2-only
#server min protocol = SMB2

# Control Client and Access
# client min protocol = SMB2
# client max protocol = SMB3

# Other File Settings
follow symlinks = yes
unix extensions = No
wide links = Yes
case sensitive = True
default case = lower
preserve case = yes
short preserve case = yes
guest ok = Yes
map hidden = Yes
map system = Yes
smbd max xattr size = 2097152
read raw = yes
write raw = yes

# Hook for user-defined Samba config
# include = /boot/config/smb-extra.conf
# Disabled as using this Override Config...

# Other addins from other plugins and share via WebUI
# Hook for unassigned devices shares
include = /etc/samba/smb-unassigned.conf

# Auto-configured shares
include = /etc/samba/smb-shares.conf

This is what I would recommend fixing samba on unarid for your use case.

If that doesn't work, then disable the user script, reboot unraid to undo smb changes and look at window side settings as certain updates, gpo settings, registry settings may need to be applied...

as example windows 10 enterprise has certain smb options disabled by default. Attached is a registry I run to enable smb access on windows 10 enterprise.
 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"EnablePlainTextPassword"=dword:00000000
"EnableSecuritySignature"=dword:00000001
"ServiceDllUnloadOnStop"=dword:00000001
"AllowInsecureGuestAuth"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"LimitBlankPasswordUse"=dword:00000001
"NoLmHash"=dword:00000001
"everyoneincludesanonymous"=dword:00000001
"restrictanonymous"=dword:00000000
"restrictanonymoussam"=dword:00000001

Which re-enbales the guest user account for samba access
all which are explained more in the first form post later in that post...

 

enterprise-fix.reg

Edited October 24, 20241 yr by bmartino1

please also see:

 

Your first solution worked. Setting NetBIOS to enabled fixed the issue. Thanks for your help!