Skip to main content

Thread: 12.04 Samba Behaviour Changes


i have ubuntu file server running @ home, started on 10.04, went 11.10 , had no problems. yesterday upgraded 12.04 , have run issues samba.

have 2 shares show odd behaviour:

[incoming]
path = /raid/incoming
browsable = no
valid users = @users
write list = @users

[work]
path = /raid/work
guest ok = yes
write list = @users

permissions same on each directory:

stew@chinken:/raid$ls -alh
drwxrwxr-x 44 stew users 4.0k aug 22 22:53 work
drwxrwxr-x 75 stew users 4.0k aug 22 23:58 incoming

have user 'stew' belongs @users group can write work not incoming - gets permission error. worked fine, write both shares. global settings follows:

code:
server role: role_standalone [global]         server string = %h         map guest = bad user         obey pam restrictions = yes         pam password change = yes         passwd program = /usr/bin/passwd %u         passwd chat = *enter\snew\s*\spassword:* %n\n *retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .         unix password sync = yes         syslog = 0         log file = /var/log/samba/log.%m         max log size = 1000         dns proxy = no         usershare allow guests = yes         panic action = /usr/share/samba/panic-action %d         idmap config * : backend = tdb         create mask = 0775         directory mask = 0775
i note windows xp machines, user/pass required when bringing share list browsing network. typing guest/guest user/pass seems work ok, changed behaviour. before, users see shares , required enter user/pass shares 'valid users' or 'write users' settings. windows7 still seems work expected in regard although when i'm prompted password wont accept valid smbuser user/passes. weird thing on windows7 machine 'work' folder reads/writes fine without having enter password (using ntlm i'm guessing user/pass on host same smbuser) not 'incoming'.

ideas what's changed?

in advance

managed solve reading samba change notes.

http://www.samba.org/samba/history/samba-3.6.0.html

samba 3.6 has adopted number of improved security defaults will
impact on existing users of samba.

client ntlmv2 auth = yes
client use spnego principal = no
send spnego principal = no

impact of 'client ntlmv2 auth = yes' default not
use ntlm authentication client. applies samba client
tools such smbclient , winbind, not change separately
released in-kernel cifs client. re-enable poorer ntlm encryption
set '--option=clientusentlmv2auth=no' on smbclient command line, or
set 'client ntlmv2 auth = no' in smb.conf
adding client ntlmv2 auth = no config has fixed issue , functions old version (albeit less security apparently?)


Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [SOLVED] 12.04 Samba Behaviour Changes


Ubuntu

Comments

Popular posts from this blog

Thread: Can not create raid array: mdadm: no raid-devices specified.

Thread: HOW TO: Package and theme GTK+ / Gtkmm apps in Linux for Windows

Thread: Twinview issues