Samba Web Help http://us1.samba.org/samba/ The Official Samba 3.2.x HOWTO and Reference Guide http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/ Practical Exercises in Successful Samba Deploymen http://us1.samba.org/samba/docs/man/Samba-Guide/ Other https://calomel.org/samba.html Local Help file:///usr/share/doc/packages/samba/ file:///usr/share/doc/packages/samba/Samba3-HOWTO.pdf file:///usr/share/doc/packages/samba/examples/smb.conf.SUSE Configuration Files located in /etc/samba or /usr/local/samba/lib/ dhcp.conf, lmhosts, secrets.tdb, smb.conf, smb.conf.rpmnew, smbfstab, smbpasswd, smbusers /etc/samba/smb.conf is the main Samba configuration file. TDB Database File Information dirs and files located in /var/lib/samba account_policy.tdb,connections.tdb,group_mapping.tdb, netlogon,ntprinters.tdb, profiles, share_info.tdb, wins.dat, brlock.tdb, drivers, locking.tdb, ntdrivers.tdb, perfmon, registry.tdb, unexpected.tdb, wins.tdb, browse.dat, gencache.tdb, messages.tdb, ntforms.tdb, printing, sessionid.tdb, usershares Samba essentially consists of two or three daemons. A daemon is a UNIX application that runs in the background and provides services. An example of a service is the Apache Web server for which the daemon is called httpd. In the case of Samba there are three daemons, two of which are needed as a minimum. The Samba server is made up of the following daemons: nmbd: This daemon handles all name registration and resolution requests. It is the primary vehicle involved in network browsing. It handles all UDP-based protocols. The nmbd daemon should be the first command started as part of the Samba startup process. smbd: This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also manages local authentication. It should be started immediately following the startup of nmbd. winbindd: This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when Samba has trust relationships with another domain. The winbindd daemon will check the smb.conf file for the presence of the idmap uid and idmap gid parameters. If they are not found, winbindd bails out and refuses to start. The Samba daemons[smb,nmb] are located in /usr/bin Starting samba root# /usr/bin/nmbd stop root# /usr/bin/smbd stop Starting Samba root# /usr/bin/nmbd start root# /usr/bin/smbd start Starting Samba for Novell SUSE Linux Novell SUSE Linux products automatically install all essential Samba components in a default installation. Configure your smb.conf file, then execute the following to start Samba: root# rcnmb start root# rcsmb start root# rcwinbind start Alternative: Starting smbd as a Daemon To start the server as a daemon, you should create a script something like this one, perhaps calling it startsmb. #!/bin/sh /usr/local/samba/sbin/smbd -D /usr/local/samba/sbin/winbindd -B /usr/local/samba/sbin/nmbd -D Make it executable with chmod +x startsmb. You can then run startsmb by hand or execute it from /etc/rc.local. To kill it, send a kill signal to the processes nmbd and smbd. use the command 'testparm' after any changes you made A minimal smb.conf [global] workgroup = WKG netbios name = MYNAME [share1] path = /tmp [share2] path = /my_shared_folder comment = Some random files My samba.conf file setup: # Global parameters [global] workgroup = Federation netbios name = Enterprise server string = Samba Server %v map to guest = Bad User log file = /var/log/samba/log.%m max log size = 5 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No security = user add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = No ; Shares [storage] path = /storage/ valid users = pcosta read only = No create mask = 0777 directory mask = 0777 comment = Storage on Enterprise inherit acls = Yes