4 >The Samba 2.2 PDC FAQ</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
26 >The Samba 2.2 PDC FAQ</A
38 >La Trobe University<BR></SPAN
47 >Comments, corrections and additions to <TT
50 HREF="mailto:D.Bannon@latrobe.edu.au"
51 >D.Bannon@latrobe.edu.au</A
55 >This is the FAQ for Samba 2.2 as an NTDomain controller.
56 This document is derived from the origional FAQ that was built and
57 maintained by Gerald Carter
58 from the early days of Samba NTDomain development up until recently.
59 It is now being updated as significent changes are made to 2.2.0.</P
61 >Please note it does not apply to Samba2.2alpha0, Samba2.2alpha1, Samba 2.0.7, TNG nor HEAD branch.
64 >I'll repeat, it does not apply to the current snapshot [ftp mirror]:/pub/samba/alpha/samba-2.2.0-alpha1.tar.gz, only to the to the current cvs.</P
66 > Also available is a Samba 2.2 PDC <A
67 HREF="samba-pdc-howto.html"
70 > that takes you, step
71 by step, over the process of setting up a very basic Samba 2.2 Primary Domain Controller
80 >Please read the Introduction for the current <A
115 >General Information</A
129 >What can Samba Primary Domain Controller (PDC) do ?</A
134 >Can I have a Windows 2000 client logon to a Samba controlled domain?</A
139 >What's the status of print spool (spoolss) support in the NTDOM code?</A
153 >What are the different Samba branches available in CVS ?</A
158 >What are the CVS commands ?</A
167 >Establishing Connections</A
181 >How do I get my NT4 or W2000 Workstation to login to the Samba controlled Domain?</A
186 >What is a 'machine account' ?</A
191 >"The machine account for this computer either does not exist or is not accessable."</A
196 >How do I create machine accounts manually ?</A
201 >I cannot include a '$' in a machine name.</A
206 >I get told "You already have a connection to the Domain...." when creating a
212 >I get told "Cannot join domain, the credentials supplied conflict
213 with an existing set.."</A
218 >"The system can not log you on (C000019B)...."</A
227 >User Account Management</A
241 >How do I configure an account as a domain administrator?</A
255 >Why is it bad to set "logon path = \\%N\%U\profile" in smb.conf? ?</A
260 >Why are all the users listed in the "domain admin users" using the same profile?</A
265 >The roaming profiles do not seem to be updating on the server.</A
279 >What are 'Policies' ?.</A
284 >I can't get system policies to work.</A
289 >What about Windows NT Policy Editor ?</A
294 >Can Win95 do Policies ?</A
308 >What is password sync and should I use it ?</A
313 >How do I get remote password (unix and SMB) changing working ?</A
336 >What editor can I use in DOS/Windows that won't mess with my unix EOF</A
341 >How do I get 'User Manager' and 'Server Manager'</A
346 >The time setting from a Samba server does not work.</A
351 >"trust account xxx should be in DOMAIN_GROUP_RID_USERS"</A
356 >How do I get my samba server to become a member ( not PDC ) of an NT domain?</A
365 >Troubleshooting and Bug Reporting</A
379 >What are some diagnostics tools I can use to debug the domain logon process and where can I
385 >How do I install 'Network Monitor' on an NT Workstation or a Windows 9x box?</A
392 >What other help can I get ?</A
404 >How do I get help from the mailing lists ?</A
409 >How do I get off the mailing lists ?</A
422 >Chapter 1. Introduction</A
435 >It should be noted that 2.2.0 in its pre-release form still has a few problems,
436 I'll try and keep this section current while things are still dynamic.
437 At the time of this update (November 13, 2000) the current state of play is :</I
440 >Comments here about W2K joining the domain apply only to Samba 2.2 from the CVS after November 27th. The
441 'snapshot' release Samba2.2alpha1 does not work !!! See below on how to get a CVS tree.</P
443 >Client Side creation of Machine accounts does work but is not complete.
447 > runs as the user who's
448 name was entered, not as root. Secondly, the machine name passed to the script (%U)
449 has an underscore at the end, not a '$'. One alternative is to use %m and add the $.
450 This method is documented in the <A
451 HREF="samba-pdc-howto.html"
455 And thirdly, it does not work with NT4ws.
458 >A W2K machine can join the domain. See the <A
459 HREF="samba-pdc-howto.html"
463 which explains the process. The methods
464 described are 'work arounds' and should be regarded as temporary. Although I (drb)
465 have tested these procedures a number of people have had difficulty so there
466 may be other issues at work. JFM is aware of these
467 problems and will attend to them when he can.</P
469 >A Domain Admin account is required and at present it appears that only root
470 is a suitable candidate.</P
472 >Much of the related code does work. For example, if an NT is removed from the
473 domain and then rejoins, the <TT
475 >Create a Computer Account in the Domain</TT
477 will let you reset the smbpasswd. That is you don't need to do it from
478 the unix box. However, at the present, you do need to have root as an
479 administrator and use the root user name and password.</P
484 not sure that last paragraph is correct ....</I
490 > do work on a W2K machine. MS says that recent builds of
491 W2K dont observe an NT policy but it appears it does in 'legacy' mode.</P
502 >This FAQ was origionally compiled by Jerry Carter (gc) chiefly dealing with the 'old head'
503 version of Samba and its NTDomain facilities. It is being rewritten by David Bannon (drb)
504 so that it addresses more accurately the Samba 2.2 planned for release late 2000. </P
506 >This document probably still contains some material that does not apply to
507 Samba 2.2 but most (all?) of the really misleading stuff has been removed. Some
508 issues are not dealt with or are dealt with badly. Please send corrections and additions to
509 David Bannon at D.Bannon@latrobe.edu.au</P
511 >Hopefully, as we all become familiar with the Samba 2.2 as a PDC this document will
512 become much more usefull.</P
520 >Chapter 2. General Information</A
536 >What can Samba Primary Domain Controller (PDC) do ?</A
539 >If you wish to have Samba act as a PDC for Windows NT 3.51.and 4.0 or W2000 client, then you
540 will need to obtain the 2.2.0 version, currently in pre-release. Release of a stable,
541 full featured Samba PDC is currently slated for version 3.0. </P
543 >The following is a list of included features currently in Samba 2.2:</P
549 >The ability to act as a limited PDC for Windows NT and W2000 clients.
550 This includes adding NT and W2K machines to the domain and authenticating users logging
555 >Domain account can be viewed using the User Manager for
560 >Viewing resources on the Samba PDC via the Server Manager for Domains
561 from the NT client. ??</P
565 >Windows 95 clients will allow user level security to be set
566 but will not currently allow browsing of accounts.</P
570 >Machine account password updates.</P
574 >Changing of user passwords from an NT client.</P
578 >Partial support for Windows NT group and username mapping.</P
582 >Support for a LDAP password database backend.</P
593 >These things are note expected to work in the forseeable future</B
598 >Trust relationships</P
602 >PDC and BDC integration</P
606 >Windows NT ACLs (on the Samba shares)</P
610 >Offer a list of domain users to User Manager for Domains
611 (or the Security Tab etc).</P
621 >Can I have a Windows 2000 client logon to a Samba controlled domain?</A
624 >The 2.2 release branch of Samba supports Windows 2000 domain
625 clients in legacy mode, ie as if the PDC is a NTServer, not a
634 >What's the status of print spool (spoolss) support in the NTDOM code?</A
637 >The implementation of support for SPOOLSS pipe is complete and it will be available
638 in the 2.2.0 release. This means that Samba will support the automatic downloading of printer
639 drivers for Windows NT clients just as it currently does for Windows 9x clients.</P
651 >CVS is a programme (publically available) that the Samba developers use to
652 maintain the central source code. Non developers can get access to the source in
653 a read only capacity. Many flavours of unix now arrive with cvs installed.</P
660 >What are the different Samba branches available in CVS ?</A
663 >You can find out more about obtaining Samba's via
666 HREF="http://pserver.samba.org/samba/cvs.html"
668 > http://pserver.samba.org/samba/cvs.html"</A
676 >There are basically four branches to watch at the moment :</B
683 >Samba 3.0 ? This code boasts all the main development
684 work in Samba. Two things that most people are not aware of
685 which live in the HEAD branch code are winbind NSS module and
686 Tim Potter's VFS implementation. Due to its developmental
687 nature, its not really suitable for production work.
694 >This branch contains the current stable release release.
695 At the moment it contains 2.0.7, a version that will do some
696 limited PDC stuff. If you are really going to do PDC things then
697 I (drb) suggest that you consider 2.2 instead.
704 >The next stable release, currently in a 'alpha' form.
705 It provides the Samba developers, testers and interested
706 people with an approximation of what is to come. This document
707 addresses only SAMBA_2_2.
714 >This branch is no longer maintained from the Samba sites.
716 HREF="http://www.samba-tng.org/"
718 > http://www.samba-tng.org/</A
719 >. It has been requested
720 that questions about TNG are not posted to the regular Samba mailing
721 lists including samba-ntdom and samba-technical.
733 >What are the CVS commands ?</A
737 HREF="http://pserver.samba.org/samba/cvs.html"
739 > http://pserver.samba.org/samba/cvs.html</A
745 >To get the Samba 2.2 version, tag SAMBA_2_2 you would do :</B
752 >cd /usr/local/src/</B
759 >cvs -d :pserver:cvs@pserver.samba.org:/cvsroot
765 > When prompted enter a password of <B
774 >cvs -d :pserver:cvs@pserver.samba.org:/cvsroot
775 co -r SAMBA_2_2 samba</B
783 >Then to update that directory at some later time,</B
790 >cd /usr/local/src/samba</B
797 >cvs -d :pserver:cvs@pserver.samba.org:/cvsroot login</B
802 > When prompted enter a password of 'cvs'.</P
820 >Chapter 3. Establishing Connections</A
836 >How do I get my NT4 or W2000 Workstation to login to the Samba controlled Domain?</A
839 >There is a comprehensive Samba PDC <A
840 HREF="samba-pdc-howto.html"
844 accessable from the samba web site
845 under 'Documentation'. Its currently located at <A
846 HREF="http://bioserve.latrobe.edu.au/samba"
848 > http://bioserve.latrobe.edu.au/samba</A
857 >What is a 'machine account' ?</A
860 >Every NT, W2K or Samba machine that joins a Samba controlled domain must be known to
861 the Samba PDC. There are two entries required, one in (typically) <TT
865 and the other in (typically) <TT
867 >/usr/local/samba/private/smbpasswd</TT
869 some circumstances these entries are made <A
874 HREF="samba-pdc-howto.html"
877 > discusses ways of creating them automatically.</P
885 >"The machine account for this computer either does not exist or is not accessable."</A
888 >When I try to join the domain I get the message "The machine account for this computer
889 either does not exist or is not accessable". Whats wrong ?</P
891 >This problem is caused by the PDC not having a suitable machine account.
892 If you are using the <B
894 >add user script =</B
895 > method to create accounts
896 then this would indicate that it has not worked. Ensure the domain admin user
897 system is working.</P
899 >Alternatively if you are creating account entries manually then they have not been created
900 correctly. Make sure that you have the entry correct for the machine account in smbpasswd
901 file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd utility,
902 make sure that the account name is the machine netbios name with a '$' appended to it
903 ( ie. computer_name$ ). There must be an entry in both /etc/passwd and
904 the smbpasswd file. Some people have reported that
905 inconsistent subnet masks between the Samba server and the NT client have caused this problem.
906 Make sure that these are consistent for both client and server.</P
914 >How do I create machine accounts manually ?</A
917 >This was the only option until recently, now in version 2.2 better means are available.
918 You might still need to do it manually for a couple of reasons. A machine account
919 consists of two entries (assuming a standard install and /etc/passwd use),
920 one in /etc/passwd and the other in /usr/local/samba/private/smbpasswd. The /etc/passwd
921 entry will list the machine name with a $ appended, won't have a passwd, will have a null
922 shell and no home directory. For example a machine called 'doppy' would have an /etc/passwd
927 >doppy$:x:505:501:NTMachine:/dev/null:/bin/false</B
930 >On a linux system for example, you would typically add it like this :</P
934 >adduser -g machines -c NTMachine -d /dev/null -s /bin/false -n
938 >Then you need to add that entry to smbpasswd, assuming you have a suitable
942 > programme, do this :</P
946 >smbpasswd -a -m doppy$</B
949 >The entry will be created with a well known password, so any machine that
950 says its doppy could join the domain as long as it gets in first. So don't create
951 the accounts any earlier than you need them.</P
959 >I cannot include a '$' in a machine name.</A
962 >A 'machine name' in (typically) <TT
966 of the machine name with a '$' appended. FreeBSD (and other BSD systems ?)
967 won't create a user with a '$' in their name.</P
969 >The problem is only in the program used to make the entry, once made, it works
970 perfectly. So create a user without the '$' and use <B
974 the entry, adding the '$'. Or create the whole entry with vipw if you like,
975 make sure you use a unique uid !</P
983 >I get told "You already have a connection to the Domain...." when creating a
987 >This happens if you try to create a machine account from the machine itself
988 and use a user name that does not work (for whatever reason) and then try
989 another (possibly valid) user name.
990 Exit out of the network applet to close the initial connection and try again.</P
992 >Further, if the machine is a already a 'member of a workgroup' that is the
993 same name as the domain you are joining (bad idea) you will get this message.
994 Change the workgroup name to something else, it does not matter what, reboot,
1003 >I get told "Cannot join domain, the credentials supplied conflict
1004 with an existing set.."</A
1007 >This is the same basic problem as mentioned above, <A
1009 > "You already have a connection..."</A
1018 >"The system can not log you on (C000019B)...."</A
1021 >I joined the domain successfully but after upgrading to a newer version of the
1022 Samba code I get the message, "The system can not log you on (C000019B), Please try a
1023 gain or consult your system administrator" when attempting to logon.</P
1025 >This occurs when the domain SID stored in private/WORKGROUP.SID is changed.
1026 For example, you remove the file and smbd automatically creates a new one.
1027 Or you are swapping back and forth between versions 2.0.7, TNG and the HEAD branch
1028 code (not recommended). The only way to correct the problem is to restore the
1029 original domain SID or remove the domain client from the domain and rejoin.</P
1038 >Chapter 4. User Account Management</A
1054 >How do I configure an account as a domain administrator?</A
1058 HREF="samba-pdc-howto.html"
1078 >Why is it bad to set "logon path = \\%N\%U\profile" in smb.conf? ?</A
1081 >Sometimes Windows clients will maintain a connection to the \\homes\ ( or [%U] ) share
1082 even after the user has logged out. Consider the following scenario.</P
1088 > user1 logs into the Windows NT machine. Therefore the
1089 [homes] share is set to \\server\user1.</P
1093 > user1 works for a while and then logs out. </P
1097 > user2 logs into the same Windows NT machine.</P
1101 >However, since the NT box has maintained a connection to [homes] which was
1102 previously set to \\server\user1, when the operating system attempts to
1103 get the profile and if it can read users1's profile, will get it otherwise it
1104 will return an error. You get the picture.</P
1106 >A better solution is to use a separate [profiles] share and set the
1107 "logon path = \\%N\profiles\%U" </P
1115 >Is this still a problem ????</P
1125 >Why are all the users listed in the "domain admin users" using the same profile?</A
1128 >You are using a very very old development version of Samba. Upgrade.</P
1136 >The roaming profiles do not seem to be updating on the server.</A
1139 >There can be several reasons for this.</P
1141 >Make sure that the time on the client and the PDC are synchronized. You can accomplish
1142 this by executing a <B
1144 >net time \\server /set /yes</B
1145 > replacing server with the
1146 name of your PDC (or another synchronized SMB server). See <A
1148 > about Setting Time</A
1152 logon path is writeable by the user and make sure that the connection to the logon
1153 path location is by the current user. Sometimes Windows client do not drop the
1154 connection immediately upon logoff.</P
1156 >Some people have reported that the logon path location should also be browseable.
1157 I (GC) have yet to emperically verify this, but you can try.</P
1174 >What are 'Policies' ?.</A
1177 >When a user logs onto the domain via a client machine, the PDC sends
1178 the client machine a list of things contained in the 'policy' (if it exists).
1179 This list may do things like suppress a splach screen, format the dates the way you
1180 like them or perhaps remove locally stored profiles.</P
1182 >On a samba PDC this list is obtained from a file called <B
1186 and located in the <B
1189 >share. The file is created with a policy editor
1190 and must be readable by anyone and writeable by only root. See <A
1193 > for how to get a suitable editor.</P
1201 >I can't get system policies to work.</A
1204 >There are two possible reasons for system policies not functioning correctly.
1205 Make sure that you have the following parameters set in smb.conf </P
1207 CLASS="PROGRAMLISTING"
1216 >A policy file must be in the <B
1220 readable by everyone and writeable by only root. The file must be created
1226 >Last time I (drb) looked in the source, it was
1230 > first then several other combinations of upper
1231 and lower case. People have reported success using <TT
1241 >. These are the case
1242 settings that I (GC) use with the
1248 CLASS="PROGRAMLISTING"
1249 > case sensitive = no
1260 >What about Windows NT Policy Editor ?</A
1263 >To create or edit <B
1266 > you must use the NT Server
1270 > which is included with NT Server
1273 >not NT Workstation</I
1274 >. There is a Policy Editor on a NTws
1275 but it is not suitable for creating <I
1279 Further, although the Windows 95
1280 Policy Editor can be installed on an NT Workstation/Server, it will not
1281 work with NT policies because the registry key that are set by the policy templates.
1282 However, the files from the NT Server will run happily enough on an NTws.
1285 >poledit.exe, common.adm</TT
1290 to put the two *.adm files in <TT
1294 the binary will look for them unless told otherwise. Note also that that
1295 directory is 'hidden'.</P
1297 >The Windows NT policy editor is also included with the
1298 Service Pack 3 (and later) for Windows NT 4.0. Extract the files using
1301 >servicepackname /x</B
1306 for service pack 6a.
1307 The policy editor, <B
1310 > and the associated template files (*.adm) should
1311 be extracted as well. It is also possible to downloaded the policy template
1312 files for Office97 and get a copy of the policy editor. Another possible
1313 location is with the Zero Administration Kit available for download from Microsoft.
1322 >Can Win95 do Policies ?</A
1325 >Install the group policy handler for Win9x to pick up group policies.
1326 Look on the Win98 CD in <TT
1328 > \tools\reskit\netadmin\poledit</TT
1329 >. Install group policies on a Win9x client by double-clicking
1333 >. Log off and on again a couple of times and see if
1334 Win98 picks up group policies.
1335 Unfortunately this needs to be done on every Win9x machine that uses group policies....</P
1337 >If group policies don't work one reports suggests getting the updated (read: working)
1338 grouppol.dll for Windows 9x. The group list is grabbed from /etc/group.</P
1355 >What is password sync and should I use it ?</A
1358 >NTws users can change their domain password by pressing Ctrl-Alt-Del and
1359 choosing 'Change Password'. By default however, this does not change the unix password
1362 >/etc/passwd or /etc/shadow</TT
1363 >). In lots of situations
1364 thats OK, for example :</P
1370 >The server is only accessible to the user via samba.</P
1374 >Pam_smb or similar is installed so other applications
1375 still refer to the samba password.</P
1379 >But sometimes you really do need to maintain two seperate password databases and
1380 there are good reasons to keep then in sync. Trying to explain to users
1381 that they need to change their passwords in two seperate places or use
1382 two seperate passwords is not fun.</P
1384 >However do understand that setting up password sync is not without problems either.
1385 The chief difficulty is the interface between Samba and the <B
1389 it can be a fiddle to set up and if the password the user has entered fails,
1390 the resulting errors are ambiguously reported
1391 and the user is confused. Further, you need to take steps to ensure that users
1392 only ever change their passwords via samba (or use <B
1396 otherwise they will only be changing the unix password.</P
1404 >How do I get remote password (unix and SMB) changing working ?</A
1407 >Have a practice changing a user's password (as root) to see what
1408 discussion takes place and change the text in the 'passwd chat' line below as necessary. The
1409 line as shown works for recent RH Linux but most other systems seem to like to do something
1410 different. The '*' is a wild card and will match anything (or nothing).
1413 >Add these lines to smb.conf under [Global]</P
1415 CLASS="PROGRAMLISTING"
1418 unix password sync = true
1419 passwd program = /usr/bin/passwd %u
1420 passwd chat = *password* %n\n *password* %n\n *successful*
1423 >As mentioned above, the change to the unix password
1424 happens as root, not as the user, as is indicated in ~/smbd/chgpasswd.c If
1425 you are using NIS, the Samba server must be running on the NIS master machine.</P
1434 >Chapter 5. Miscellaneous</A
1450 >What editor can I use in DOS/Windows that won't mess with my unix EOF</A
1453 >There are a number of Windows or DOS based editors that will understand, and
1454 leave intact, the unix eof (as opposed to a DOS CL/LF). List members suggested :</P
1461 HREF="http://www.ultraedit.com"
1463 >www.ultraedit.com</A
1468 >VI for windows at <A
1469 HREF="http://home.snafu.de/ramo/WinViEn.htm"
1471 > home.snafu.de/ramo/WinViEn.htm</A
1476 >The author prefers PFE at <A
1477 HREF="http://www.lancs.ac.uk/people/cpaap/pfe/"
1479 > www.lancs.ac.uk/people/cpaap/pfe/</A
1480 > but its no longer being developed...</P
1490 >How do I get 'User Manager' and 'Server Manager'</A
1493 >Since I don't need to buy an NT Server CD now, how do I get the 'User Manager for
1494 Domains', the 'Server Manager' ?</P
1499 >Microsoft distributes a version of these tools called nexus
1500 for installation on Windows 95 systems. The tools set includes</B
1509 >User Manager for Domains</P
1517 >Click here to download the archived file
1519 HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
1521 > ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
1524 >The Windows NT 4.0 version of the 'User Manager for Domains'
1525 and 'Server Manager' are available from Microsoft via ftp from
1527 HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
1529 > ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
1538 >The time setting from a Samba server does not work.</A
1541 >If it works OK when you log on as Domain Admin then the problem is that ordinary users
1542 don't have permission to change the time. (The system is running with their permission
1543 at logon time.) This is not a Samba problem, you will have the same problem where ever
1544 you connect. You can give 'everyone' permission to change the time from the User Manager.
1547 >Anyone know what the registry settings are so this could be done with a Policy ?</P
1555 >"trust account xxx should be in DOMAIN_GROUP_RID_USERS"</A
1558 >I keep getting the message "trust account xxx should be in DOMAIN_GROUP_RID_USERS."
1559 in the logs. What do I need to do?</P
1561 >You are using one of the old development versions. Upgrade.
1562 (The message is unimportant, was a reminder to a developer)</P
1570 >How do I get my samba server to become a member ( not PDC ) of an NT domain?</A
1573 >In a domain that has a number of servers you only need one password database.
1574 The machines that don't have their own ask the PDC to check for them.
1575 This will work fine for a domain controlled by either a Samba or NT machine.
1576 The following lines in smb.conf are typical, 'password server' points to the
1577 samba machine (or an NT) that has the password list : </P
1579 CLASS="PROGRAMLISTING"
1585 workgroup = { Put your domain name here }
1586 password server = { Put the ip of the PDC here }
1587 encrypt passwords = yes
1591 >The samba server in question will have to 'join the domain', that requires
1592 the domain controller to have a machine account for it. This is no different
1593 to the machine account requirements to allow a NTws to join the domain. For
1594 example, if we want a unix box called <I
1597 > to ask the PDC called <I
1601 to do its authentication then <I
1604 > will need an entry in its smbpasswd
1605 (assuming it's also samba) that starts with <I
1608 >. It would have to be
1614 >If the domain is controlled by an NTServer then the "Server Manager for Domains"
1615 tool must be used to add 'sleepy' to the domain list.</P
1617 >In either case we then join the domain. If the domain is called <I
1621 then on sleepy we would join the domain by typing :</P
1625 >smbpasswd -j forest</B
1628 >Note that the directory where the smbpasswd file would be
1629 located should exist as this is where smbd will generate the MACHINE.SID file. This
1632 >/usr/local/samba/private/FOREST.SLEEPY.SID</TT
1634 it contains the trust account password for the domain member. The permissions are
1635 (and should remain) "rw-------</P
1637 >Note the Samba Servers without the password list will most likely still need an account
1638 for each user, this means a line in its <TT
1641 >. Because authentication
1642 is being handled at the domain level the
1646 > line does not need a password.
1647 If the shares being offered are not user specific, ie a common (read only ?)
1648 area or perhaps just printing then the user's
1652 > does not need a home directory. A typical
1656 > for a server that allows domain users to
1657 connect to the samba shares but does not offer a home share ('cos that's on the PDC)
1658 and does not allow logon to the unix prompt would be like this :</P
1660 CLASS="PROGRAMLISTING"
1661 >jblow:x:542:100:Joe Blow:/dev/null:/bin/false</PRE
1671 >When removing those 'dummy' users, watch the 'remove user' scripts,
1672 some OS think they should remove a users directory even when its not owned by the user !
1679 >username map = </TT
1680 > parameter might help you to avoid having
1681 all those accounts created.</P
1685 >You should investigate the smb.conf parameter
1688 >'add user script'</TT
1689 >, it will be used to create accounts on
1690 secondary servers when that account already exists on the PDC. Very nice.
1693 CLASS="PROGRAMLISTING"
1696 add user script = /usr/sbin/adduser -n -g users -c User -d /dev/null -s /bin/false %U
1711 >Chapter 6. Troubleshooting and Bug Reporting</A
1719 >Diagnostic tools</A
1727 >What are some diagnostics tools I can use to debug the domain logon process and where can I
1731 >One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d
1732 option for both smbd and nmbd to specifiy what 'debug level' at which to run. See the man
1733 pages on smbd, nmbd and smb.conf for more information on debugging options. The debug
1734 level can range from 1 (the default) to around 100 but a debug level of about 20 will
1735 normally help you find any errors that samba is encountering. Another helpful method
1736 of debugging is to compile samba using the gcc -g flag. This will include debug
1737 information in the binaries and allow you to attch gdb to the running smbd / nmbd
1738 process. In order to attach gdb to an smbd process for an NT workstation, first
1739 get the workstation to make the connection. Pressing ctrl-alt-delete and going down
1740 to the domain box is sufficient (at least, on the first time you join the domain) to
1741 generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation maintains an open
1742 connection, and therefore there will be an smbd process running (assuming that you
1743 haven't set a really short smbd idle timeout) So, in between pressing ctrl alt
1744 delete, and actually typing in your password, you can gdb attach and continue.</P
1749 >Some usefull samba commands worth investigating:</B
1754 >testparam | more</P
1758 >smbclient -L //{netbios name of server}</P
1762 >An SMB enabled version of tcpdump is available from
1764 HREF="ftp://samba.org/pub/samba/tcpdump-smb/"
1766 >ftp://samba.org/pub/samba/tcpdump-smb/
1770 >Capconvert is a small C program for translating output from tcpdump-smb to CAP format
1771 that can be read by netmon. You will need to use the raw output from tcp dump
1774 >tcpdump -w output.dump</B
1775 > ). Good news! Now you can convert
1776 Solaris' snoop output as well. The C source code for snoop2cap is available for download.
1779 >For tracing things on the Microsoft Windows NT, Network Monitor (aka. netmon) is available
1780 on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's.
1781 The version of netmon that ships with SMS allows for dumping packets between any two
1782 computers (ie. placing the network interface in promiscuous mode). The version
1783 on the NT Server install CD will only allow monitoring of network traffic directed to the
1784 local NT box and broadcasts on the local subnet.</P
1792 >How do I install 'Network Monitor' on an NT Workstation or a Windows 9x box?</A
1795 >Installing netmon on an NT workstation requires a couple of steps. The following
1796 are for installing Netmon V4.00.349, which comes with Microsoft Windows NT Server
1797 4.0, on Microsoft Windows NT Workstation 4.0. The process should be similar
1798 for other version of Windows NT / Netmon. You will need both the Microsoft Windows
1799 NT Server 4.0 Install CD and the Workstation 4.0 Install CD.</P
1801 >Initially you will need to install 'Network Monitor Tools and Agent' on the
1802 NT Server. To do this </P
1808 >Goto Start - Settings - Control Panel - Network - Services - Add </P
1812 >Select the 'Network Monitor Tools and Agent' and click on 'OK'.</P
1816 >Click 'OK' on the Network Control Panel.</P
1820 >Insert the Windows NT Server 4.0 install CD when prompted.</P
1824 >At this point the Netmon files should exist in <TT
1826 >%SYSTEMROOT%\System32\netmon\*.*</TT
1828 Two subdirectories exist as well, <TT
1831 > which contains the necessary DLL's
1832 for parsing the netmon packet dump, and <TT
1837 >In order to install the Netmon tools on an NT Workstation, you will first need to
1838 install the 'Network Monitor Agent' from the Workstation install CD.</P
1844 >Goto Start - Settings - Control Panel - Network - Services - Add</P
1848 >Select the 'Network Monitor Agent' and click on 'OK'.</P
1852 >Click 'OK' on the Network Control Panel.</P
1856 >Insert the Windows NT Workstation 4.0 install CD when prompted.</P
1860 >Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* to
1861 %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set permissions as
1862 you deem appropriate for your site. You will need administrative rights on the
1863 NT box to run netmon.</P
1865 >To install Netmon on a Windows 9x box install the network monitor agent from
1866 the Windows 9x CD (\admin\nettools\netmon).
1867 There is a readme file located with the netmon driver files on the CD if you need
1868 information on how to do this. Copy the files from a working Netmon installation.</P
1877 >What other help can I get ?</A
1880 >There are many sources of information available in the form of mailing lists, RFC's
1881 and documentation. The docs that come with the samba distribution contain very
1882 good explanations of general SMB topics such as browsing.</P
1889 >URLs and similar</A
1896 >Home of Samba site <A
1897 HREF="http://samba.org"
1899 > http://samba.org</A
1900 >. We have a mirror near you !</P
1908 on the Samba mirrors might mention your problem. If so,
1909 it might mean that the developers are working on it.</P
1913 > Ignacio Coupeau has a very comprehesive look at LDAP with Samba at
1915 HREF="http://www.unav.es/cti/ldap-smb-howto.html"
1917 > http://www.unav.es/cti/ldap-smb-howto.html</A
1919 Be a little carefull however, I suspect that it does not specificly
1920 address samba 2.2.x. The HEAD pre-2.1 may possibly be the best
1921 stream to look at.</P
1925 > Lars Kneschke's site covers <A
1926 HREF="http://www.samba-tng.org"
1931 HREF="http://www.kneschke.de/projekte/samba_tng"
1933 > http://www.kneschke.de/projekte/samba_tng</A
1935 lot of it does not apply to the main stream Samba.</P
1939 >Although 2.0.7 has almost had its day as a PDC, I (drb) will
1940 keep the 2.0.7 PDC pages at <A
1941 HREF="http://bioserve.latrobe.edu.au/samba"
1943 > http://bioserve.latrobe.edu.au/samba</A
1944 > going for a while yet.</P
1948 >Misc links to CIFS information
1950 HREF="http://samba.org/cifs/"
1952 >http://samba.org/cifs/</A
1957 >NT Domains for Unix <A
1958 HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
1960 > http://mailhost.cb1.com/~lkcl/ntdom/</A
1965 >FTP site for older SMB specs:
1967 HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
1969 > ftp://ftp.microsoft.com/developr/drg/CIFS/</A
1977 >There are a number of documents that no longer appear to live at their
1978 origional home. Any one know where the following may be found ?</B
1983 >CIFS/E Browser Protocol draft-leach-cifs-browser-spec-00.txt</P
1987 >CIFS Remote Administration Protocol draft-leach-cifs-rap-spec-00.txt</P
1991 >CIFS Logon and Pass Through Authentication draft-leach-cifs-logon-spec-00.txt</P
1995 >A Common Internet File System (CIFS/1.0) Protocol draft-leach-cifs-v1-spec-01.txt</P
1999 >CIFS Printing Specification draft-leach-cifs-print-spec-00.txt</P
2003 >RFC1001 (March '87) Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods.
2004 http://ds.internic.net/rfc/rfc1001.txt </P
2008 >RFC1002 (March '87) Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications.
2009 http://ds.internic.net/rfc/rfc1002.txt </P
2013 >Microsoft's main CIFS page: http://www.microsoft.com/workshop/networking/cifs/</P
2023 >How do I get help from the mailing lists ?</A
2026 > There are a number of Samba related mailing lists. Go to <A
2027 HREF="http://samba.org"
2029 >http://samba.org</A
2030 >, click on your nearest mirror
2031 and then click on <B
2034 > and then click on <B
2036 > Samba related mailing lists</B
2039 >For questions relating to Samba TNG go to
2041 HREF="http://www.samba-tng.org/"
2043 >http://www.samba-tng.org/</A
2045 It has been requested that you don't post questions about Samba-TNG to the
2046 main stream Samba lists.</P
2051 >If you post a message to one of the lists please
2052 observe the following guide lines :</B
2057 > Always remember that the developers are volunteers, they are
2058 not paid and they never guarantee to produce a particular feature at
2059 a particular time. Any time lines are 'best guess' and nothing more.
2064 > Always mention what version of samba you are using and what
2065 operating system its running under. You should probably list the
2066 relevant sections of your smb.conf file, at least the options
2067 in [global] that affect PDC support.</P
2071 >In addition to the version, if you obtained Samba via
2072 CVS mention the date when you last checked it out.</P
2076 > Try and make your question clear and brief, lots of long,
2077 convoluted questions get deleted before they are completely read !
2078 Don't post html encoded messages (if you can select colour or font
2083 > If you run one of those niffy 'I'm on holidays' things when
2084 you are away, make sure its configured to not answer mailing lists.
2089 > Don't cross post. Work out which is the best list to post to
2090 and see what happens, ie don't post to both samba-ntdom and samba-technical.
2091 Many people active on the lists subscribe to more
2092 than one list and get annoyed to see the same message two or more times.
2093 Often someone will see a message and thinking it would be better dealt
2094 with on another, will forward it on for you.</P
2098 >You might include <I
2102 log files written at a debug level set to as much as 20.
2103 Please don't send the entire log but enough to give the context of the
2108 >(Possibly) If you have a complete netmon trace ( from the opening of
2109 the pipe to the error ) you can send the *.CAP file as well.</P
2113 >Please think carefully before attaching a document to an email.
2114 Consider pasting the relevant parts into the body of the message. The samba
2115 mailing lists go to a huge number of people, do they all need a copy of your
2116 smb.conf in their attach directory ?</P
2126 >How do I get off the mailing lists ?</A
2129 >To have your name removed from a samba mailing list, go to the
2130 same place you went to to get on it. Go to <A
2131 HREF="http://samba.org"
2133 >http://samba.org</A
2134 >, click on your nearest mirror
2135 and then click on <B
2138 > and then click on <B
2140 > Samba related mailing lists</B
2143 HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
2148 >Please don't post messages to the list asking to be removed, you will just
2149 be refered to the above address (unless that process failed in some way...)