vb.net qr code reader Figure 10.1: Server Manager in Software

Make Code39 in Software Figure 10.1: Server Manager

Example 10.1 Creating a Domain Server Password $ smbpasswd j <Domain Name> r <PDC Name>. Now it's time to start the smbd and nmbd daemons on the server. Samba should log-on to the domain during initialization. You can verify active membership using Server Manager (Figure 10.2).

Although Samba's domain controller functionality is not quite on a par with Windows NT yet, you may still want to consider running Samba as a domain controller for your Windows 9x clients. One reason is that by using Samba as the domain's authentication service, you can collocate UNIX and NetBIOS namespace administration on the same server platform. It may also be that your in-house system administration skills and platform support infrastructure favor running a domain controller under UNIX rather than Windows NT. Whatever the reason, you'll find that Samba will perform adequately as a domain controller in the Windows 9x context. Domain control for Windows NT clients entails additional undocumented protocol support and still lies in the realm of the experimental Samba PDC effort. To enlist Samba as the domain controller for your Windows 9x domain you'll need to verify that WINS service has been configured and is available (see 8). You can run WINS under Samba by enabling the wins support parameter. If WINS services are provided by another machine, identify the remote server's IP address or DNS name using the wins server parameter. Remember that wins support and wins server are mutually exclusive. wins support = yes

- 134 -

wins server = <IP address or DNS name> Identify the NetBIOS name of the server and the domain name using the netbios name and workgroup parameters respectively. netbios name = <NetBIOS name> workgroup = <domain name> You will also need to configure the server to act as the domain master browser (see 9). Remember that in a Windows NT domain controller world, the PDC is also the domain master browser. Enable the server's domain master, local master, and preferred master parameters and set the os level parameter to "65" indicating that Samba is emulating Windows NT Server. os level = 65 domain master = yes local master = yes preferred master = yes Next you need to create a netlogon a share to support domain logons. This share will be used to store logon scripts and the system policy file, CONFIG.POL (see the "Policies" section later in this chapter). The following is an example netlogin share definition. Make certain that the netlogin share is "read-only" to ensure that the domain's system policies and logon scripts can't be modified by clients: [netlogon] comment = Network Logon Service path = /usr/local/samba/lib/netlogon public = no writable = no locking = no Verify the netlogin share configuration by invoking the smbclient command with the -U<username> option. You can include the associated password on the command line by using the "%" character as a delimiter between the username and password: $ smbclient U <username>[%<password>] If Samba will also be providing a private file store for each client, verify that a homes share is defined in smb.conf (see 11). The homes share is a special service that provides access to a user's UNIX $HOME directory by referencing the user name when accessing the share. You can also designate that the home directory be mounted as a specified drive letter at login time by setting the logon drive and logon home parameters: [homes] comment = Home Directories browseable = no writable = yes

- 135 -

logon drive = <drive letter> logon home = \\%N\%U Now you're ready to permit domain logins by enabling the domain logons parameter. You'll also need to verify that the security parameter has a value of user and that encrypt passwords is enabled. security = user encrypt passwords = yes domain logons = yes