[Bug 990945] Re: samba-common doesn't read workgroup from smb.conf

[Abhijeet Anand]

G'day again,

I seem to have found a solution for my problem; I think it is more a
workaround than a solution IMHO. All I had to do was to reinstall samba-
common a couple of times and make certain changes to /etc/samba/smb.conf
in between re-installation attempts.

Steps I followed:
1. Changed:
    realm = DOMAINNAME -> realm = DOMAINNAME.SOMETHING
This is weird because, installation script itself populates this variable with the value from workgroup and then complains
@jelmer: I guess you need to look into this.

2. sudo aptitude reinstall samba-common
Everything goes fine, however, now the installation will complain about absence of two shares, viz, NETLOGON and SYSVOL because, allegedly, I was trying to install samba as a Domain Controller; which I was not. Despite removing the line "server role = dc", it didn't help as the install script would create it back and then whinge. I searched on how to NOT create a Domain Controller, however, the suggestions from samba.org didn't help at all. The suggestions were to have the following two config parameters:
"passdb backend = guest" and "security = share"

Anyway, since that didn't help, I simply uncommented the lines for
NETLOGON and created the SYSVOL share, following the default
recommendation. The recommendation was to look at some default config
file for domain controller.

Finally, after all this, the installation succeeded.

@jelmer: I originally wanted to install Samba4 as a simple file-server,
however, I could not understand why the install script would constantly
try to install it as a DC. Could you please shed some light on this and
how could I only install it as a simple file-server, like we could with
samba3?

Thanks again mate.

Cheers,
Abhi

PS: While I was trying to investigate how to change workgroup name fetched by samba-common, I stumbled upon some interesting and amusing debconf scripts. One in particular had an amusing comment.
samba-common.postinst: # Oh my GOD, this is ugly.  Why would anyone put these
samba-common.postinst: # characters in a workgroup name?  Why, Lord, why???

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/990945

Title:
  samba-common doesn't read workgroup from smb.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/990945/+subscriptions