JanDeAlleman:
So, it seems my server is indeed using a deprecated protocol! (ubuntu’s default, you would maybe like to know). Let’s try to force a more modern one:
[global]
workgroup = WORKGROUP
server string = %h server
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
client min protocol = SMB2
client max protocol = SMB3
[server]
comment = media server
browsable = yes
path = /home/jan/hardeschijf/
guest ok = yes
read only = no
I just examined your change to the Ubuntu samba server. BTW, which version of Ubuntu are you using?
Anyway, I note that you specified ‘client min protocol = SMB2’ and ‘client max protocol = SMB3’, but for server directives this should be
min protocol = SMB2
max protocol = SMB3
These directives a synonyms for ‘server min protocol’ and ‘server max protocol’ respectively.
Reference
https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
With a share allowing guest access, it should be possible to mount on the fly using…
sudo mount -t cifs -o nosuid,nodev,relatime,gid=100,uid=1000,guest,file_mode=0770,dir_mode=0770 //192.168.178.72/server/Server/Music /media/music
deano_ferrari:
I just examined your change to the Ubuntu samba server. BTW, which version of Ubuntu are you using?
Anyway, I note that you specified ‘client min protocol = SMB2’ and ‘client max protocol = SMB3’, but for server directives this should be
min protocol = SMB2
max protocol = SMB3
These directives a synonyms for ‘server min protocol’ and ‘server max protocol’ respectively.
Of course it shouldn’t! ****, that’s quite obvious.
And you know what? It solved my all of my problems! Thanks for the help all, you have been very patient.
Well done. Glad to have been of guidance.
hcvv
November 2, 2020, 12:40pm
44
That is fine. Often it is just the discussion that helps.