1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Integrating MS Windows networks with Samba</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
10 TITLE="SAMBA Project Documentation"
11 HREF="samba-howto-collection.html"><LINK
13 TITLE="Optional configuration"
14 HREF="p1346.html"><LINK
16 TITLE="Optional configuration"
17 HREF="p1346.html"><LINK
19 TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
20 HREF="unix-permissions.html"></HEAD
31 SUMMARY="Header navigation table"
40 >SAMBA Project Documentation</TH
62 HREF="unix-permissions.html"
75 NAME="INTEGRATE-MS-NETWORKS"
77 >Chapter 10. Integrating MS Windows networks with Samba</H1
87 >To identify the key functional mechanisms of MS Windows networking
88 to enable the deployment of Samba as a means of extending and/or
89 replacing MS Windows NT/2000 technology.</P
98 >Name resolution in a pure Unix/Linux TCP/IP
104 >Name resolution as used within MS Windows
110 >How browsing functions and how to deploy stable
111 and dependable browsing using Samba
116 >MS Windows security options and how to
117 configure Samba for seemless integration
122 >Configuration of Samba as:</P
129 >A stand-alone server</P
133 >An MS Windows NT 3.x/4.0 security domain member
138 >An alternative to an MS Windows NT 3.x/4.0 Domain Controller
152 >10.2. Name Resolution in a pure Unix/Linux world</H1
154 >The key configuration files covered in this section are:</P
169 >/etc/resolv.conf</TT
183 >/etc/nsswitch.conf</TT
199 >Contains a static list of IP Addresses and names.
203 CLASS="PROGRAMLISTING"
204 > 127.0.0.1 localhost localhost.localdomain
205 192.168.1.1 bigbox.caldera.com bigbox alias4box</PRE
212 name resolution mechanism so that uses do not need to remember
215 >Network packets that are sent over the physical network transport
216 layer communicate not via IP addresses but rather using the Media
217 Access Control address, or MAC address. IP Addresses are currently
218 32 bits in length and are typically presented as four (4) decimal
219 numbers that are separated by a dot (or period). eg: 168.192.1.1</P
221 >MAC Addresses use 48 bits (or 6 bytes) and are typically represented
222 as two digit hexadecimal numbers separated by colons. eg:
225 >Every network interfrace must have an MAC address. Associated with
226 a MAC address there may be one or more IP addresses. There is NO
227 relationship between an IP address and a MAC address, all such assignments
228 are arbitary or discretionary in nature. At the most basic level all
229 network communications takes place using MAC addressing. Since MAC
230 addresses must be globally unique, and generally remains fixed for
231 any particular interface, the assignment of an IP address makes sense
232 from a network management perspective. More than one IP address can
233 be assigned per MAC address. One address must be the primary IP address,
234 this is the address that will be returned in the ARP reply.</P
236 >When a user or a process wants to communicate with another machine
237 the protocol implementation ensures that the "machine name" or "host
238 name" is resolved to an IP address in a manner that is controlled
239 by the TCP/IP configuration control files. The file
243 > is one such file.</P
245 >When the IP address of the destination interface has been
246 determined a protocol called ARP/RARP is used to identify
247 the MAC address of the target interface. ARP stands for Address
248 Resolution Protocol, and is a broadcast oriented method that
249 uses UDP (User Datagram Protocol) to send a request to all
250 interfaces on the local network segment using the all 1's MAC
251 address. Network interfaces are programmed to respond to two
252 MAC addresses only; their own unique address and the address
253 ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will
254 contain the MAC address and the primary IP address for each
260 > file is foundational to all
261 Unix/Linux TCP/IP installations and as a minumum will contain
262 the localhost and local network interface IP addresses and the
263 primary names by which they are known within the local machine.
264 This file helps to prime the pump so that a basic level of name
265 resolution can exist before any other method of name resolution
266 becomes available.</P
277 >/etc/resolv.conf</TT
280 >This file tells the name resolution libraries:</P
286 >The name of the domain to which the machine
292 >The name(s) of any domains that should be
293 automatically searched when trying to resolve unqualified
294 host names to their IP address
299 >The name or IP address of available Domain
300 Name Servers that may be asked to perform name to address
321 > is the primary means by
322 which the setting in /etc/resolv.conf may be affected. It is a
323 critical configuration file. This file controls the order by
324 which name resolution may procede. The typical structure is:</P
327 CLASS="PROGRAMLISTING"
332 >then both addresses should be returned. Please refer to the
333 man page for host.conf for further details.</P
344 >/etc/nsswitch.conf</TT
347 >This file controls the actual name resolution targets. The
348 file typically has resolver object specifications as follows:</P
351 CLASS="PROGRAMLISTING"
352 > # /etc/nsswitch.conf
354 # Name Service Switch configuration file.
358 # Alternative entries for password authentication are:
359 # passwd: compat files nis ldap winbind
364 # Alternative entries for host name resolution are:
365 # hosts: files dns nis nis+ hesoid db compat ldap wins
366 networks: nis files dns
371 services: nis files</PRE
374 >Of course, each of these mechanisms requires that the appropriate
375 facilities and/or services are correctly configured.</P
377 >It should be noted that unless a network request/message must be
378 sent, TCP/IP networks are silent. All TCP/IP communications assumes a
379 principal of speaking only when necessary.</P
381 >Starting with version 2.2.0 samba has Linux support for extensions to
382 the name service switch infrastructure so that linux clients will
383 be able to obtain resolution of MS Windows NetBIOS names to IP
384 Addresses. To gain this functionality Samba needs to be compiled
385 with appropriate arguments to the make command (ie: <B
388 nsswitch/libnss_wins.so</B
389 >). The resulting library should
390 then be installed in the <TT
394 the "wins" parameter needs to be added to the "hosts:" line in
397 >/etc/nsswitch.conf</TT
398 > file. At this point it
399 will be possible to ping any MS Windows machine by it's NetBIOS
400 machine name, so long as that machine is within the workgroup to
401 which both the samba machine and the MS Windows machine belong.</P
411 >10.3. Name resolution as used within MS Windows networking</H1
413 >MS Windows networking is predicated about the name each machine
414 is given. This name is known variously (and inconsistently) as
415 the "computer name", "machine name", "networking name", "netbios name",
416 "SMB name". All terms mean the same thing with the exception of
417 "netbios name" which can apply also to the name of the workgroup or the
418 domain name. The terms "workgroup" and "domain" are really just a
419 simply name with which the machine is associated. All NetBIOS names
420 are exactly 16 characters in length. The 16th character is reserved.
421 It is used to store a one byte value that indicates service level
422 information for the NetBIOS name that is registered. A NetBIOS machine
423 name is therefore registered for each service type that is provided by
424 the client/server.</P
426 >The following are typical NetBIOS name/service type registrations:</P
429 CLASS="PROGRAMLISTING"
430 > Unique NetBIOS Names:
431 MACHINENAME<00> = Server Service is running on MACHINENAME
432 MACHINENAME<03> = Generic Machine Name (NetBIOS name)
433 MACHINENAME<20> = LanMan Server service is running on MACHINENAME
434 WORKGROUP<1b> = Domain Master Browser
437 WORKGROUP<03> = Generic Name registered by all members of WORKGROUP
438 WORKGROUP<1c> = Domain Controllers / Netlogon Servers
439 WORKGROUP<1d> = Local Master Browsers
440 WORKGROUP<1e> = Internet Name Resolvers</PRE
443 >It should be noted that all NetBIOS machines register their own
444 names as per the above. This is in vast contrast to TCP/IP
445 installations where traditionally the system administrator will
446 determine in the /etc/hosts or in the DNS database what names
447 are associated with each IP address.</P
449 >One further point of clarification should be noted, the <TT
453 file and the DNS records do not provide the NetBIOS name type information
454 that MS Windows clients depend on to locate the type of service that may
455 be needed. An example of this is what happens when an MS Windows client
456 wants to locate a domain logon server. It find this service and the IP
457 address of a server that provides it by performing a lookup (via a
458 NetBIOS broadcast) for enumeration of all machines that have
459 registered the name type *<1c>. A logon request is then sent to each
460 IP address that is returned in the enumerated list of IP addresses. Which
461 ever machine first replies then ends up providing the logon services.</P
463 >The name "workgroup" or "domain" really can be confusing since these
464 have the added significance of indicating what is the security
465 architecture of the MS Windows network. The term "workgroup" indicates
466 that the primary nature of the network environment is that of a
467 peer-to-peer design. In a WORKGROUP all machines are responsible for
468 their own security, and generally such security is limited to use of
469 just a password (known as SHARE MODE security). In most situations
470 with peer-to-peer networking the users who control their own machines
471 will simply opt to have no security at all. It is possible to have
472 USER MODE security in a WORKGROUP environment, thus requiring use
473 of a user name and a matching password.</P
475 >MS Windows networking is thus predetermined to use machine names
476 for all local and remote machine message passing. The protocol used is
477 called Server Message Block (SMB) and this is implemented using
478 the NetBIOS protocol (Network Basic Input Output System). NetBIOS can
479 be encapsulated using LLC (Logical Link Control) protocol - in which case
480 the resulting protocol is called NetBEUI (Network Basic Extended User
481 Interface). NetBIOS can also be run over IPX (Internetworking Packet
482 Exchange) protocol as used by Novell NetWare, and it can be run
483 over TCP/IP protocols - in which case the resulting protocol is called
484 NBT or NetBT, the NetBIOS over TCP/IP.</P
486 >MS Windows machines use a complex array of name resolution mechanisms.
487 Since we are primarily concerned with TCP/IP this demonstration is
488 limited to this area.</P
496 >10.3.1. The NetBIOS Name Cache</H2
498 >All MS Windows machines employ an in memory buffer in which is
499 stored the NetBIOS names and IP addresses for all external
500 machines that that machine has communicated with over the
501 past 10-15 minutes. It is more efficient to obtain an IP address
502 for a machine from the local cache than it is to go through all the
503 configured name resolution mechanisms.</P
505 >If a machine whose name is in the local name cache has been shut
506 down before the name had been expired and flushed from the cache, then
507 an attempt to exchange a message with that machine will be subject
508 to time-out delays. i.e.: Its name is in the cache, so a name resolution
509 lookup will succeed, but the machine can not respond. This can be
510 frustrating for users - but it is a characteristic of the protocol.</P
512 >The MS Windows utility that allows examination of the NetBIOS
513 name cache is called "nbtstat". The Samba equivalent of this
514 is called "nmblookup".</P
523 >10.3.2. The LMHOSTS file</H2
525 >This file is usually located in MS Windows NT 4.0 or
528 >C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
530 the IP Address and the machine name in matched pairs. The
534 > file performs NetBIOS name
535 to IP address mapping oriented.</P
537 >It typically looks like:</P
540 CLASS="PROGRAMLISTING"
541 > # Copyright (c) 1998 Microsoft Corp.
543 # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS
544 # over TCP/IP) stack for Windows98
546 # This file contains the mappings of IP addresses to NT computernames
547 # (NetBIOS) names. Each entry should be kept on an individual line.
548 # The IP address should be placed in the first column followed by the
549 # corresponding computername. The address and the comptername
550 # should be separated by at least one space or tab. The "#" character
551 # is generally used to denote the start of a comment (see the exceptions
554 # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
555 # files and offers the following extensions:
558 # #DOM:<domain>
559 # #INCLUDE <filename>
562 # \0xnn (non-printing character support)
564 # Following any entry in the file with the characters "#PRE" will cause
565 # the entry to be preloaded into the name cache. By default, entries are
566 # not preloaded, but are parsed only after dynamic name resolution fails.
568 # Following an entry with the "#DOM:<domain>" tag will associate the
569 # entry with the domain specified by <domain>. This affects how the
570 # browser and logon services behave in TCP/IP environments. To preload
571 # the host name associated with #DOM entry, it is necessary to also add a
572 # #PRE to the line. The <domain> is always preloaded although it will not
573 # be shown when the name cache is viewed.
575 # Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
576 # software to seek the specified <filename> and parse it as if it were
577 # local. <filename> is generally a UNC-based name, allowing a
578 # centralized lmhosts file to be maintained on a server.
579 # It is ALWAYS necessary to provide a mapping for the IP address of the
580 # server prior to the #INCLUDE. This mapping must use the #PRE directive.
581 # In addtion the share "public" in the example below must be in the
582 # LanManServer list of "NullSessionShares" in order for client machines to
583 # be able to read the lmhosts file successfully. This key is under
584 # \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
585 # in the registry. Simply add "public" to the list found there.
587 # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
588 # statements to be grouped together. Any single successful include
589 # will cause the group to succeed.
591 # Finally, non-printing characters can be embedded in mappings by
592 # first surrounding the NetBIOS name in quotations, then using the
593 # \0xnn notation to specify a hex value for a non-printing character.
595 # The following example illustrates all of these extensions:
597 # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
598 # 102.54.94.102 "appname \0x14" #special app server
599 # 102.54.94.123 popular #PRE #source server
600 # 102.54.94.117 localsrv #PRE #needed for the include
603 # #INCLUDE \\localsrv\public\lmhosts
604 # #INCLUDE \\rhino\public\lmhosts
607 # In the above example, the "appname" server contains a special
608 # character in its name, the "popular" and "localsrv" server names are
609 # preloaded, and the "rhino" server name is specified so it can be used
610 # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
611 # system is unavailable.
613 # Note that the whole file is parsed including comments on each lookup,
614 # so keeping the number of comments to a minimum will improve performance.
615 # Therefore it is not advisable to simply add lmhosts file entries onto the
616 # end of this file.</PRE
626 >10.3.3. HOSTS file</H2
628 >This file is usually located in MS Windows NT 4.0 or 2000 in
631 >C:\WINNT\SYSTEM32\DRIVERS\ETC</TT
633 the IP Address and the IP hostname in matched pairs. It can be
634 used by the name resolution infrastructure in MS Windows, depending
635 on how the TCP/IP environment is configured. This file is in
636 every way the equivalent of the Unix/Linux <TT
648 >10.3.4. DNS Lookup</H2
650 >This capability is configured in the TCP/IP setup area in the network
651 configuration facility. If enabled an elaborate name resolution sequence
652 is followed the precise nature of which isdependant on what the NetBIOS
653 Node Type parameter is configured to. A Node Type of 0 means use
654 NetBIOS broadcast (over UDP broadcast) is first used if the name
655 that is the subject of a name lookup is not found in the NetBIOS name
656 cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to
657 Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the
658 WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast
668 >10.3.5. WINS Lookup</H2
670 >A WINS (Windows Internet Name Server) service is the equivaent of the
671 rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
672 the names and IP addresses that are registered by a Windows client
673 if the TCP/IP setup has been given at least one WINS Server IP Address.</P
675 >To configure Samba to be a WINS server the following parameter needs
676 to be added to the <TT
682 CLASS="PROGRAMLISTING"
683 > wins support = Yes</PRE
686 >To configure Samba to use a WINS server the following parameters are
687 needed in the smb.conf file:</P
690 CLASS="PROGRAMLISTING"
692 wins server = xxx.xxx.xxx.xxx</PRE
701 of the WINS server.</P
711 >10.4. How browsing functions and how to deploy stable and
712 dependable browsing using Samba</H1
714 >As stated above, MS Windows machines register their NetBIOS names
715 (i.e.: the machine name for each service type in operation) on start
716 up. Also, as stated above, the exact method by which this name registration
717 takes place is determined by whether or not the MS Windows client/server
718 has been given a WINS server address, whether or not LMHOSTS lookup
719 is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P
721 >In the case where there is no WINS server all name registrations as
722 well as name lookups are done by UDP broadcast. This isolates name
723 resolution to the local subnet, unless LMHOSTS is used to list all
724 names and IP addresses. In such situations Samba provides a means by
725 which the samba server name may be forcibly injected into the browse
726 list of a remote MS Windows network (using the "remote announce" parameter).</P
728 >Where a WINS server is used, the MS Windows client will use UDP
729 unicast to register with the WINS server. Such packets can be routed
730 and thus WINS allows name resolution to function across routed networks.</P
732 >During the startup process an election will take place to create a
733 local master browser if one does not already exist. On each NetBIOS network
734 one machine will be elected to function as the domain master browser. This
735 domain browsing has nothing to do with MS security domain control.
736 Instead, the domain master browser serves the role of contacting each local
737 master browser (found by asking WINS or from LMHOSTS) and exchanging browse
738 list contents. This way every master browser will eventually obtain a complete
739 list of all machines that are on the network. Every 11-15 minutes an election
740 is held to determine which machine will be the master browser. By the nature of
741 the election criteria used, the machine with the highest uptime, or the
742 most senior protocol version, or other criteria, will win the election
743 as domain master browser.</P
745 >Clients wishing to browse the network make use of this list, but also depend
746 on the availability of correct name resolution to the respective IP
747 address/addresses. </P
749 >Any configuration that breaks name resolution and/or browsing intrinsics
750 will annoy users because they will have to put up with protracted
751 inability to use the network services.</P
753 >Samba supports a feature that allows forced synchonisation
754 of browse lists across routed networks using the "remote
755 browse sync" parameter in the smb.conf file. This causes Samba
756 to contact the local master browser on a remote network and
757 to request browse list synchronisation. This effectively bridges
758 two networks that are separated by routers. The two remote
759 networks may use either broadcast based name resolution or WINS
760 based name resolution, but it should be noted that the "remote
761 browse sync" parameter provides browse list synchronisation - and
762 that is distinct from name to address resolution, in other
763 words, for cross subnet browsing to function correctly it is
764 essential that a name to address resolution mechanism be provided.
765 This mechanism could be via DNS, <TT
778 >10.5. MS Windows security options and how to configure
779 Samba for seemless integration</H1
781 >MS Windows clients may use encrypted passwords as part of a
782 challenege/response authentication model (a.k.a. NTLMv1) or
783 alone, or clear text strings for simple password based
784 authentication. It should be realized that with the SMB
785 protocol the password is passed over the network either
786 in plain text or encrypted, but not both in the same
787 authentication requets.</P
789 >When encrypted passwords are used a password that has been
790 entered by the user is encrypted in two ways:</P
796 >An MD4 hash of the UNICODE of the password
797 string. This is known as the NT hash.
802 >The password is converted to upper case,
803 and then padded or trucated to 14 bytes. This string is
804 then appended with 5 bytes of NULL characters and split to
805 form two 56 bit DES keys to encrypt a "magic" 8 byte value.
806 The resulting 16 bytes for the LanMan hash.
811 >You should refer to the <A
812 HREF="ENCRYPTION.html"
814 >Password Encryption</A
815 > chapter in this HOWTO collection
816 for more details on the inner workings</P
818 >MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x
819 and version 4.0 pre-service pack 3 will use either mode of
820 password authentication. All versions of MS Windows that follow
821 these versions no longer support plain text passwords by default.</P
823 >MS Windows clients have a habit of dropping network mappings that
824 have been idle for 10 minutes or longer. When the user attempts to
825 use the mapped drive connection that has been dropped, the client
826 re-establishes the connection using
827 a cached copy of the password.</P
829 >When Microsoft changed the default password mode, they dropped support for
830 caching of the plain text password. This means that when the registry
831 parameter is changed to re-enable use of plain text passwords it appears to
832 work, but when a dropped mapping attempts to revalidate it will fail if
833 the remote authentication server does not support encrypted passwords.
834 This means that it is definitely not a good idea to re-enable plain text
835 password support in such clients.</P
837 >The following parameters can be used to work around the
838 issue of Windows 9x client upper casing usernames and
839 password before transmitting them to the SMB server
840 when using clear text authentication.</P
843 CLASS="PROGRAMLISTING"
845 HREF="smb.conf.5.html#PASSWORDLEVEL"
855 HREF="smb.conf.5.html#USERNAMELEVEL"
866 >By default Samba will lower case the username before attempting
867 to lookup the user in the database of local system accounts.
868 Because UNIX usernames conventionally only contain lower case
875 is rarely even needed.</P
877 >However, password on UNIX systems often make use of mixed case
878 characters. This means that in order for a user on a Windows 9x
879 client to connect to a Samba server using clear text authentication,
885 > must be set to the maximum
886 number of upper case letter which <SPAN
893 is a password. Note that is the server OS uses the traditional
894 DES version of crypt(), then a <TT
900 of 8 will result in case insensitive passwords as seen from Windows
901 users. This will also result in longer login times as Samba
902 hash to compute the permutations of the password string and
903 try them one by one until a match is located (or all combinations fail).</P
905 >The best option to adopt is to enable support for encrypted passwords
906 where ever Samba is used. There are three configuration possibilities
907 for support of encrypted passwords:</P
915 >10.5.1. Use MS Windows NT as an authentication server</H2
917 >This method involves the additions of the following parameters
918 in the smb.conf file:</P
921 CLASS="PROGRAMLISTING"
922 > encrypt passwords = Yes
924 password server = "NetBIOS_name_of_PDC"</PRE
927 >There are two ways of identifying whether or not a username and
928 password pair was valid or not. One uses the reply information provided
929 as part of the authentication messaging process, the other uses
930 just and error code.</P
932 >The down-side of this mode of configuration is the fact that
933 for security reasons Samba will send the password server a bogus
934 username and a bogus password and if the remote server fails to
935 reject the username and password pair then an alternative mode
936 of identification of validation is used. Where a site uses password
937 lock out after a certain number of failed authentication attempts
938 this will result in user lockouts.</P
940 >Use of this mode of authentication does require there to be
941 a standard Unix account for the user, this account can be blocked
942 to prevent logons by other than MS Windows clients.</P
951 >10.5.2. Make Samba a member of an MS Windows NT security domain</H2
953 >This method involves additon of the following paramters in the smb.conf file:</P
956 CLASS="PROGRAMLISTING"
957 > encrypt passwords = Yes
959 workgroup = "name of NT domain"
960 password server = *</PRE
963 >The use of the "*" argument to "password server" will cause samba
964 to locate the domain controller in a way analogous to the way
965 this is done within MS Windows NT.</P
967 >In order for this method to work the Samba server needs to join the
968 MS Windows NT security domain. This is done as follows:</P
974 >On the MS Windows NT domain controller using
975 the Server Manager add a machine account for the Samba server.
980 >Next, on the Linux system execute:
983 >smbpasswd -r PDC_NAME -j DOMAIN_NAME</B
989 >Use of this mode of authentication does require there to be
990 a standard Unix account for the user in order to assign
991 a uid once the account has been authenticated by the remote
992 Windows DC. This account can be blocked to prevent logons by
993 other than MS Windows clients by things such as setting an invalid
999 >An alternative to assigning UIDs to Windows users on a
1000 Samba member server is presented in the <A
1003 >Winbind Overview</A
1005 this HOWTO collection.</P
1014 >10.5.3. Configure Samba as an authentication server</H2
1016 >This mode of authentication demands that there be on the
1017 Unix/Linux system both a Unix style account as well as an
1018 smbpasswd entry for the user. The Unix system account can be
1019 locked if required as only the encrypted password will be
1020 used for SMB client authentication.</P
1022 >This method involves addition of the following parameters to
1023 the smb.conf file:</P
1026 CLASS="PROGRAMLISTING"
1027 >## please refer to the Samba PDC HOWTO chapter later in
1028 ## this collection for more details
1030 encrypt passwords = Yes
1033 ; an OS level of 33 or more is recommended
1037 path = /somewhare/in/file/system
1038 read only = yes</PRE
1041 >in order for this method to work a Unix system account needs
1042 to be created for each user, as well as for each MS Windows NT/2000
1043 machine. The following structure is required.</P
1051 >10.5.3.1. Users</H3
1053 >A user account that may provide a home directory should be
1054 created. The following Linux system commands are typical of
1055 the procedure for creating an account.</P
1058 CLASS="PROGRAMLISTING"
1059 > # useradd -s /bin/bash -d /home/"userid" -m "userid"
1061 Enter Password: <pw>
1063 # smbpasswd -a "userid"
1064 Enter Password: <pw></PRE
1074 >10.5.3.2. MS Windows NT Machine Accounts</H3
1076 >These are required only when Samba is used as a domain
1077 controller. Refer to the Samba-PDC-HOWTO for more details.</P
1080 CLASS="PROGRAMLISTING"
1081 > # useradd -s /bin/false -d /dev/null "machine_name"\$
1082 # passwd -l "machine_name"\$
1083 # smbpasswd -a -m "machine_name"</PRE
1095 >10.6. Conclusions</H1
1097 >Samba provides a flexible means to operate as...</P
1103 >A Stand-alone server - No special action is needed
1104 other than to create user accounts. Stand-alone servers do NOT
1105 provide network logon services, meaning that machines that use this
1106 server do NOT perform a domain logon but instead make use only of
1107 the MS Windows logon which is local to the MS Windows
1113 >An MS Windows NT 3.x/4.0 security domain member.
1118 >An alternative to an MS Windows NT 3.x/4.0
1130 SUMMARY="Footer navigation table"
1150 HREF="samba-howto-collection.html"
1159 HREF="unix-permissions.html"
1169 >Optional configuration</TD
1183 >UNIX Permission Bits and Windows NT Access Control Lists</TD