[Samba] Samba 3 to Samba 4

[Rowland Penny]

On 13/01/14 03:18, shemgp at aiias.edu wrote:
> Hello,
>
> I would like to connect a winbind samba 3 client to a samba 4 domain
> server.  I run net rpc info -U administrator to register to the domain.
> wbinfo -m displays the server. But when I run wbinfo -u, the users are not
> being displayed.  I don't understand why. Can anybody help me. Thanks.
>
> Here's my smb.conf for the samba 3 client:
>
> [global]
>     workgroup = AIIAS.SAMBA4
>     server string = %h server
>      wins server = 172.16.0.242
>     dns proxy = no
>     password server = 172.16.0.242
>     log file = /var/log/samba/log.%m
>     log level = 3
>     max log size = 1000
>     syslog = 3
>     panic action = /usr/share/samba/panic-action %d
>     security = domain
>     encrypt passwords = true
>     passdb backend = tdbsam
>     obey pam restrictions = yes
>     invalid users = root
>     passwd program = /usr/bin/passwd %u
>     passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
> *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
>     socket options = TCP_NODELAY
>          winbind uid = 15000-30000
>          winbind gid = 15000-30000
>          winbind enum users = yes
>          winbind enum groups = yes
>          winbind use default domain = true
>          template homedir = /home/%U
>          template shell = /bin/bash
>          winbind offline logon = true
>          winbind  cache time = 100
> [homes]
>     comment = Home Directories
>     browseable = no
>     writable = no
>     create mask = 0700
>     directory mask = 0700
>     valid users = %S
> [printers]
>     comment = All Printers
>     browseable = no
>     path = /var/spool/samba
>     printable = yes
>     public = no
>     writable = no
>     create mode = 0700
> [print$]
>     comment = Printer Drivers
>     path = /var/lib/samba/printers
>     browseable = yes
>     read only = yes
>     guest ok = no
>
> Thanks again.
>
> Windell Shem Pasamba
>
Hi, your problem is probably being caused by having a dot in your 
workgroup name, this, it would seem, is not allowed. Remove the dot, 
rerun provision on the server and try again.

Rowland