[SOLVED] Update to Samba 4 completely broke functionality of Samba

Question

I have a computer running Arch 64bit, from which I share media files to my girlfriend's Windows 7 laptop, and to my own Windows 8 tablet.
Until an hour or so, I was running Samba 3.6.13 which happily worked most of the time (with occasional breaks that were easily quelled). I upgraded to Samba 4 to realize (much to my horror, just before we were going to watch a movie) that the configuration is no longer valid and whenever someone tries to connect to the server... it crashes.
I tried to delete the configuration file (leaving only the shares, along with the example configuration from the Samba4 wiki), but the result is the same. I have no need for AD DC, or so. I just want a working share that Windows can read without a hassle, so we can watch movies and so in the living room.
Last time I tried to start it using systemctl start smbd.service it failed and the error log implied that it fails to fetch the printers list (I have no printers at home...)
Is there any advice on the situation? Here is my smb.conf file, although it's pretty dull right now.
[global]
workgroup = WORKGROUP
security = ADS
realm = Home
encrypt passwords = yes
idmap config *:backend = tdb
idmap config *:range = 70001-80000
idmap config SHORTDOMAINNAME:backend = ad
idmap config SHORTDOMAINNAME:schema_mode = rfc2307
idmap config SHORTDOMAINNAME:range = 500-40000
winbind nss info = rfc2307
winbind trusted domains only = no
winbind use default domain = yes
winbind enum users = yes
winbind enum groups = yes
[Videos]
path = /home/****/Videos
comment = Videos
valid users = nobody
read only = yes
available = yes
browseable = yes
writable = no
guest ok = yes
printable = no
locking = no
strict locking = no
[Music]
path =/home/****/Music
comment = Music
valid users = nobody
read only = yes
available = yes
browseable = yes
writable = no
guest ok = yes
printable = no
locking = no
strict locking = no
Last edited by Asaf K. (2013-04-16 09:33:18)

Answer 1

Beelzebud wrote:For an upgrade this big, there should be some documentation ready before it happens...
Exactly, the wiki has nothing about basic shares except for:
[test]
path = /data/test
comment = Test Share
read only = no
but using that template in my virtual machine does nothing!
Inxsible wrote:
t0m5k1 wrote:EDIT:
After reading their wiki I seriously think Arch Dev's should keep Samba3 in the repo's alongside Samba4  I say this because it appears Samba4 is more for those who require AD/DC functionality for a more enterprise scenario.
Are you volunteering yourself to maintain that package? Have you considered that it might break other dependency chains if its in the same repo?
Point is, its easy to say "you need to do this" -- its quite another to actually do it
Where do I say "you need to do this"?? I do not as I am simply sharing my opinion on what seems to be a bit of a major thing! Sorry if I offended you that was not my intention at all
Perhaps you thought I meant Arch linux wiki when I said "their wiki" as I was actually referring to Samba!
However I do consider it is possible that keeping Samba 3 in the repo's could have knock on effect but is it not obvious that basic file sharing has been broken by this upgrade!
And no unfortunately I do not have the required skills to volunteer to maintain this neither do I have the time as well.
Last edited by t0m5k1 (2013-04-12 18:36:15)