1 <chapter id="integrate-ms-networks">
6 <firstname>John</firstname><surname>Terpstra</surname>
8 <orgname>Samba Team</orgname>
10 <email>jht@samba.org</email>
16 <pubdate> (Jan 01 2001) </pubdate>
19 <title>Integrating MS Windows networks with Samba</title>
25 To identify the key functional mechanisms of MS Windows networking
26 to enable the deployment of Samba as a means of extending and/or
27 replacing MS Windows NT/2000 technology.
35 <listitem><para>Name resolution in a pure Unix/Linux TCP/IP
39 <listitem><para>Name resolution as used within MS Windows
43 <listitem><para>How browsing functions and how to deploy stable
44 and dependable browsing using Samba
47 <listitem><para>MS Windows security options and how to
48 configure Samba for seemless integration
51 <listitem><para>Configuration of Samba as:</para>
53 <listitem><para>A stand-alone server</para></listitem>
54 <listitem><para>An MS Windows NT 3.x/4.0 security domain member
56 <listitem><para>An alternative to an MS Windows NT 3.x/4.0 Domain Controller
66 <title>Name Resolution in a pure Unix/Linux world</title>
69 The key configuration files covered in this section are:
73 <listitem><para><filename>/etc/hosts</filename></para></listitem>
74 <listitem><para><filename>/etc/resolv.conf</filename></para></listitem>
75 <listitem><para><filename>/etc/host.conf</filename></para></listitem>
76 <listitem><para><filename>/etc/nsswitch.conf</filename></para></listitem>
80 <title><filename>/etc/hosts</filename></title>
83 Contains a static list of IP Addresses and names.
86 <para><programlisting>
87 127.0.0.1 localhost localhost.localdomain
88 192.168.1.1 bigbox.caldera.com bigbox alias4box
89 </programlisting></para>
92 The purpose of <filename>/etc/hosts</filename> is to provide a
93 name resolution mechanism so that uses do not need to remember
99 Network packets that are sent over the physical network transport
100 layer communicate not via IP addresses but rather using the Media
101 Access Control address, or MAC address. IP Addresses are currently
102 32 bits in length and are typically presented as four (4) decimal
103 numbers that are separated by a dot (or period). eg: 168.192.1.1
107 MAC Addresses use 48 bits (or 6 bytes) and are typically represented
108 as two digit hexadecimal numbers separated by colons. eg:
113 Every network interfrace must have an MAC address. Associated with
114 a MAC address there may be one or more IP addresses. There is NO
115 relationship between an IP address and a MAC address, all such assignments
116 are arbitary or discretionary in nature. At the most basic level all
117 network communications takes place using MAC addressing. Since MAC
118 addresses must be globally unique, and generally remains fixed for
119 any particular interface, the assignment of an IP address makes sense
120 from a network management perspective. More than one IP address can
121 be assigned per MAC address. One address must be the primary IP address,
122 this is the address that will be returned in the ARP reply.
126 When a user or a process wants to communicate with another machine
127 the protocol implementation ensures that the "machine name" or "host
128 name" is resolved to an IP address in a manner that is controlled
129 by the TCP/IP configuration control files. The file
130 <filename>/etc/hosts</filename> is one such file.
134 When the IP address of the destination interface has been
135 determined a protocol called ARP/RARP is used to identify
136 the MAC address of the target interface. ARP stands for Address
137 Resolution Protocol, and is a broadcast oriented method that
138 uses UDP (User Datagram Protocol) to send a request to all
139 interfaces on the local network segment using the all 1's MAC
140 address. Network interfaces are programmed to respond to two
141 MAC addresses only; their own unique address and the address
142 ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will
143 contain the MAC address and the primary IP address for each
148 The <filename>/etc/hosts</filename> file is foundational to all
149 Unix/Linux TCP/IP installations and as a minumum will contain
150 the localhost and local network interface IP addresses and the
151 primary names by which they are known within the local machine.
152 This file helps to prime the pump so that a basic level of name
153 resolution can exist before any other method of name resolution
161 <title><filename>/etc/resolv.conf</filename></title>
164 This file tells the name resolution libraries:
168 <listitem><para>The name of the domain to which the machine
172 <listitem><para>The name(s) of any domains that should be
173 automatically searched when trying to resolve unqualified
174 host names to their IP address
177 <listitem><para>The name or IP address of available Domain
178 Name Servers that may be asked to perform name to address
187 <title><filename>/etc/host.conf</filename></title>
191 <filename>/etc/host.conf</filename> is the primary means by
192 which the setting in /etc/resolv.conf may be affected. It is a
193 critical configuration file. This file controls the order by
194 which name resolution may procede. The typical structure is:
197 <para><programlisting>
200 </programlisting></para>
203 then both addresses should be returned. Please refer to the
204 man page for host.conf for further details.
213 <title><filename>/etc/nsswitch.conf</filename></title>
216 This file controls the actual name resolution targets. The
217 file typically has resolver object specifications as follows:
221 <para><programlisting>
224 # Name Service Switch configuration file.
228 # Alternative entries for password authentication are:
229 # passwd: compat files nis ldap winbind
234 # Alternative entries for host name resolution are:
235 # hosts: files dns nis nis+ hesoid db compat ldap wins
236 networks: nis files dns
242 </programlisting></para>
245 Of course, each of these mechanisms requires that the appropriate
246 facilities and/or services are correctly configured.
250 It should be noted that unless a network request/message must be
251 sent, TCP/IP networks are silent. All TCP/IP communications assumes a
252 principal of speaking only when necessary.
256 Starting with version 2.2.0 samba has Linux support for extensions to
257 the name service switch infrastructure so that linux clients will
258 be able to obtain resolution of MS Windows NetBIOS names to IP
259 Addresses. To gain this functionality Samba needs to be compiled
260 with appropriate arguments to the make command (ie: <command>make
261 nsswitch/libnss_wins.so</command>). The resulting library should
262 then be installed in the <filename>/lib</filename> directory and
263 the "wins" parameter needs to be added to the "hosts:" line in
264 the <filename>/etc/nsswitch.conf</filename> file. At this point it
265 will be possible to ping any MS Windows machine by it's NetBIOS
266 machine name, so long as that machine is within the workgroup to
267 which both the samba machine and the MS Windows machine belong.
275 <title>Name resolution as used within MS Windows networking</title>
278 MS Windows networking is predicated about the name each machine
279 is given. This name is known variously (and inconsistently) as
280 the "computer name", "machine name", "networking name", "netbios name",
281 "SMB name". All terms mean the same thing with the exception of
282 "netbios name" which can apply also to the name of the workgroup or the
283 domain name. The terms "workgroup" and "domain" are really just a
284 simply name with which the machine is associated. All NetBIOS names
285 are exactly 16 characters in length. The 16th character is reserved.
286 It is used to store a one byte value that indicates service level
287 information for the NetBIOS name that is registered. A NetBIOS machine
288 name is therefore registered for each service type that is provided by
293 The following are typical NetBIOS name/service type registrations:
296 <para><programlisting>
297 Unique NetBIOS Names:
298 MACHINENAME<00> = Server Service is running on MACHINENAME
299 MACHINENAME<03> = Generic Machine Name (NetBIOS name)
300 MACHINENAME<20> = LanMan Server service is running on MACHINENAME
301 WORKGROUP<1b> = Domain Master Browser
304 WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
305 WORKGROUP<1c> = Domain Controllers / Netlogon Servers
306 WORKGROUP<1d> = Local Master Browsers
307 WORKGROUP<1e> = Internet Name Resolvers
308 </programlisting></para>
311 It should be noted that all NetBIOS machines register their own
312 names as per the above. This is in vast contrast to TCP/IP
313 installations where traditionally the system administrator will
314 determine in the /etc/hosts or in the DNS database what names
315 are associated with each IP address.
319 One further point of clarification should be noted, the <filename>/etc/hosts</filename>
320 file and the DNS records do not provide the NetBIOS name type information
321 that MS Windows clients depend on to locate the type of service that may
322 be needed. An example of this is what happens when an MS Windows client
323 wants to locate a domain logon server. It find this service and the IP
324 address of a server that provides it by performing a lookup (via a
325 NetBIOS broadcast) for enumeration of all machines that have
326 registered the name type *<1c>. A logon request is then sent to each
327 IP address that is returned in the enumerated list of IP addresses. Which
328 ever machine first replies then ends up providing the logon services.
332 The name "workgroup" or "domain" really can be confusing since these
333 have the added significance of indicating what is the security
334 architecture of the MS Windows network. The term "workgroup" indicates
335 that the primary nature of the network environment is that of a
336 peer-to-peer design. In a WORKGROUP all machines are responsible for
337 their own security, and generally such security is limited to use of
338 just a password (known as SHARE MODE security). In most situations
339 with peer-to-peer networking the users who control their own machines
340 will simply opt to have no security at all. It is possible to have
341 USER MODE security in a WORKGROUP environment, thus requiring use
342 of a user name and a matching password.
346 MS Windows networking is thus predetermined to use machine names
347 for all local and remote machine message passing. The protocol used is
348 called Server Message Block (SMB) and this is implemented using
349 the NetBIOS protocol (Network Basic Input Output System). NetBIOS can
350 be encapsulated using LLC (Logical Link Control) protocol - in which case
351 the resulting protocol is called NetBEUI (Network Basic Extended User
352 Interface). NetBIOS can also be run over IPX (Internetworking Packet
353 Exchange) protocol as used by Novell NetWare, and it can be run
354 over TCP/IP protocols - in which case the resulting protocol is called
355 NBT or NetBT, the NetBIOS over TCP/IP.
359 MS Windows machines use a complex array of name resolution mechanisms.
360 Since we are primarily concerned with TCP/IP this demonstration is
361 limited to this area.
365 <title>The NetBIOS Name Cache</title>
368 All MS Windows machines employ an in memory buffer in which is
369 stored the NetBIOS names and IP addresses for all external
370 machines that that machine has communicated with over the
371 past 10-15 minutes. It is more efficient to obtain an IP address
372 for a machine from the local cache than it is to go through all the
373 configured name resolution mechanisms.
377 If a machine whose name is in the local name cache has been shut
378 down before the name had been expired and flushed from the cache, then
379 an attempt to exchange a message with that machine will be subject
380 to time-out delays. i.e.: Its name is in the cache, so a name resolution
381 lookup will succeed, but the machine can not respond. This can be
382 frustrating for users - but it is a characteristic of the protocol.
386 The MS Windows utility that allows examination of the NetBIOS
387 name cache is called "nbtstat". The Samba equivalent of this
388 is called "nmblookup".
394 <title>The LMHOSTS file</title>
397 This file is usually located in MS Windows NT 4.0 or
398 2000 in <filename>C:\WINNT\SYSTEM32\DRIVERS\ETC</filename> and contains
399 the IP Address and the machine name in matched pairs. The
400 <filename>LMHOSTS</filename> file performs NetBIOS name
401 to IP address mapping oriented.
405 It typically looks like:
408 <para><programlisting>
409 # Copyright (c) 1998 Microsoft Corp.
411 # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
412 # over TCP/IP) stack for Windows98
414 # This file contains the mappings of IP addresses to NT computernames
415 # (NetBIOS) names. Each entry should be kept on an individual line.
416 # The IP address should be placed in the first column followed by the
417 # corresponding computername. The address and the comptername
418 # should be separated by at least one space or tab. The "#" character
419 # is generally used to denote the start of a comment (see the exceptions
422 # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
423 # files and offers the following extensions:
426 # #DOM:<domain>
427 # #INCLUDE <filename>
430 # \0xnn (non-printing character support)
432 # Following any entry in the file with the characters "#PRE" will cause
433 # the entry to be preloaded into the name cache. By default, entries are
434 # not preloaded, but are parsed only after dynamic name resolution fails.
436 # Following an entry with the "#DOM:<domain>" tag will associate the
437 # entry with the domain specified by <domain>. This affects how the
438 # browser and logon services behave in TCP/IP environments. To preload
439 # the host name associated with #DOM entry, it is necessary to also add a
440 # #PRE to the line. The <domain> is always preloaded although it will not
441 # be shown when the name cache is viewed.
443 # Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
444 # software to seek the specified <filename> and parse it as if it were
445 # local. <filename> is generally a UNC-based name, allowing a
446 # centralized lmhosts file to be maintained on a server.
447 # It is ALWAYS necessary to provide a mapping for the IP address of the
448 # server prior to the #INCLUDE. This mapping must use the #PRE directive.
449 # In addtion the share "public" in the example below must be in the
450 # LanManServer list of "NullSessionShares" in order for client machines to
451 # be able to read the lmhosts file successfully. This key is under
452 # \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
453 # in the registry. Simply add "public" to the list found there.
455 # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
456 # statements to be grouped together. Any single successful include
457 # will cause the group to succeed.
459 # Finally, non-printing characters can be embedded in mappings by
460 # first surrounding the NetBIOS name in quotations, then using the
461 # \0xnn notation to specify a hex value for a non-printing character.
463 # The following example illustrates all of these extensions:
465 # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
466 # 102.54.94.102 "appname \0x14" #special app server
467 # 102.54.94.123 popular #PRE #source server
468 # 102.54.94.117 localsrv #PRE #needed for the include
471 # #INCLUDE \\localsrv\public\lmhosts
472 # #INCLUDE \\rhino\public\lmhosts
475 # In the above example, the "appname" server contains a special
476 # character in its name, the "popular" and "localsrv" server names are
477 # preloaded, and the "rhino" server name is specified so it can be used
478 # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
479 # system is unavailable.
481 # Note that the whole file is parsed including comments on each lookup,
482 # so keeping the number of comments to a minimum will improve performance.
483 # Therefore it is not advisable to simply add lmhosts file entries onto the
485 </programlisting></para>
490 <title>HOSTS file</title>
493 This file is usually located in MS Windows NT 4.0 or 2000 in
494 <filename>C:\WINNT\SYSTEM32\DRIVERS\ETC</filename> and contains
495 the IP Address and the IP hostname in matched pairs. It can be
496 used by the name resolution infrastructure in MS Windows, depending
497 on how the TCP/IP environment is configured. This file is in
498 every way the equivalent of the Unix/Linux <filename>/etc/hosts</filename> file.
504 <title>DNS Lookup</title>
507 This capability is configured in the TCP/IP setup area in the network
508 configuration facility. If enabled an elaborate name resolution sequence
509 is followed the precise nature of which isdependant on what the NetBIOS
510 Node Type parameter is configured to. A Node Type of 0 means use
511 NetBIOS broadcast (over UDP broadcast) is first used if the name
512 that is the subject of a name lookup is not found in the NetBIOS name
513 cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to
514 Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the
515 WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast
522 <title>WINS Lookup</title>
525 A WINS (Windows Internet Name Server) service is the equivaent of the
526 rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
527 the names and IP addresses that are registered by a Windows client
528 if the TCP/IP setup has been given at least one WINS Server IP Address.
532 To configure Samba to be a WINS server the following parameter needs
533 to be added to the <filename>smb.conf</filename> file:
536 <para><programlisting>
538 </programlisting></para>
541 To configure Samba to use a WINS server the following parameters are
542 needed in the smb.conf file:
545 <para><programlisting>
547 wins server = xxx.xxx.xxx.xxx
548 </programlisting></para>
551 where <replaceable>xxx.xxx.xxx.xxx</replaceable> is the IP address
560 <title>How browsing functions and how to deploy stable and
561 dependable browsing using Samba</title>
565 As stated above, MS Windows machines register their NetBIOS names
566 (i.e.: the machine name for each service type in operation) on start
567 up. Also, as stated above, the exact method by which this name registration
568 takes place is determined by whether or not the MS Windows client/server
569 has been given a WINS server address, whether or not LMHOSTS lookup
570 is enabled, or if DNS for NetBIOS name resolution is enabled, etc.
574 In the case where there is no WINS server all name registrations as
575 well as name lookups are done by UDP broadcast. This isolates name
576 resolution to the local subnet, unless LMHOSTS is used to list all
577 names and IP addresses. In such situations Samba provides a means by
578 which the samba server name may be forcibly injected into the browse
579 list of a remote MS Windows network (using the "remote announce" parameter).
583 Where a WINS server is used, the MS Windows client will use UDP
584 unicast to register with the WINS server. Such packets can be routed
585 and thus WINS allows name resolution to function across routed networks.
589 During the startup process an election will take place to create a
590 local master browser if one does not already exist. On each NetBIOS network
591 one machine will be elected to function as the domain master browser. This
592 domain browsing has nothing to do with MS security domain control.
593 Instead, the domain master browser serves the role of contacting each local
594 master browser (found by asking WINS or from LMHOSTS) and exchanging browse
595 list contents. This way every master browser will eventually obtain a complete
596 list of all machines that are on the network. Every 11-15 minutes an election
597 is held to determine which machine will be the master browser. By the nature of
598 the election criteria used, the machine with the highest uptime, or the
599 most senior protocol version, or other criteria, will win the election
600 as domain master browser.
604 Clients wishing to browse the network make use of this list, but also depend
605 on the availability of correct name resolution to the respective IP
610 Any configuration that breaks name resolution and/or browsing intrinsics
611 will annoy users because they will have to put up with protracted
612 inability to use the network services.
616 Samba supports a feature that allows forced synchonisation
617 of browse lists across routed networks using the "remote
618 browse sync" parameter in the smb.conf file. This causes Samba
619 to contact the local master browser on a remote network and
620 to request browse list synchronisation. This effectively bridges
621 two networks that are separated by routers. The two remote
622 networks may use either broadcast based name resolution or WINS
623 based name resolution, but it should be noted that the "remote
624 browse sync" parameter provides browse list synchronisation - and
625 that is distinct from name to address resolution, in other
626 words, for cross subnet browsing to function correctly it is
627 essential that a name to address resolution mechanism be provided.
628 This mechanism could be via DNS, <filename>/etc/hosts</filename>,
635 <title>MS Windows security options and how to configure
636 Samba for seemless integration</title>
639 MS Windows clients may use encrypted passwords as part of a
640 challenege/response authentication model (a.k.a. NTLMv1) or
641 alone, or clear text strings for simple password based
642 authentication. It should be realized that with the SMB
643 protocol the password is passed over the network either
644 in plain text or encrypted, but not both in the same
645 authentication requets.
649 When encrypted passwords are used a password that has been
650 entered by the user is encrypted in two ways:
654 <listitem><para>An MD4 hash of the UNICODE of the password
655 string. This is known as the NT hash.
658 <listitem><para>The password is converted to upper case,
659 and then padded or trucated to 14 bytes. This string is
660 then appended with 5 bytes of NULL characters and split to
661 form two 56 bit DES keys to encrypt a "magic" 8 byte value.
662 The resulting 16 bytes for the LanMan hash.
667 You should refer to the <ulink url="ENCRYPTION.html">
668 Password Encryption</ulink> chapter in this HOWTO collection
669 for more details on the inner workings
673 MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x
674 and version 4.0 pre-service pack 3 will use either mode of
675 password authentication. All versions of MS Windows that follow
676 these versions no longer support plain text passwords by default.
680 MS Windows clients have a habit of dropping network mappings that
681 have been idle for 10 minutes or longer. When the user attempts to
682 use the mapped drive connection that has been dropped, the client
683 re-establishes the connection using
684 a cached copy of the password.
688 When Microsoft changed the default password mode, they dropped support for
689 caching of the plain text password. This means that when the registry
690 parameter is changed to re-enable use of plain text passwords it appears to
691 work, but when a dropped mapping attempts to revalidate it will fail if
692 the remote authentication server does not support encrypted passwords.
693 This means that it is definitely not a good idea to re-enable plain text
694 password support in such clients.
698 The following parameters can be used to work around the
699 issue of Windows 9x client upper casing usernames and
700 password before transmitting them to the SMB server
701 when using clear text authentication.
704 <para><programlisting>
705 <ulink url="smb.conf.5.html#PASSWORDLEVEL">passsword level</ulink> = <replaceable>integer</replaceable>
706 <ulink url="smb.conf.5.html#USERNAMELEVEL">username level</ulink> = <replaceable>integer</replaceable>
707 </programlisting></para>
710 By default Samba will lower case the username before attempting
711 to lookup the user in the database of local system accounts.
712 Because UNIX usernames conventionally only contain lower case
713 character, the <parameter>username level</parameter> parameter
714 is rarely even needed.
718 However, password on UNIX systems often make use of mixed case
719 characters. This means that in order for a user on a Windows 9x
720 client to connect to a Samba server using clear text authentication,
721 the <parameter>password level</parameter> must be set to the maximum
722 number of upper case letter which <emphasis>could</emphasis> appear
723 is a password. Note that is the server OS uses the traditional
724 DES version of crypt(), then a <parameter>password level</parameter>
725 of 8 will result in case insensitive passwords as seen from Windows
726 users. This will also result in longer login times as Samba
727 hash to compute the permutations of the password string and
728 try them one by one until a match is located (or all combinations fail).
732 The best option to adopt is to enable support for encrypted passwords
733 where ever Samba is used. There are three configuration possibilities
734 for support of encrypted passwords:
739 <title>Use MS Windows NT as an authentication server</title>
742 This method involves the additions of the following parameters
743 in the smb.conf file:
746 <para><programlisting>
747 encrypt passwords = Yes
749 password server = "NetBIOS_name_of_PDC"
750 </programlisting></para>
754 There are two ways of identifying whether or not a username and
755 password pair was valid or not. One uses the reply information provided
756 as part of the authentication messaging process, the other uses
761 The down-side of this mode of configuration is the fact that
762 for security reasons Samba will send the password server a bogus
763 username and a bogus password and if the remote server fails to
764 reject the username and password pair then an alternative mode
765 of identification of validation is used. Where a site uses password
766 lock out after a certain number of failed authentication attempts
767 this will result in user lockouts.
771 Use of this mode of authentication does require there to be
772 a standard Unix account for the user, this account can be blocked
773 to prevent logons by other than MS Windows clients.
779 <title>Make Samba a member of an MS Windows NT security domain</title>
782 This method involves additon of the following paramters in the smb.conf file:
785 <para><programlisting>
786 encrypt passwords = Yes
788 workgroup = "name of NT domain"
790 </programlisting></para>
793 The use of the "*" argument to "password server" will cause samba
794 to locate the domain controller in a way analogous to the way
795 this is done within MS Windows NT.
799 In order for this method to work the Samba server needs to join the
800 MS Windows NT security domain. This is done as follows:
804 <listitem><para>On the MS Windows NT domain controller using
805 the Server Manager add a machine account for the Samba server.
808 <listitem><para>Next, on the Linux system execute:
809 <command>smbpasswd -r PDC_NAME -j DOMAIN_NAME</command>
814 Use of this mode of authentication does require there to be
815 a standard Unix account for the user in order to assign
816 a uid once the account has been authenticated by the remote
817 Windows DC. This account can be blocked to prevent logons by
818 other than MS Windows clients by things such as setting an invalid
819 shell in the <filename>/etc/passwd</filename> entry.
823 An alternative to assigning UIDs to Windows users on a
824 Samba member server is presented in the <ulink
825 url="winbind.html">Winbind Overview</ulink> chapter in
826 this HOWTO collection.
834 <title>Configure Samba as an authentication server</title>
837 This mode of authentication demands that there be on the
838 Unix/Linux system both a Unix style account as well as an
839 smbpasswd entry for the user. The Unix system account can be
840 locked if required as only the encrypted password will be
841 used for SMB client authentication.
845 This method involves addition of the following parameters to
849 <para><programlisting>
850 ## please refer to the Samba PDC HOWTO chapter later in
851 ## this collection for more details
853 encrypt passwords = Yes
856 ; an OS level of 33 or more is recommended
860 path = /somewhare/in/file/system
862 </programlisting></para>
865 in order for this method to work a Unix system account needs
866 to be created for each user, as well as for each MS Windows NT/2000
867 machine. The following structure is required.
874 A user account that may provide a home directory should be
875 created. The following Linux system commands are typical of
876 the procedure for creating an account.
879 <para><programlisting>
880 # useradd -s /bin/bash -d /home/"userid" -m "userid"
882 Enter Password: <pw>
884 # smbpasswd -a "userid"
885 Enter Password: <pw>
886 </programlisting></para>
890 <title>MS Windows NT Machine Accounts</title>
893 These are required only when Samba is used as a domain
894 controller. Refer to the Samba-PDC-HOWTO for more details.
897 <para><programlisting>
898 # useradd -s /bin/false -d /dev/null "machine_name"\$
899 # passwd -l "machine_name"\$
900 # smbpasswd -a -m "machine_name"
901 </programlisting></para>
908 <title>Conclusions</title>
911 Samba provides a flexible means to operate as...
915 <listitem><para>A Stand-alone server - No special action is needed
916 other than to create user accounts. Stand-alone servers do NOT
917 provide network logon services, meaning that machines that use this
918 server do NOT perform a domain logon but instead make use only of
919 the MS Windows logon which is local to the MS Windows
923 <listitem><para>An MS Windows NT 3.x/4.0 security domain member.
927 <listitem><para>An alternative to an MS Windows NT 3.x/4.0