Sponsored Content
Full Discussion: Samba configuration (?)
Operating Systems Linux Samba configuration (?) Post 302300823 by woofie on Wednesday 25th of March 2009 06:50:11 AM
Old 03-25-2009
Samba configuration (?)

I'm trying to setup OpenSUSE 11.0 as a PDC on a small test network at home.

So far it's sort of going good I guess. I'm setup SUSE and think I have configure Samba correct, well sort of. Not really what I was after. I wanted SUSE to act as a PDC and have a Windows XP machine be able to join the domain (with SUSE as the PDC).

I am aware that the samba users also have to be system users (that's what I read) on the Linux box. Have turned LDSP Server - ON (Doesn't make a difference though). Turned 'Samba Server' - ON. Below is the smb.conf file (this is just a test/trial run I'm trying here).

Code:
[global]
	workgroup = domain
	printing = cups
	printcap name = cups
	printcap cache time = 750
	cups options = raw
	map to guest = Bad User
	logon path = \\%L\profiles\.msprofile
	logon home = \\%L\%U\.9xprofile
	logon drive = P:
	usershare allow guests = No
	add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
	domain logons = Yes
	domain master = Yes
	security = user
	netbios name = test
	local master = Yes
	os level = 65
	preferred master = Yes

[homes]
	comment = Home Directories
	valid users = %S, %D%w%S
	browseable = Yes
	read only = No
	inherit acls = Yes
[profiles]
	comment = Network Profiles Service
	path = %H
	read only = No
	store dos attributes = Yes
	create mask = 0600
	directory mask = 0700
[users]
	comment = All users
	path = /home
	read only = No
	inherit acls = Yes
	veto files = /aquota.user/groups/shares/
[groups]
	comment = All groups
	path = /home/groups
	read only = No
	inherit acls = Yes
[printers]
	comment = All Printers
	path = /var/tmp
	printable = Yes
	create mask = 0600
	browseable = No
[print$]
	comment = Printer Drivers
	path = /var/lib/samba/drivers
	write list = @ntadmin root
	force group = ntadmin
	create mask = 0664
	directory mask = 0775

[netlogon]
	comment = Network Logon Service
	path = /var/lib/samba/netlogon
	write list = root

I played around with a few other things but they are back to default settings of turned off now as that didn't seem to make any difference.

From my Windows XP machine (client/workstation) I can't join a domain, but I can join the SUSE box as a WORKGROUP. I can view the shared folders etc which is all good and well.

But I really wanted to setup as a PDC. I've searched google and can't really find any specific documents for setting up Linux (specifically OpenSUSE) for a PDC. I was wondering if anyone can lead/push me in the right direction to some good reading which might be able to help me setup a PDC and not create a workgroup.

Thanks in advanced.

EDIT: When setting up Samba Server I did select Primary PDC in the settings.

Last edited by woofie; 03-25-2009 at 07:59 AM.. Reason: updating info
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Samba 3.0.24 Configuration Problem

Dear all, I have set the security level to user. My samba is running on Unixware 7.1.4. I get the following screen error when trying to login from windows clients.... (0 Replies)
Discussion started by: ndege
0 Replies

2. Red Hat

krb5.h not usable and not found during samba configuration error

Hi folks, I am using RH linux server 8.0 and have downloaded latest samba package for it. While configuring samba with --with-krb5 option while making this server join a windows AD domain, it gives the following error. active directory cannot be supported... (1 Reply)
Discussion started by: dextergenious
1 Replies

3. Red Hat

Re:Configuration of samba services

Hi, Can any one give me the simple way of configuring samba services on the linux server & similarly what are the thing that have to be done on the client side. Thanks & Regards Venky (0 Replies)
Discussion started by: venky_vemuri
0 Replies

4. UNIX for Dummies Questions & Answers

samba server configuration on linux.

Today I have configured samba server on my linux machine .I thought it would be better if i share it here and get feedback from an experienced users. This configuration is based on Redhat release 5. # lsb_release -a LSB Version: ... (0 Replies)
Discussion started by: pinga123
0 Replies

5. Solaris

solaris samba configuration without wins service from authentication window server/Active directory

Hi All, We are using solaris samba server for our company project to provide access to code to our development team.Recently our ICT has disabled wins service on Active directory due which user are not able to connect to samba share and they are getting error "No logon server available" as samba... (2 Replies)
Discussion started by: sahil_shine
2 Replies

6. Solaris

samba issue: one samba share without password prompting and the others with.

Hi All, I've been trying to configure samba on Solaris 10 to allow me to have one share that is open and writable to all users and have the rest of my shares password protected by a generic account. If I set my security to user, my secured shares work just fine and prompt accordingly, but when... (0 Replies)
Discussion started by: ideal2545
0 Replies

7. UNIX and Linux Applications

Samba configuration

Good morning. I installed Samba on my server but I need some help in consfiguratin: 1. Access only for users from my network 2. Create catalog for all users, users not login - only read, users log in - all(read, create, write) 3. Create catalog for users group. If we create some group users... (2 Replies)
Discussion started by: Budrys
2 Replies

8. UNIX for Dummies Questions & Answers

Ubuntu Server 14.04 LTS - domain controller configuration (SAMBA)

Hello! Never configured a Linux server from a scratch. Reviewed the official documentation and dozens of different "how to", but now one of them helped me to solve the issue. The need: My final goal is to install a small network (later with around 10 stations) where I can controle the... (0 Replies)
Discussion started by: AQwert
0 Replies

9. IP Networking

Samba ha configuration require

I HAVE TO DESIGN TWO NODE SAMBA HA SERVER, TO DO THIS I NEED YOUR HELP, HOW CAN CONFIGURE SUCH SCENARIO? REGARDS PRAMOD INGOLE (4 Replies)
Discussion started by: pramod_ingole
4 Replies
WINBINDD(8)                                                 System Administration tools                                                WINBINDD(8)

NAME
winbindd - Name Service Switch daemon for resolving names from NT servers SYNOPSIS
winbindd [-D] [-F] [-S] [-i] [-Y] [-d <debug level>] [-s <smb config file>] [-n] DESCRIPTION
This program is part of the samba(7) suite. winbindd is a daemon that provides a number of services to the Name Service Switch capability found in most modern C libraries, to arbitrary applications via PAM and ntlm_auth and to Samba itself. Even if winbind is not used for nsswitch, it still provides a service to smbd, ntlm_auth and the pam_winbind.so PAM module, by managing connections to domain controllers. In this configuraiton the idmap uid and idmap gid parameters are not required. (This is known as `netlogon proxy only mode'.) The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS. The exact behaviour can be configured through the /etc/nsswitch.conf file. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system. The service provided by winbindd is called `winbind' and can be used to resolve user and group information from a Windows NT server. The service can also provide authentication services via an associated PAM module. The pam_winbind module supports the auth, account and password module-types. It should be noted that the account module simply performs a getpwnam() to verify that the system can obtain a uid for the user, as the domain controller has already performed access control. If the libnss_winbind library has been correctly installed, or an alternate source of names configured, this should always succeed. The following nsswitch databases are implemented by the winbindd service: hosts This feature is only available on IRIX. User information traditionally stored in the hosts(5) file and used by gethostbyname(3) functions. Names are resolved through the WINS server or by broadcast. passwd User information traditionally stored in the passwd(5) file and used by getpwent(3) functions. group Group information traditionally stored in the group(5) file and used by getgrent(3) functions. For example, the following simple configuration in the /etc/nsswitch.conf file can be used to initially resolve user and group information from /etc/passwd and /etc/group and then from the Windows NT server. passwd: files winbind group: files winbind ## only available on IRIX: use winbind to resolve hosts: # hosts: files dns winbind ## All other NSS enabled systems should use libnss_wins.so like this: hosts: files dns wins The following simple configuration in the /etc/nsswitch.conf file can be used to initially resolve hostnames from /etc/hosts and then from the WINS server. hosts: files wins OPTIONS
-D If specified, this parameter causes the server to operate as a daemon. That is, it detaches itself and runs in the background on the appropriate port. This switch is assumed if winbindd is executed on the command line of a shell. -F If specified, this parameter causes the main winbindd process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running winbindd under process supervisors such as supervise and svscan from Daniel J. Bernstein's daemontools package, or the AIX process monitor. -S If specified, this parameter causes winbindd to log to standard output rather than a file. -d|--debuglevel=level level is an integer from 0 to 10. The default value if this parameter is not specified is 0. The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running - it generates a small amount of information about operations carried out. Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic. Note that specifying this parameter here will override the smb.conf.5.html# parameter in the smb.conf file. -V|--version Prints the program version number. -s|--configfile <configuration file> The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See smb.conf for more information. The default configuration file name is determined at compile time. -l|--log-basename=logdirectory Base directory name for log/debug files. The extension ".progname" will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client. -h|--help Print a summary of command line options. -i Tells winbindd to not become a daemon and detach from the current terminal. This option is used by developers when interactive debugging of winbindd is required. winbindd also logs to standard output, as if the -S parameter had been given. -n Disable caching. This means winbindd will always have to wait for a response from the domain controller before it can respond to a client and this thus makes things slower. The results will however be more accurate, since results from the cache might not be up-to-date. This might also temporarily hang winbindd if the DC doesn't respond. -Y Single daemon mode. This means winbindd will run as a single process (the mode of operation in Samba 2.2). Winbindd's default behavior is to launch a child process that is responsible for updating expired cache entries. NAME AND ID RESOLUTION
Users and groups on a Windows NT server are assigned a security id (SID) which is globally unique when the user or group is created. To convert the Windows NT user or group into a unix user or group, a mapping between SIDs and unix user and group ids is required. This is one of the jobs that winbindd performs. As winbindd users and groups are resolved from a server, user and group ids are allocated from a specified range. This is done on a first come, first served basis, although all existing users and groups will be mapped as soon as a client performs a user or group enumeration command. The allocated unix ids are stored in a database and will be remembered. WARNING: The SID to unix id database is the only location where the user and group mappings are stored by winbindd. If this store is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids. CONFIGURATION
Configuration of the winbindd daemon is done through configuration parameters in the smb.conf(5) file. All parameters should be specified in the [global] section of smb.conf. o winbind separator o idmap uid o idmap gid o idmap backend o winbind cache time o winbind enum users o winbind enum groups o template homedir o template shell o winbind use default domain o winbind: rpc only Setting this parameter forces winbindd to use RPC instead of LDAP to retrieve information from Domain Controllers. EXAMPLE SETUP
To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup. This was tested on an early Red Hat Linux box. In /etc/nsswitch.conf put the following: passwd: files winbind group: files winbind In /etc/pam.d/* replace the auth lines with something like this: auth required /lib/security/pam_securetty.so auth required /lib/security/pam_nologin.so auth sufficient /lib/security/pam_winbind.so auth required /lib/security/pam_unix.so use_first_pass shadow nullok Note The PAM module pam_unix has recently replaced the module pam_pwdb. Some Linux systems use the module pam_unix2 in place of pam_unix. Note in particular the use of the sufficient keyword and the use_first_pass keyword. Now replace the account lines with this: account required /lib/security/pam_winbind.so The next step is to join the domain. To do that use the net program like this: net join -S PDC -U Administrator The username after the -U can be any Domain user that has administrator privileges on the machine. Substitute the name or IP of your PDC for "PDC". Next copy libnss_winbind.so to /lib and pam_winbind.so to /lib/security. A symbolic link needs to be made from /lib/libnss_winbind.so to /lib/libnss_winbind.so.2. If you are using an older version of glibc then the target of the link should be /lib/libnss_winbind.so.1. Finally, setup a smb.conf(5) containing directives like the following: [global] winbind separator = + winbind cache time = 10 template shell = /bin/bash template homedir = /home/%D/%U idmap uid = 10000-20000 idmap gid = 10000-20000 workgroup = DOMAIN security = domain password server = * Now start winbindd and you should find that your user and group database is expanded to include your NT users and groups, and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username. You may wish to use the commands getent passwd and getent group to confirm the correct operation of winbindd. NOTES
The following notes are useful when configuring and running winbindd: nmbd(8) must be running on the local machine for winbindd to work. PAM is really easy to misconfigure. Make sure you know what you are doing when modifying PAM configuration files. It is possible to set up PAM such that you can no longer log into your system. If more than one UNIX machine is running winbindd, then in general the user and groups ids allocated by winbindd will not be the same. The user and group ids will only be valid for the local machine, unless a shared idmap backend is configured. If the the Windows NT SID to UNIX user and group id mapping file is damaged or destroyed then the mappings will be lost. SIGNALS
The following signals can be used to manipulate the winbindd daemon. SIGHUP Reload the smb.conf(5) file and apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted by winbindd is also reloaded. SIGUSR2 The SIGUSR2 signal will cause winbindd to write status information to the winbind log file. Log files are stored in the filename specified by the log file parameter. FILES
/etc/nsswitch.conf(5) Name service switch configuration file. /tmp/.winbindd/pipe The UNIX pipe over which clients communicate with the winbindd program. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the /tmp/.winbindd directory and /tmp/.winbindd/pipe file are owned by root. $LOCKDIR/winbindd_privileged/pipe The UNIX pipe over which 'privileged' clients communicate with the winbindd program. For security reasons, access to some winbindd functions - like those needed by the ntlm_auth utility - is restricted. By default, only users in the 'root' group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privileged to allow programs like 'squid' to use ntlm_auth. Note that the winbind client will only attempt to connect to the winbindd daemon if both the $LOCKDIR/winbindd_privileged directory and $LOCKDIR/winbindd_privileged/pipe file are owned by root. /lib/libnss_winbind.so.X Implementation of name service switch library. $LOCKDIR/winbindd_idmap.tdb Storage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially compiled using the --with-lockdir option. This directory is by default /usr/local/samba/var/locks . $LOCKDIR/winbindd_cache.tdb Storage for cached user and group information. VERSION
This man page is correct for version 3 of the Samba suite. SEE ALSO
nsswitch.conf(5), samba(7), wbinfo(1), ntlm_auth(8), smb.conf(5), pam_winbind(8) AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. wbinfo and winbindd were written by Tim Potter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. Samba 3.5 06/18/2010 WINBINDD(8)
All times are GMT -4. The time now is 10:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy