- Very good "by example" document:
  http://us2.samba.org/samba/docs/man/guide/
- Even longer good reference
  http://us2.samba.org/samba/docs/man/howto/


OUTLINE:

- Check for right version of Samba installed

- Add a slide about CUPS and printer queues


HANDS-ON TASKS:

   - http://us2.samba.org/samba/docs/man/guide/simple.html

2. Server with multiple shares, printer queue, share security, force user
    - Procedure 2.4.
    - Step 10 of printer setup. If routing to remote CUPS server, use
      lpadmin -p PRINTERNAME -v smb://WORKGROUP/SERVER/SHARE
    - Mention SUID and SGID purpose
    - Step 5 of Windows Printer setup may actually be Details Tab+Add
      Port+"\\server\PRINTQ"


3. Procedure 2.9.
    - smb.conf different from tutorial
    - Users
      joel
      linuxconf1
      linuxconf2


NOTES:


- Network browsing involves SMB broadcast announcements, SMB
  enumeration requests, connections to the IPC$ share, share
  enumerations, and SMB connection setup processes. The use of
  anonymous connections to a Samba server involve the use of the guest
  account that must map to a valid UNIX UID.

    \\COMPUTER\IPC$
    - Probed using the NULL account to get list of shared resources
    - Samba requires all accesses to be mapped to valid user accounts.
    - Normally the NULL account is mapped to the UNIX account nobody.

smbpasswd -a 'username'
    - Add a user to the password database backend
    - User must exist in /etc/passwd

Share and user mode


- When NetBIOS over TCP/IP protocols are enabled, MS Windows
  networking employs broadcast oriented messaging protocols to provide
  knowledge of network services.
- Network browsing protocols query information stored on Browse
  Masters that manage information provided by NetBIOS Name
  Registrations and by way of on-going Host Announcements and
  Workgroup Announcements.
- All Samba servers must be configured with a mechanism for mapping
  the NULL-Session to a valid but non-privileged UNIX system account.
- The use of Microsoft encrypted passwords is built right into the
  fabric of Windows networking operations. Such passwords cannot be
  provided from the UNIX /etc/passwd database and thus must be stored
  elsewhere on the UNIX system in a manner that Samba can use.
  Samba-2.x permitted such encrypted passwords to be stored in the
  smbpasswd file or in an LDAP database. Samba-3 permits that use of
  multiple different passdb backend databases, in concurrent deploy.
  Refer to TOSHARG, Chapter 10, Account Information Databases.