Hi all. I've been playing with this for a while. Recently noticed that on 3 of my Win 10 boxes, I can only access the samba shares using the ip address of the server. My main Win 10 is unaffected and can connect using netbios name or IP. I'm not sure if this is related to the 225 updates I did recently on the CentOS box or the updates for Windows. The fact that one box is fine has made things confusing. Anyhow I've worked through all the Windows fixes, resetting winsock etc. So now I'm starting on the CentOS with limited knowledge.
I've noticed that Testparm produces a slightly different output to the samb.conf that I see using WinSCP, is this normal or are there 2 smb.conf files?
Here's testparm results :-
[root@dvofps ~]# testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[datatest]"
Processing section "[Data]"
Processing section "[alldata]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
netbios name = CENTOS
map to guest = Bad User
security = USER
wins support = Yes
idmap config * : backend = tdb
cups options = raw
guest ok = Yes
guest only = Yes
[datatest]
path = /mnt/win
map archive = No
Here's smb.conf - via WinSCP :-
# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.
[global]
dns proxy = yes
netbios name = centos
cups options = raw
# server string = Samba Server
writeable = yes
guest ok = yes
workgroup = WORKGROUP
os level = 20
map to guest = bad user
security = user
public = yes
guest only = yes
wins support = true
[datatest]
guest ok = yes
map archive = no
writable = yes
browsable = yes
guest only = yes
path = /mnt/win
[Data]
guest ok = yes
map archive = no
delete readonly = yes
path = /mnt/win02
force user = root
valid users = nobody,@nobody,@wheel,@samba
create mode = 777
directory mode = 777
[alldata]
path = /mnt
For good measure, here's what I get using Webmin-
# See smb.conf.example for a more detailed config file or
# read the smb.conf manpage.
# Run 'testparm' to verify the config is correct after
# you modified it.
[global]
dns proxy = yes
netbios name = centos
cups options = raw
# server string = Samba Server
writeable = yes
guest ok = yes
workgroup = WORKGROUP
os level = 20
map to guest = bad user
security = user
public = yes
guest only = yes
wins support = true
[datatest]
guest ok = yes
map archive = no
writable = yes
browsable = yes
guest only = yes
path = /mnt/win
[Data]
guest ok = yes
map archive = no
delete readonly = yes
path = /mnt/win02
force user = root
valid users = nobody,@nobody,@wheel,@samba
create mode = 777
directory mode = 777
[alldata]
path = /mnt
Is it something to do with symbolic links?
Samba shares access by IP only
Re: Samba shares access by IP only (Solved)
put me in a home!
a week I've been playing with this and I knew it would be something simple. "start nmb" normal service has been resumed, can now access samba shares using netbios name and IP.
Still doesn't explain why one of the Win 10 boxes was working or why testparm shows different results. I've done testparm -s -v output results to a txt file. Lot of info but most of it means nothing to me
start nmb, doh
a week I've been playing with this and I knew it would be something simple. "start nmb" normal service has been resumed, can now access samba shares using netbios name and IP.
Still doesn't explain why one of the Win 10 boxes was working or why testparm shows different results. I've done testparm -s -v output results to a txt file. Lot of info but most of it means nothing to me
start nmb, doh