1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
|
<HTML
><HEAD
><TITLE
>The Samba 2.2 PDC FAQ</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="BOOK"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="BOOK"
><A
NAME="SAMBA-PDC-FAQ"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="SAMBA-PDC-FAQ"
>The Samba 2.2 PDC FAQ</A
></H1
><H3
CLASS="AUTHOR"
><A
NAME="AEN4"
>David Bannon</A
></H3
><DIV
CLASS="AFFILIATION"
><SPAN
CLASS="ORGNAME"
>La Trobe University<BR></SPAN
></DIV
><HR></DIV
><HR><H1
><A
NAME="AEN12"
></A
></H1
><P
>Comments, corrections and additions to <TT
CLASS="EMAIL"
><<A
HREF="mailto:D.Bannon@latrobe.edu.au"
>D.Bannon@latrobe.edu.au</A
>></TT
></P
><P
>This is the FAQ for Samba 2.2 as an NTDomain controller.
This document is derived from the origional FAQ that was built and
maintained by Gerald Carter
from the early days of Samba NTDomain development up until recently.
It is now being updated as significent changes are made to 2.2.0.</P
><P
>Please note it does not apply to Samba2.2alpha0, Samba2.2alpha1, Samba 2.0.7, TNG nor HEAD branch.
</P
><P
>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
><P
> Also available is a Samba 2.2 PDC <A
HREF="samba-pdc-howto.html"
TARGET="_top"
>HowTo</A
> that takes you, step
by step, over the process of setting up a very basic Samba 2.2 Primary Domain Controller
</P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>Please read the Introduction for the current <A
HREF="#AEN27"
> state of play</A
>.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="#AEN25"
>Introduction</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN27"
>State of Play</A
></DT
><DT
><A
HREF="#AEN44"
>Introduction</A
></DT
></DL
></DD
><DT
>2. <A
HREF="#AEN49"
>General Information</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN51"
>What can we do ?</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN53"
>What can Samba Primary Domain Controller (PDC) do ?</A
></DT
><DT
><A
HREF="#AEN86"
>Can I have a Windows 2000 client logon to a Samba controlled domain?</A
></DT
><DT
><A
HREF="#AEN89"
>What's the status of print spool (spoolss) support in the NTDOM code?</A
></DT
></DL
></DD
><DT
><A
HREF="#AEN92"
>CVS</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN95"
>What are the different Samba branches available in CVS ?</A
></DT
><DT
><A
HREF="#AEN118"
>What are the CVS commands ?</A
></DT
></DL
></DD
></DL
></DD
><DT
>3. <A
HREF="#AEN149"
>Establishing Connections</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN151"
></A
></DT
><DD
><DL
><DT
><A
HREF="#AEN153"
>How do I get my NT4 or W2000 Workstation to login to the Samba controlled Domain?</A
></DT
><DT
><A
HREF="#AEN158"
>What is a 'machine account' ?</A
></DT
><DT
><A
HREF="#AEN165"
>"The machine account for this computer either does not exist or is not accessable."</A
></DT
><DT
><A
HREF="#AEN171"
>How do I create machine accounts manually ?</A
></DT
><DT
><A
HREF="#AEN184"
>I cannot include a '$' in a machine name.</A
></DT
><DT
><A
HREF="#AEN190"
>I get told "You already have a connection to the Domain...." when creating a
machine account.</A
></DT
><DT
><A
HREF="#AEN194"
>I get told "Cannot join domain, the credentials supplied conflict
with an existing set.."</A
></DT
><DT
><A
HREF="#AEN198"
>"The system can not log you on (C000019B)...."</A
></DT
></DL
></DD
></DL
></DD
><DT
>4. <A
HREF="#AEN202"
>User Account Management</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN204"
>Domain Admins</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN206"
>How do I configure an account as a domain administrator?</A
></DT
></DL
></DD
><DT
><A
HREF="#AEN210"
>Profiles</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN212"
>Why is it bad to set "logon path = \\%N\%U\profile" in smb.conf? ?</A
></DT
><DT
><A
HREF="#AEN226"
>Why are all the users listed in the "domain admin users" using the same profile?</A
></DT
><DT
><A
HREF="#AEN229"
>The roaming profiles do not seem to be updating on the server.</A
></DT
></DL
></DD
><DT
><A
HREF="#AEN237"
>Policies</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN239"
>What are 'Policies' ?.</A
></DT
><DT
><A
HREF="#AEN246"
>I can't get system policies to work.</A
></DT
><DT
><A
HREF="#AEN260"
>What about Windows NT Policy Editor ?</A
></DT
><DT
><A
HREF="#AEN274"
>Can Win95 do Policies ?</A
></DT
></DL
></DD
><DT
><A
HREF="#AEN280"
>Passwords</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN282"
>What is password sync and should I use it ?</A
></DT
><DT
><A
HREF="#AEN295"
>How do I get remote password (unix and SMB) changing working ?</A
></DT
></DL
></DD
></DL
></DD
><DT
>5. <A
HREF="#AEN301"
>Miscellaneous</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN303"
></A
></DT
><DD
><DL
><DT
><A
HREF="#AEN305"
>How do I get 'User Manager' and 'Server Manager'</A
></DT
><DT
><A
HREF="#AEN320"
>The time setting from a Samba server does not work.</A
></DT
><DT
><A
HREF="#AEN324"
>"trust account xxx should be in DOMAIN_GROUP_RID_USERS"</A
></DT
><DT
><A
HREF="#AEN328"
>How do I get my samba server to become a member ( not PDC ) of an NT domain?</A
></DT
></DL
></DD
></DL
></DD
><DT
>6. <A
HREF="#AEN363"
>Troubleshooting and Bug Reporting</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN365"
>Diagnostic tools</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN367"
>What are some diagnostics tools I can use to debug the domain logon process and where can I
find them?</A
></DT
><DT
><A
HREF="#AEN375"
>How do I install 'Network Monitor' on an NT Workstation or a Windows 9x box?</A
></DT
></DL
></DD
><DT
><A
HREF="#AEN404"
>What other help can I get ?</A
></DT
><DD
><DL
><DT
><A
HREF="#AEN407"
>URLs and similar</A
></DT
><DT
><A
HREF="#AEN453"
>How do I get help from the mailing lists ?</A
></DT
><DT
><A
HREF="#AEN482"
>How do I get off the mailing lists ?</A
></DT
></DL
></DD
></DL
></DD
></DL
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="AEN25"
>Chapter 1. Introduction</A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN27"
>State of Play</A
></H1
><P
><I
CLASS="EMPHASIS"
>It should be noted that 2.2.0 in its pre-release form still has a few problems,
I'll try and keep this section current while things are still dynamic.
At the time of this update (November 13, 2000) the current state of play is :</I
></P
><P
>Comments here about W2K joining the domain apply only to Samba 2.2 from the CVS after November 27th. The
'snapshot' release Samba2.2alpha1 does not work !!! See below on how to get a CVS tree.</P
><P
>Client Side creation of Machine accounts does work but is not complete.
Firstly, the <TT
CLASS="FILENAME"
>add user script</TT
> runs as the user who's
name was entered, not as root. Secondly, the machine name passed to the script (%U)
has an underscore at the end, not a '$'. One alternative is to use %m and add the $.
This method is documented in the <A
HREF="samba-pdc-howto.html"
TARGET="_top"
>HowTo</A
>.
And thirdly, it does not work with NT4ws.
</P
><P
>A W2K machine can join the domain. See the <A
HREF="samba-pdc-howto.html"
TARGET="_top"
>HowTo</A
>
which explains the process. The methods
described are 'work arounds' and should be regarded as temporary. Although I (drb)
have tested these procedures a number of people have had difficulty so there
may be other issues at work. JFM is aware of these
problems and will attend to them when he can.</P
><P
>A Domain Admin account is required and at present it appears that only root
is a suitable candidate.</P
><P
>Much of the related code does work. For example, if an NT is removed from the
domain and then rejoins, the <TT
CLASS="FILENAME"
>Create a Computer Account in the Domain</TT
> dialog
will let you reset the smbpasswd. That is you don't need to do it from
the unix box. However, at the present, you do need to have root as an
administrator and use the root user name and password.</P
><P
><I
CLASS="EMPHASIS"
>Actually I'm
not sure that last paragraph is correct ....</I
></P
><P
><B
CLASS="COMMAND"
>Policies</B
> do work on a W2K machine. MS says that recent builds of
W2K dont observe an NT policy but it appears it does in 'legacy' mode.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN44"
>Introduction</A
></H1
><P
>This FAQ was origionally compiled by Jerry Carter (gc) chiefly dealing with the 'old head'
version of Samba and its NTDomain facilities. It is being rewritten by David Bannon (drb)
so that it addresses more accurately the Samba 2.2 planned for release late 2000. </P
><P
>This document probably still contains some material that does not apply to
Samba 2.2 but most (all?) of the really misleading stuff has been removed. Some
issues are not dealt with or are dealt with badly. Please send corrections and additions to
David Bannon at D.Bannon@latrobe.edu.au</P
><P
>Hopefully, as we all become familiar with the Samba 2.2 as a PDC this document will
become much more usefull.</P
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="AEN49"
>Chapter 2. General Information</A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN51"
>What can we do ?</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN53"
>What can Samba Primary Domain Controller (PDC) do ?</A
></H2
><P
>If you wish to have Samba act as a PDC for Windows NT 3.51.and 4.0 or W2000 client, then you
will need to obtain the 2.2.0 version, currently in pre-release. Release of a stable,
full featured Samba PDC is currently slated for version 3.0. </P
><P
>The following is a list of included features currently in Samba 2.2:</P
><P
></P
><UL
><LI
><P
>The ability to act as a limited PDC for Windows NT and W2000 clients.
This includes adding NT and W2K machines to the domain and authenticating users logging
into the domain.</P
></LI
><LI
><P
>Domain account can be viewed using the User Manager for
Domains ????</P
></LI
><LI
><P
>Viewing resources on the Samba PDC via the Server Manager for Domains
from the NT client. ??</P
></LI
><LI
><P
>Windows 95 clients will allow user level security to be set
but will not currently allow browsing of accounts.</P
></LI
><LI
><P
>Machine account password updates.</P
></LI
><LI
><P
>Changing of user passwords from an NT client.</P
></LI
><LI
><P
>Partial support for Windows NT group and username mapping.</P
></LI
><LI
><P
>Support for a LDAP password database backend.</P
></LI
><LI
><P
>Printing.</P
></LI
></UL
><P
></P
><P
><B
>These things are note expected to work in the forseeable future</B
></P
><UL
><LI
><P
>Trust relationships</P
></LI
><LI
><P
>PDC and BDC integration</P
></LI
><LI
><P
>Windows NT ACLs (on the Samba shares)</P
></LI
><LI
><P
>Offer a list of domain users to User Manager for Domains
(or the Security Tab etc).</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN86"
>Can I have a Windows 2000 client logon to a Samba controlled domain?</A
></H2
><P
>The 2.2 release branch of Samba supports Windows 2000 domain
clients in legacy mode, ie as if the PDC is a NTServer, not a
W2K server.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN89"
>What's the status of print spool (spoolss) support in the NTDOM code?</A
></H2
><P
>The implementation of support for SPOOLSS pipe is complete and it will be available
in the 2.2.0 release. This means that Samba will support the automatic downloading of printer
drivers for Windows NT clients just as it currently does for Windows 9x clients.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN92"
>CVS</A
></H1
><P
>CVS is a programme (publically available) that the Samba developers use to
maintain the central source code. Non developers can get access to the source in
a read only capacity. Many flavours of unix now arrive with cvs installed.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN95"
>What are the different Samba branches available in CVS ?</A
></H2
><P
>You can find out more about obtaining Samba's via
anonymous CVS from
<A
HREF="http://pserver.samba.org/samba/cvs.html"
TARGET="_top"
> http://pserver.samba.org/samba/cvs.html"</A
>. </P
><P
></P
><DIV
CLASS="VARIABLELIST"
><P
><B
>There are basically four branches to watch at the moment :</B
></P
><DL
><DT
>HEAD</DT
><DD
><P
>Samba 3.0 ? This code boasts all the main development
work in Samba. Two things that most people are not aware of
which live in the HEAD branch code are winbind NSS module and
Tim Potter's VFS implementation. Due to its developmental
nature, its not really suitable for production work.
</P
></DD
><DT
>SAMBA_2_0</DT
><DD
><P
>This branch contains the current stable release release.
At the moment it contains 2.0.7, a version that will do some
limited PDC stuff. If you are really going to do PDC things then
I (drb) suggest that you consider 2.2 instead.
</P
></DD
><DT
>SAMBA_2_2</DT
><DD
><P
>The next stable release, currently in a 'alpha' form.
It provides the Samba developers, testers and interested
people with an approximation of what is to come. This document
addresses only SAMBA_2_2.
</P
></DD
><DT
>SAMBA_TNG</DT
><DD
><P
>This branch is no longer maintained from the Samba sites.
Please see <A
HREF="http://www.samba-tng.org/"
TARGET="_top"
> http://www.samba-tng.org/</A
>. It has been requested
that questions about TNG are not posted to the regular Samba mailing
lists including samba-ntdom and samba-technical.
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN118"
>What are the CVS commands ?</A
></H2
><P
>See <A
HREF="http://pserver.samba.org/samba/cvs.html"
TARGET="_top"
> http://pserver.samba.org/samba/cvs.html</A
></P
><P
></P
><P
><B
>To get the Samba 2.2 version, tag SAMBA_2_2 you would do :</B
></P
><UL
><LI
><P
> For example : <B
CLASS="COMMAND"
>cd /usr/local/src/</B
></P
></LI
><LI
><P
> <B
CLASS="COMMAND"
>cvs -d :pserver:cvs@pserver.samba.org:/cvsroot
login</B
></P
></LI
><LI
><P
> When prompted enter a password of <B
CLASS="COMMAND"
>cvs</B
></P
></LI
><LI
><P
> <B
CLASS="COMMAND"
>cvs -d :pserver:cvs@pserver.samba.org:/cvsroot
co -r SAMBA_2_2 samba</B
></P
></LI
></UL
><P
></P
><P
><B
>Then to update that directory at some later time,</B
></P
><UL
><LI
><P
> <B
CLASS="COMMAND"
>cd /usr/local/src/samba</B
></P
></LI
><LI
><P
> <B
CLASS="COMMAND"
>cvs -d :pserver:cvs@pserver.samba.org:/cvsroot login</B
></P
></LI
><LI
><P
> When prompted enter a password of 'cvs'.</P
></LI
><LI
><P
> <B
CLASS="COMMAND"
>cvs update -d -P</B
></P
></LI
></UL
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="AEN149"
>Chapter 3. Establishing Connections</A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN151"
></A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN153"
>How do I get my NT4 or W2000 Workstation to login to the Samba controlled Domain?</A
></H2
><P
>There is a comprehensive Samba PDC <A
HREF="samba-pdc-howto.html"
TARGET="_top"
>HowTo</A
>
accessable from the samba web site
under 'Documentation'. Its currently located at <A
HREF="http://bioserve.latrobe.edu.au/samba"
TARGET="_top"
> http://bioserve.latrobe.edu.au/samba</A
>. Read it.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN158"
>What is a 'machine account' ?</A
></H2
><P
>Every NT, W2K or Samba machine that joins a Samba controlled domain must be known to
the Samba PDC. There are two entries required, one in (typically) <TT
CLASS="FILENAME"
>/etc/passwd</TT
>
and the other in (typically) <TT
CLASS="FILENAME"
>/usr/local/samba/private/smbpasswd</TT
>. Under
some circumstances these entries are made <A
HREF="#AEN171"
>manually</A
>, the
<A
HREF="samba-pdc-howto.html"
TARGET="_top"
>HowTo</A
> discusses ways of creating them automatically.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN165"
>"The machine account for this computer either does not exist or is not accessable."</A
></H2
><P
>When I try to join the domain I get the message "The machine account for this computer
either does not exist or is not accessable". Whats wrong ?</P
><P
>This problem is caused by the PDC not having a suitable machine account.
If you are using the <B
CLASS="COMMAND"
>add user script =</B
> method to create accounts
then this would indicate that it has not worked. Ensure the domain admin user
system is working.</P
><P
>Alternatively if you are creating account entries manually then they have not been created
correctly. Make sure that you have the entry correct for the machine account in smbpasswd
file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd utility,
make sure that the account name is the machine netbios name with a '$' appended to it
( ie. computer_name$ ). There must be an entry in both /etc/passwd and
the smbpasswd file. Some people have reported that
inconsistent subnet masks between the Samba server and the NT client have caused this problem.
Make sure that these are consistent for both client and server.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN171"
>How do I create machine accounts manually ?</A
></H2
><P
>This was the only option until recently, now in version 2.2 better means are available.
You might still need to do it manually for a couple of reasons. A machine account
consists of two entries (assuming a standard install and /etc/passwd use),
one in /etc/passwd and the other in /usr/local/samba/private/smbpasswd. The /etc/passwd
entry will list the machine name with a $ appended, won't have a passwd, will have a null
shell and no home directory. For example a machine called 'doppy' would have an /etc/passwd
entry like this :</P
><P
><B
CLASS="COMMAND"
>doppy$:x:505:501:NTMachine:/dev/null:/bin/false</B
></P
><P
>On a linux system for example, you would typically add it like this :</P
><P
><B
CLASS="COMMAND"
>adduser -g machines -c NTMachine -d /dev/null -s /bin/false -n
doppy$</B
></P
><P
>Then you need to add that entry to smbpasswd, assuming you have a suitable
path to the <B
CLASS="COMMAND"
>smbpasswd</B
> programme, do this :</P
><P
><B
CLASS="COMMAND"
>smbpasswd -a -m doppy$</B
></P
><P
>The entry will be created with a well known password, so any machine that
says its doppy could join the domain as long as it gets in first. So don't create
the accounts any earlier than you need them.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN184"
>I cannot include a '$' in a machine name.</A
></H2
><P
>A 'machine name' in (typically) <TT
CLASS="FILENAME"
>/etc/passwd</TT
> consists
of the machine name with a '$' appended. FreeBSD (and other BSD systems ?)
won't create a user with a '$' in their name.</P
><P
>The problem is only in the program used to make the entry, once made, it works
perfectly. So create a user without the '$' and use <B
CLASS="COMMAND"
>vipw</B
> to edit
the entry, adding the '$'. Or create the whole entry with vipw if you like,
make sure you use a unique uid !</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN190"
>I get told "You already have a connection to the Domain...." when creating a
machine account.</A
></H2
><P
>This happens if you try to create a machine account from the machine itself
and use a user name that does not work (for whatever reason) and then try
another (possibly valid) user name.
Exit out of the network applet to close the initial connection and try again.</P
><P
>Further, if the machine is a already a 'member of a workgroup' that is the
same name as the domain you are joining (bad idea) you will get this message.
Change the workgroup name to something else, it does not matter what, reboot,
and try again.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN194"
>I get told "Cannot join domain, the credentials supplied conflict
with an existing set.."</A
></H2
><P
>This is the same basic problem as mentioned above, <A
HREF="#AEN190"
> "You already have a connection..."</A
></P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN198"
>"The system can not log you on (C000019B)...."</A
></H2
><P
>I joined the domain successfully but after upgrading to a newer version of the
Samba code I get the message, "The system can not log you on (C000019B), Please try a
gain or consult your system administrator" when attempting to logon.</P
><P
>This occurs when the domain SID stored in private/WORKGROUP.SID is changed.
For example, you remove the file and smbd automatically creates a new one.
Or you are swapping back and forth between versions 2.0.7, TNG and the HEAD branch
code (not recommended). The only way to correct the problem is to restore the
original domain SID or remove the domain client from the domain and rejoin.</P
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="AEN202"
>Chapter 4. User Account Management</A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN204"
>Domain Admins</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN206"
>How do I configure an account as a domain administrator?</A
></H2
><P
>See the NTDom <A
HREF="samba-pdc-howto.html"
TARGET="_top"
>HowTo</A
>.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN210"
>Profiles</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN212"
>Why is it bad to set "logon path = \\%N\%U\profile" in smb.conf? ?</A
></H2
><P
>Sometimes Windows clients will maintain a connection to the \\homes\ ( or [%U] ) share
even after the user has logged out. Consider the following scenario.</P
><P
></P
><UL
><LI
><P
> user1 logs into the Windows NT machine. Therefore the
[homes] share is set to \\server\user1.</P
></LI
><LI
><P
> user1 works for a while and then logs out. </P
></LI
><LI
><P
> user2 logs into the same Windows NT machine.</P
></LI
></UL
><P
>However, since the NT box has maintained a connection to [homes] which was
previously set to \\server\user1, when the operating system attempts to
get the profile and if it can read users1's profile, will get it otherwise it
will return an error. You get the picture.</P
><P
>A better solution is to use a separate [profiles] share and set the
"logon path = \\%N\profiles\%U" </P
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
>Is this still a problem ????</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN226"
>Why are all the users listed in the "domain admin users" using the same profile?</A
></H2
><P
>You are using a very very old development version of Samba. Upgrade.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN229"
>The roaming profiles do not seem to be updating on the server.</A
></H2
><P
>There can be several reasons for this.</P
><P
>Make sure that the time on the client and the PDC are synchronized. You can accomplish
this by executing a <B
CLASS="COMMAND"
>net time \\server /set /yes</B
> replacing server with the
name of your PDC (or another synchronized SMB server). See <A
HREF="#AEN320"
> about Setting Time</A
></P
><P
>Make sure that the
logon path is writeable by the user and make sure that the connection to the logon
path location is by the current user. Sometimes Windows client do not drop the
connection immediately upon logoff.</P
><P
>Some people have reported that the logon path location should also be browseable.
I (GC) have yet to emperically verify this, but you can try.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN237"
>Policies</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN239"
>What are 'Policies' ?.</A
></H2
><P
>When a user logs onto the domain via a client machine, the PDC sends
the client machine a list of things contained in the 'policy' (if it exists).
This list may do things like suppress a splach screen, format the dates the way you
like them or perhaps remove locally stored profiles.</P
><P
>On a samba PDC this list is obtained from a file called <B
CLASS="COMMAND"
>ntconfig.pol</B
>
and located in the <B
CLASS="COMMAND"
>[netlogon]</B
>share. The file is created with a policy editor
and must be readable by anyone and writeable by only root. See <A
HREF="#AEN260"
> below</A
> for how to get a suitable editor.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN246"
>I can't get system policies to work.</A
></H2
><P
>There are two possible reasons for system policies not functioning correctly.
Make sure that you have the following parameters set in smb.conf </P
><PRE
CLASS="PROGRAMLISTING"
> [netlogon]
....
locking = no
public = no
browseable = yes
....
</PRE
><P
>A policy file must be in the <B
CLASS="COMMAND"
>[netlogon]</B
> share and must be
readable by everyone and writeable by only root. The file must be created
by an NTServer <A
HREF="#AEN260"
>Policy Editor</A
>.</P
><P
>Last time I (drb) looked in the source, it was
looking for <TT
CLASS="FILENAME"
>ntconfig.pol</TT
> first then several other combinations of upper
and lower case. People have reported success using <TT
CLASS="FILENAME"
>NTconfig.pol</TT
>,
<TT
CLASS="FILENAME"
>NTconfig.POL</TT
> and <TT
CLASS="FILENAME"
>ntconfig.pol</TT
>. These are the case
settings that I (GC) use with the
filename <TT
CLASS="FILENAME"
>ntconfig.pol</TT
></P
><PRE
CLASS="PROGRAMLISTING"
> case sensitive = no
case preserve = yes
default case = yes
</PRE
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN260"
>What about Windows NT Policy Editor ?</A
></H2
><P
>To create or edit <B
CLASS="COMMAND"
>ntconfig.pol</B
> you must use the NT Server
Policy Editor, <B
CLASS="COMMAND"
>poledit.exe</B
> which is included with NT Server
but <I
CLASS="EMPHASIS"
>not NT Workstation</I
>. There is a Policy Editor on a NTws
but it is not suitable for creating <I
CLASS="EMPHASIS"
>Domain Policies</I
>.
Further, although the Windows 95
Policy Editor can be installed on an NT Workstation/Server, it will not
work with NT policies because the registry key that are set by the policy templates.
However, the files from the NT Server will run happily enough on an NTws.
You need <TT
CLASS="FILENAME"
>poledit.exe, common.adm</TT
> and <TT
CLASS="FILENAME"
>winnt.adm</TT
>. It is convenient
to put the two *.adm files in <TT
CLASS="FILENAME"
>c:\winnt\inf</TT
> which is where
the binary will look for them unless told otherwise. Note also that that
directory is 'hidden'.</P
><P
>The Windows NT policy editor is also included with the
Service Pack 3 (and later) for Windows NT 4.0. Extract the files using
<B
CLASS="COMMAND"
>servicepackname /x</B
>, ie thats <B
CLASS="COMMAND"
>Nt4sp6ai.exe /x</B
>
for service pack 6a.
The policy editor, <B
CLASS="COMMAND"
>poledt.exe</B
> and the associated template files (*.adm) should
be extracted as well. It is also possible to downloaded the policy template
files for Office97 and get a copy of the policy editor. Another possible
location is with the Zero Administration Kit available for download from Microsoft.
</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN274"
>Can Win95 do Policies ?</A
></H2
><P
>Install the group policy handler for Win9x to pick up group policies.
Look on the Win98 CD in <TT
CLASS="FILENAME"
> \tools\reskit\netadmin\poledit</TT
>. Install group policies on a Win9x client by double-clicking
<TT
CLASS="FILENAME"
>grouppol.inf</TT
>. Log off and on again a couple of times and see if
Win98 picks up group policies.
Unfortunately this needs to be done on every Win9x machine that uses group policies....</P
><P
>If group policies don't work one reports suggests getting the updated (read: working)
grouppol.dll for Windows 9x. The group list is grabbed from /etc/group.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN280"
>Passwords</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN282"
>What is password sync and should I use it ?</A
></H2
><P
>NTws users can change their domain password by pressing Ctrl-Alt-Del and
choosing 'Change Password'. By default however, this does not change the unix password
(typically in <TT
CLASS="FILENAME"
>/etc/passwd or /etc/shadow</TT
>). In lots of situations
thats OK, for example :</P
><P
></P
><UL
><LI
><P
>The server is only accessible to the user via samba.</P
></LI
><LI
><P
>Pam_smb or similar is installed so other applications
still refer to the samba password.</P
></LI
></UL
><P
>But sometimes you really do need to maintain two seperate password databases and
there are good reasons to keep then in sync. Trying to explain to users
that they need to change their passwords in two seperate places or use
two seperate passwords is not fun.</P
><P
>However do understand that setting up password sync is not without problems either.
The chief difficulty is the interface between Samba and the <B
CLASS="COMMAND"
>passwd</B
> command,
it can be a fiddle to set up and if the password the user has entered fails,
the resulting errors are ambiguously reported
and the user is confused. Further, you need to take steps to ensure that users
only ever change their passwords via samba (or use <B
CLASS="COMMAND"
>smbpasswd</B
>),
otherwise they will only be changing the unix password.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN295"
>How do I get remote password (unix and SMB) changing working ?</A
></H2
><P
>Have a practice changing a user's password (as root) to see what
discussion takes place and change the text in the 'passwd chat' line below as necessary. The
line as shown works for recent RH Linux but most other systems seem to like to do something
different. The '*' is a wild card and will match anything (or nothing).
</P
><P
>Add these lines to smb.conf under [Global]</P
><PRE
CLASS="PROGRAMLISTING"
>
unix password sync = true
passwd program = /usr/bin/passwd %u
passwd chat = *password* %n\n *password* %n\n *successful*
</PRE
><P
>As mentioned above, the change to the unix password
happens as root, not as the user, as is indicated in ~/smbd/chgpasswd.c If
you are using NIS, the Samba server must be running on the NIS master machine.</P
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="AEN301"
>Chapter 5. Miscellaneous</A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN303"
></A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN305"
>How do I get 'User Manager' and 'Server Manager'</A
></H2
><P
>Since I don't need to buy an NT Server CD now, how do I get the 'User Manager for
Domains', the 'Server Manager' ?</P
><P
></P
><P
><B
>Microsoft distributes a version of these tools called nexus
for installation on Windows 95 systems. The tools set includes</B
></P
><UL
><LI
><P
>Server Manager</P
></LI
><LI
><P
>User Manager for Domains</P
></LI
><LI
><P
>Event Viewer</P
></LI
></UL
><P
>Click here to download the archived file
<A
HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
TARGET="_top"
> ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
></P
><P
>The Windows NT 4.0 version of the 'User Manager for Domains'
and 'Server Manager' are available from Microsoft via ftp from
<A
HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
TARGET="_top"
> ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
></P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN320"
>The time setting from a Samba server does not work.</A
></H2
><P
>If it works OK when you log on as Domain Admin then the problem is that ordinary users
don't have permission to change the time. (The system is running with their permission
at logon time.) This is not a Samba problem, you will have the same problem where ever
you connect. You can give 'everyone' permission to change the time from the User Manager.
</P
><P
>Anyone know what the registry settings are so this could be done with a Policy ?</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN324"
>"trust account xxx should be in DOMAIN_GROUP_RID_USERS"</A
></H2
><P
>I keep getting the message "trust account xxx should be in DOMAIN_GROUP_RID_USERS."
in the logs. What do I need to do?</P
><P
>You are using one of the old development versions. Upgrade.
(The message is unimportant, was a reminder to a developer)</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN328"
>How do I get my samba server to become a member ( not PDC ) of an NT domain?</A
></H2
><P
>In a domain that has a number of servers you only need one password database.
The machines that don't have their own ask the PDC to check for them.
This will work fine for a domain controlled by either a Samba or NT machine.
The following lines in smb.conf are typical, 'password server' points to the
samba machine (or an NT) that has the password list : </P
><PRE
CLASS="PROGRAMLISTING"
>
[global]
...
security = domain
workgroup = { Put your domain name here }
password server = { Put the ip of the PDC here }
encrypt passwords = yes
...
</PRE
><P
>The samba server in question will have to 'join the domain', that requires
the domain controller to have a machine account for it. This is no different
to the machine account requirements to allow a NTws to join the domain. For
example, if we want a unix box called <I
CLASS="EMPHASIS"
>sleepy</I
> to ask the PDC called <I
CLASS="EMPHASIS"
>grumpy</I
>
to do its authentication then <I
CLASS="EMPHASIS"
>grumpy</I
> will need an entry in its smbpasswd
(assuming it's also samba) that starts with <I
CLASS="EMPHASIS"
>sleepy$</I
>. It would have to be
created <A
HREF="#AEN171"
>manually</A
>. </P
><P
>If the domain is controlled by an NTServer then the "Server Manager for Domains"
tool must be used to add 'sleepy' to the domain list.</P
><P
>In either case we then join the domain. If the domain is called <I
CLASS="EMPHASIS"
>forest</I
>
then on sleepy we would join the domain by typing :</P
><P
><B
CLASS="COMMAND"
>smbpasswd -j forest</B
></P
><P
>Note that the directory where the smbpasswd file would be
located should exist as this is where smbd will generate the MACHINE.SID file. This
might be <TT
CLASS="FILENAME"
>/usr/local/samba/private/FOREST.SLEEPY.SID</TT
> and
it contains the trust account password for the domain member. The permissions are
(and should remain) "rw-------</P
><P
>Note the Samba Servers without the password list will most likely still need an account
for each user, this means a line in its <TT
CLASS="FILENAME"
>/etc/passwd</TT
>. Because authentication
is being handled at the domain level the
<TT
CLASS="FILENAME"
>/etc/passwd</TT
> line does not need a password.
If the shares being offered are not user specific, ie a common (read only ?)
area or perhaps just printing then the user's
<TT
CLASS="FILENAME"
>/etc/passwd</TT
> does not need a home directory. A typical
line in <TT
CLASS="FILENAME"
>/etc/passwd</TT
> for a server that allows domain users to
connect to the samba shares but does not offer a home share ('cos that's on the PDC)
and does not allow logon to the unix prompt would be like this :</P
><PRE
CLASS="PROGRAMLISTING"
>jblow:x:542:100:Joe Blow:/dev/null:/bin/false</PRE
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
></P
><UL
><LI
><P
>When removing those 'dummy' users, watch the 'remove user' scripts,
some OS think they should remove a users directory even when its not owned by the user !
</P
></LI
><LI
><P
>The <TT
CLASS="FILENAME"
>username map = </TT
> parameter might help you to avoid having
all those accounts created.</P
></LI
><LI
><P
>You should investigate the smb.conf parameter
<TT
CLASS="FILENAME"
>'add user script'</TT
>, it will be used to create accounts on
secondary servers when that account already exists on the PDC. Very nice.
Something like :</P
><PRE
CLASS="PROGRAMLISTING"
> [Global]
....
add user script = /usr/sbin/adduser -n -g users -c User -d /dev/null -s /bin/false %U
....
</PRE
></LI
></UL
></BLOCKQUOTE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="AEN363"
>Chapter 6. Troubleshooting and Bug Reporting</A
></H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN365"
>Diagnostic tools</A
></H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN367"
>What are some diagnostics tools I can use to debug the domain logon process and where can I
find them?</A
></H2
><P
>One of the best diagnostic tools for debugging problems is Samba itself. You can use the -d
option for both smbd and nmbd to specifiy what 'debug level' at which to run. See the man
pages on smbd, nmbd and smb.conf for more information on debugging options. The debug
level can range from 1 (the default) to around 100 but a debug level of about 20 will
normally help you find any errors that samba is encountering. Another helpful method
of debugging is to compile samba using the gcc -g flag. This will include debug
information in the binaries and allow you to attch gdb to the running smbd / nmbd
process. In order to attach gdb to an smbd process for an NT workstation, first
get the workstation to make the connection. Pressing ctrl-alt-delete and going down
to the domain box is sufficient (at least, on the first time you join the domain) to
generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation maintains an open
connection, and therefore there will be an smbd process running (assuming that you
haven't set a really short smbd idle timeout) So, in between pressing ctrl alt
delete, and actually typing in your password, you can gdb attach and continue.</P
><P
>An SMB enabled version of tcpdump is available from
<A
HREF="ftp://samba.org/pub/samba/tcpdump-smb/"
TARGET="_top"
>ftp://samba.org/pub/samba/tcpdump-smb/
</A
></P
><P
>Capconvert is a small C program for translating output from tcpdump-smb to CAP format
that can be read by netmon. You will need to use the raw output from tcp dump
( ie. <B
CLASS="COMMAND"
>tcpdump -w output.dump</B
> ). Good news! Now you can convert
Solaris' snoop output as well. The C source code for snoop2cap is available for download.
</P
><P
>For tracing things on the Microsoft Windows NT, Network Monitor (aka. netmon) is available
on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's.
The version of netmon that ships with SMS allows for dumping packets between any two
computers (ie. placing the network interface in promiscuous mode). The version
on the NT Server install CD will only allow monitoring of network traffic directed to the
local NT box and broadcasts on the local subnet.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN375"
>How do I install 'Network Monitor' on an NT Workstation or a Windows 9x box?</A
></H2
><P
>Installing netmon on an NT workstation requires a couple of steps. The following
are for installing Netmon V4.00.349, which comes with Microsoft Windows NT Server
4.0, on Microsoft Windows NT Workstation 4.0. The process should be similar
for other version of Windows NT / Netmon. You will need both the Microsoft Windows
NT Server 4.0 Install CD and the Workstation 4.0 Install CD.</P
><P
>Initially you will need to install 'Network Monitor Tools and Agent' on the
NT Server. To do this </P
><P
></P
><UL
><LI
><P
>Goto Start - Settings - Control Panel - Network - Services - Add </P
></LI
><LI
><P
>Select the 'Network Monitor Tools and Agent' and click on 'OK'.</P
></LI
><LI
><P
>Click 'OK' on the Network Control Panel.</P
></LI
><LI
><P
>Insert the Windows NT Server 4.0 install CD when prompted.</P
></LI
></UL
><P
>At this point the Netmon files should exist in <TT
CLASS="FILENAME"
>%SYSTEMROOT%\System32\netmon\*.*</TT
>.
Two subdirectories exist as well, <TT
CLASS="FILENAME"
>parsers\</TT
> which contains the necessary DLL's
for parsing the netmon packet dump, and <TT
CLASS="FILENAME"
>captures\</TT
>.</P
><P
>In order to install the Netmon tools on an NT Workstation, you will first need to
install the 'Network Monitor Agent' from the Workstation install CD.</P
><P
></P
><UL
><LI
><P
>Goto Start - Settings - Control Panel - Network - Services - Add</P
></LI
><LI
><P
>Select the 'Network Monitor Agent' and click on 'OK'.</P
></LI
><LI
><P
>Click 'OK' on the Network Control Panel.</P
></LI
><LI
><P
>Insert the Windows NT Workstation 4.0 install CD when prompted.</P
></LI
></UL
><P
>Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* to
%SYSTEMROOT%\System32\netmon\*.* on the Workstation and set permissions as
you deem appropriate for your site. You will need administrative rights on the
NT box to run netmon.</P
><P
>To install Netmon on a Windows 9x box install the network monitor agent from
the Windows 9x CD (\admin\nettools\netmon).
There is a readme file located with the netmon driver files on the CD if you need
information on how to do this. Copy the files from a working Netmon installation.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN404"
>What other help can I get ?</A
></H1
><P
>There are many sources of information available in the form of mailing lists, RFC's
and documentation. The docs that come with the samba distribution contain very
good explanations of general SMB topics such as browsing.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN407"
>URLs and similar</A
></H2
><P
></P
><UL
><LI
><P
>Home of Samba site <A
HREF="http://samba.org"
TARGET="_top"
> http://samba.org</A
>. We have a mirror near you !</P
></LI
><LI
><P
> The <I
CLASS="EMPHASIS"
>Development</I
> document
on the Samba mirrors might mention your problem. If so,
it might mean that the developers are working on it.</P
></LI
><LI
><P
> Ignacio Coupeau has a very comprehesive look at LDAP with Samba at
<A
HREF="http://www.unav.es/cti/ldap-smb-howto.html"
TARGET="_top"
> http://www.unav.es/cti/ldap-smb-howto.html</A
>
Be a little carefull however, I suspect that it does not specificly
address samba 2.2.x. The HEAD pre-2.1 may possibly be the best
stream to look at.</P
></LI
><LI
><P
> Lars Kneschke's site covers <A
HREF="http://www.samba-tng.org"
TARGET="_top"
> Samba-TNG</A
> at
<A
HREF="http://www.kneschke.de/projekte/samba_tng"
TARGET="_top"
> http://www.kneschke.de/projekte/samba_tng</A
>, but again, a
lot of it does not apply to the main stream Samba.</P
></LI
><LI
><P
>Although 2.0.7 has almost had its day as a PDC, I (drb) will
keep the 2.0.7 PDC pages at <A
HREF="http://bioserve.latrobe.edu.au/samba"
TARGET="_top"
> http://bioserve.latrobe.edu.au/samba</A
> going for a while yet.</P
></LI
><LI
><P
>Misc links to CIFS information
<A
HREF="http://samba.org/cifs/"
TARGET="_top"
>http://samba.org/cifs/</A
></P
></LI
><LI
><P
>NT Domains for Unix <A
HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
TARGET="_top"
> http://mailhost.cb1.com/~lkcl/ntdom/</A
></P
></LI
><LI
><P
>FTP site for older SMB specs:
<A
HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
TARGET="_top"
> ftp://ftp.microsoft.com/developr/drg/CIFS/</A
></P
></LI
></UL
><P
></P
><P
><B
>There are a number of documents that no longer appear to live at their
origional home. Any one know where the following may be found ?</B
></P
><UL
><LI
><P
>CIFS/E Browser Protocol draft-leach-cifs-browser-spec-00.txt</P
></LI
><LI
><P
>CIFS Remote Administration Protocol draft-leach-cifs-rap-spec-00.txt</P
></LI
><LI
><P
>CIFS Logon and Pass Through Authentication draft-leach-cifs-logon-spec-00.txt</P
></LI
><LI
><P
>A Common Internet File System (CIFS/1.0) Protocol draft-leach-cifs-v1-spec-01.txt</P
></LI
><LI
><P
>CIFS Printing Specification draft-leach-cifs-print-spec-00.txt</P
></LI
><LI
><P
>RFC1001 (March '87) Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and methods.
http://ds.internic.net/rfc/rfc1001.txt </P
></LI
><LI
><P
>RFC1002 (March '87) Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed specifications.
http://ds.internic.net/rfc/rfc1002.txt </P
></LI
><LI
><P
>Microsoft's main CIFS page: http://www.microsoft.com/workshop/networking/cifs/</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN453"
>How do I get help from the mailing lists ?</A
></H2
><P
> There are a number of Samba related mailing lists. Go to <A
HREF="http://samba.org"
TARGET="_top"
>http://samba.org</A
>, click on your nearest mirror
and then click on <B
CLASS="COMMAND"
>Support</B
> and then click on <B
CLASS="COMMAND"
> Samba related mailing lists</B
>.</P
><P
>For questions relating to Samba TNG go to
<A
HREF="http://www.samba-tng.org/"
TARGET="_top"
>http://www.samba-tng.org/</A
>
It has been requested that you don't post questions about Samba-TNG to the
main stream Samba lists.</P
><P
></P
><P
><B
>If you post a message to one of the lists please
observe the following guide lines :</B
></P
><UL
><LI
><P
> Always remember that the developers are volunteers, they are
not paid and they never guarantee to produce a particular feature at
a particular time. Any time lines are 'best guess' and nothing more.
</P
></LI
><LI
><P
> Always mention what version of samba you are using and what
operating system its running under. You should probably list the
relevant sections of your smb.conf file, at least the options
in [global] that affect PDC support.</P
></LI
><LI
><P
>In addition to the version, if you obtained Samba via
CVS mention the date when you last checked it out.</P
></LI
><LI
><P
> Try and make your question clear and brief, lots of long,
convoluted questions get deleted before they are completely read !
Don't post html encoded messages (if you can select colour or font
size its html).</P
></LI
><LI
><P
> If you run one of those niffy 'I'm on holidays' things when
you are away, make sure its configured to not answer mailing lists.
</P
></LI
><LI
><P
> Don't cross post. Work out which is the best list to post to
and see what happens, ie don't post to both samba-ntdom and samba-technical.
Many people active on the lists subscribe to more
than one list and get annoyed to see the same message two or more times.
Often someone will see a message and thinking it would be better dealt
with on another, will forward it on for you.</P
></LI
><LI
><P
>You might include <I
CLASS="EMPHASIS"
>partial</I
>
log files written at a debug level set to as much as 20.
Please don't send the entire log but enough to give the context of the
error messages.</P
></LI
><LI
><P
>(Possibly) If you have a complete netmon trace ( from the opening of
the pipe to the error ) you can send the *.CAP file as well.</P
></LI
><LI
><P
>Please think carefully before attaching a document to an email.
Consider pasting the relevant parts into the body of the message. The samba
mailing lists go to a huge number of people, do they all need a copy of your
smb.conf in their attach directory ?</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN482"
>How do I get off the mailing lists ?</A
></H2
><P
>To have your name removed from a samba mailing list, go to the
same place you went to to get on it. Go to <A
HREF="http://samba.org"
TARGET="_top"
>http://samba.org</A
>, click on your nearest mirror
and then click on <B
CLASS="COMMAND"
>Support</B
> and then click on <B
CLASS="COMMAND"
> Samba related mailing lists</B
>. Or perhaps see
<A
HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
TARGET="_top"
>here</A
></P
><P
>Please don't post messages to the list asking to be removed, you will just
be refered to the above address (unless that process failed in some way...)
</P
></DIV
></DIV
></DIV
></DIV
></BODY
></HTML
>
|
