docs/htmldocs/samba-pdc-faq.html

   1 <HTML
   2 ><HEAD
   3 ><TITLE
   4 >The Samba 2.2 PDC FAQ</TITLE
   5 ><META
   6 NAME="GENERATOR"
   7 CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
   8 ><BODY
   9 CLASS="BOOK"
  10 BGCOLOR="#FFFFFF"
  11 TEXT="#000000"
  12 LINK="#0000FF"
  13 VLINK="#840084"
  14 ALINK="#0000FF"
  15 ><DIV
  16 CLASS="BOOK"
  17 ><A
  18 NAME="SAMBA-PDC-FAQ"
  19 ></A
  20 ><DIV
  21 CLASS="TITLEPAGE"
  22 ><H1
  23 CLASS="TITLE"
  24 ><A
  25 NAME="SAMBA-PDC-FAQ"
  26 >The Samba 2.2 PDC FAQ</A
  27 ></H1
  28 ><H3
  29 CLASS="AUTHOR"
  30 ><A
  31 NAME="AEN4"
  32 >David Bannon</A
  33 ></H3
  34 ><DIV
  35 CLASS="AFFILIATION"
  36 ><SPAN
  37 CLASS="ORGNAME"
  38 >La Trobe University<BR></SPAN
  39 ></DIV
  40 ><HR></DIV
  41 ><HR><H1
  42 ><A
  43 NAME="AEN12"
  44 ></A
  45 ></H1
  46 ><P
  47 >Comments, corrections and additions to <TT
  48 CLASS="EMAIL"
  49 >&#60;<A
  50 HREF="mailto:D.Bannon@latrobe.edu.au"
  51 >D.Bannon@latrobe.edu.au</A
  52 >&#62;</TT
  53 ></P
  54 ><P
  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
  60 ><P
  61 >Please note it does not apply to Samba2.2alpha0, Samba2.2alpha1, Samba 2.0.7, TNG nor HEAD branch.
  62     </P
  63 ><P
  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
  65 ><P
  66 >       Also available is a Samba 2.2 PDC <A
  67 HREF="samba-pdc-howto.html"
  68 TARGET="_top"
  69 >HowTo</A
  70 > that takes you, step
  71     by step, over the process of setting up a very basic Samba 2.2 Primary Domain Controller
  72     </P
  73 ><DIV
  74 CLASS="NOTE"
  75 ><BLOCKQUOTE
  76 CLASS="NOTE"
  77 ><P
  78 ><B
  79 >Note: </B
  80 >Please read the Introduction for the current <A
  81 HREF="#AEN27"
  82 > state of play</A
  83 >.</P
  84 ></BLOCKQUOTE
  85 ></DIV
  86 ><DIV
  87 CLASS="TOC"
  88 ><DL
  89 ><DT
  90 ><B
  91 >Table of Contents</B
  92 ></DT
  93 ><DT
  94 >1. <A
  95 HREF="#AEN25"
  96 >Introduction</A
  97 ></DT
  98 ><DD
  99 ><DL
 100 ><DT
 101 ><A
 102 HREF="#AEN27"
 103 >State of Play</A
 104 ></DT
 105 ><DT
 106 ><A
 107 HREF="#AEN44"
 108 >Introduction</A
 109 ></DT
 110 ></DL
 111 ></DD
 112 ><DT
 113 >2. <A
 114 HREF="#AEN49"
 115 >General Information</A
 116 ></DT
 117 ><DD
 118 ><DL
 119 ><DT
 120 ><A
 121 HREF="#AEN51"
 122 >What can we do ?</A
 123 ></DT
 124 ><DD
 125 ><DL
 126 ><DT
 127 ><A
 128 HREF="#AEN53"
 129 >What can Samba Primary Domain Controller (PDC) do ?</A
 130 ></DT
 131 ><DT
 132 ><A
 133 HREF="#AEN86"
 134 >Can I have a Windows 2000 client logon to a Samba controlled domain?</A
 135 ></DT
 136 ><DT
 137 ><A
 138 HREF="#AEN89"
 139 >What's the status of print spool (spoolss) support in the NTDOM code?</A
 140 ></DT
 141 ></DL
 142 ></DD
 143 ><DT
 144 ><A
 145 HREF="#AEN92"
 146 >CVS</A
 147 ></DT
 148 ><DD
 149 ><DL
 150 ><DT
 151 ><A
 152 HREF="#AEN95"
 153 >What are the different Samba branches available in CVS ?</A
 154 ></DT
 155 ><DT
 156 ><A
 157 HREF="#AEN118"
 158 >What are the CVS commands ?</A
 159 ></DT
 160 ></DL
 161 ></DD
 162 ></DL
 163 ></DD
 164 ><DT
 165 >3. <A
 166 HREF="#AEN149"
 167 >Establishing Connections</A
 168 ></DT
 169 ><DD
 170 ><DL
 171 ><DT
 172 ><A
 173 HREF="#AEN151"
 174 ></A
 175 ></DT
 176 ><DD
 177 ><DL
 178 ><DT
 179 ><A
 180 HREF="#AEN153"
 181 >How do I get my NT4 or W2000 Workstation to login to the Samba controlled Domain?</A
 182 ></DT
 183 ><DT
 184 ><A
 185 HREF="#AEN158"
 186 >What is a 'machine account' ?</A
 187 ></DT
 188 ><DT
 189 ><A
 190 HREF="#AEN165"
 191 >"The machine account for this computer either does not exist or is not accessable."</A
 192 ></DT
 193 ><DT
 194 ><A
 195 HREF="#AEN171"
 196 >How do I create machine accounts manually ?</A
 197 ></DT
 198 ><DT
 199 ><A
 200 HREF="#AEN184"
 201 >I cannot include a '$' in a machine name.</A
 202 ></DT
 203 ><DT
 204 ><A
 205 HREF="#AEN190"
 206 >I get told "You already have a connection to the Domain...." when creating a
 207          machine account.</A
 208 ></DT
 209 ><DT
 210 ><A
 211 HREF="#AEN194"
 212 >I get told "Cannot join domain, the credentials supplied conflict
 213                 with an existing set.."</A
 214 ></DT
 215 ><DT
 216 ><A
 217 HREF="#AEN198"
 218 >"The system can not log you on (C000019B)...."</A
 219 ></DT
 220 ></DL
 221 ></DD
 222 ></DL
 223 ></DD
 224 ><DT
 225 >4. <A
 226 HREF="#AEN202"
 227 >User Account Management</A
 228 ></DT
 229 ><DD
 230 ><DL
 231 ><DT
 232 ><A
 233 HREF="#AEN204"
 234 >Domain Admins</A
 235 ></DT
 236 ><DD
 237 ><DL
 238 ><DT
 239 ><A
 240 HREF="#AEN206"
 241 >How do I configure an account as a domain administrator?</A
 242 ></DT
 243 ></DL
 244 ></DD
 245 ><DT
 246 ><A
 247 HREF="#AEN210"
 248 >Profiles</A
 249 ></DT
 250 ><DD
 251 ><DL
 252 ><DT
 253 ><A
 254 HREF="#AEN212"
 255 >Why is it bad to set "logon path = \\%N\%U\profile" in smb.conf? ?</A
 256 ></DT
 257 ><DT
 258 ><A
 259 HREF="#AEN226"
 260 >Why are all the users listed in the "domain admin users" using the same profile?</A
 261 ></DT
 262 ><DT
 263 ><A
 264 HREF="#AEN229"
 265 >The roaming profiles do not seem to be updating on the server.</A
 266 ></DT
 267 ></DL
 268 ></DD
 269 ><DT
 270 ><A
 271 HREF="#AEN237"
 272 >Policies</A
 273 ></DT
 274 ><DD
 275 ><DL
 276 ><DT
 277 ><A
 278 HREF="#AEN239"
 279 >What are 'Policies' ?.</A
 280 ></DT
 281 ><DT
 282 ><A
 283 HREF="#AEN246"
 284 >I can't get system policies to work.</A
 285 ></DT
 286 ><DT
 287 ><A
 288 HREF="#AEN260"
 289 >What about Windows NT Policy Editor ?</A
 290 ></DT
 291 ><DT
 292 ><A
 293 HREF="#AEN274"
 294 >Can Win95 do Policies ?</A
 295 ></DT
 296 ></DL
 297 ></DD
 298 ><DT
 299 ><A
 300 HREF="#AEN280"
 301 >Passwords</A
 302 ></DT
 303 ><DD
 304 ><DL
 305 ><DT
 306 ><A
 307 HREF="#AEN282"
 308 >What is password sync and should I use it ?</A
 309 ></DT
 310 ><DT
 311 ><A
 312 HREF="#AEN295"
 313 >How do I get remote password (unix and SMB) changing working ?</A
 314 ></DT
 315 ></DL
 316 ></DD
 317 ></DL
 318 ></DD
 319 ><DT
 320 >5. <A
 321 HREF="#AEN301"
 322 >Miscellaneous</A
 323 ></DT
 324 ><DD
 325 ><DL
 326 ><DT
 327 ><A
 328 HREF="#AEN303"
 329 ></A
 330 ></DT
 331 ><DD
 332 ><DL
 333 ><DT
 334 ><A
 335 HREF="#AEN305"
 336 >What editor can I use in DOS/Windows that won't mess with my unix EOF</A
 337 ></DT
 338 ><DT
 339 ><A
 340 HREF="#AEN318"
 341 >How do I get 'User Manager' and 'Server Manager'</A
 342 ></DT
 343 ><DT
 344 ><A
 345 HREF="#AEN333"
 346 >The time setting from a Samba server does not work.</A
 347 ></DT
 348 ><DT
 349 ><A
 350 HREF="#AEN337"
 351 >"trust account xxx should be in DOMAIN_GROUP_RID_USERS"</A
 352 ></DT
 353 ><DT
 354 ><A
 355 HREF="#AEN341"
 356 >How do I get my samba server to become a member ( not PDC ) of an NT domain?</A
 357 ></DT
 358 ></DL
 359 ></DD
 360 ></DL
 361 ></DD
 362 ><DT
 363 >6. <A
 364 HREF="#AEN376"
 365 >Troubleshooting and Bug Reporting</A
 366 ></DT
 367 ><DD
 368 ><DL
 369 ><DT
 370 ><A
 371 HREF="#AEN378"
 372 >Diagnostic tools</A
 373 ></DT
 374 ><DD
 375 ><DL
 376 ><DT
 377 ><A
 378 HREF="#AEN380"
 379 >What are some diagnostics tools I can use to debug the domain logon process and where can I
 380         find them?</A
 381 ></DT
 382 ><DT
 383 ><A
 384 HREF="#AEN394"
 385 >How do I install 'Network Monitor' on an NT Workstation or a Windows 9x box?</A
 386 ></DT
 387 ></DL
 388 ></DD
 389 ><DT
 390 ><A
 391 HREF="#AEN423"
 392 >What other help can I get ?</A
 393 ></DT
 394 ><DD
 395 ><DL
 396 ><DT
 397 ><A
 398 HREF="#AEN426"
 399 >URLs and similar</A
 400 ></DT
 401 ><DT
 402 ><A
 403 HREF="#AEN472"
 404 >How do I get help from the mailing lists ?</A
 405 ></DT
 406 ><DT
 407 ><A
 408 HREF="#AEN501"
 409 >How do I get off the mailing lists ?</A
 410 ></DT
 411 ></DL
 412 ></DD
 413 ></DL
 414 ></DD
 415 ></DL
 416 ></DIV
 417 ><DIV
 418 CLASS="CHAPTER"
 419 ><HR><H1
 420 ><A
 421 NAME="AEN25"
 422 >Chapter 1. Introduction</A
 423 ></H1
 424 ><DIV
 425 CLASS="SECT1"
 426 ><H1
 427 CLASS="SECT1"
 428 ><A
 429 NAME="AEN27"
 430 >State of Play</A
 431 ></H1
 432 ><P
 433 ><I
 434 CLASS="EMPHASIS"
 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
 438 ></P
 439 ><P
 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
 442 ><P
 443 >Client Side creation of Machine accounts does work but is not complete.
 444     Firstly, the <TT
 445 CLASS="FILENAME"
 446 >add user script</TT
 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"
 452 TARGET="_top"
 453 >HowTo</A
 454 >.
 455     And thirdly, it does not work with NT4ws.
 456     </P
 457 ><P
 458 >A W2K machine can join the domain. See the <A
 459 HREF="samba-pdc-howto.html"
 460 TARGET="_top"
 461 >HowTo</A
 462 >
 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
 468 ><P
 469 >A Domain Admin account is required and at present it appears that only root
 470         is a suitable candidate.</P
 471 ><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
 474 CLASS="FILENAME"
 475 >Create a Computer Account in the Domain</TT
 476 > dialog
 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
 480 ><P
 481 ><I
 482 CLASS="EMPHASIS"
 483 >Actually I'm
 484     not sure that last paragraph is correct ....</I
 485 ></P
 486 ><P
 487 ><B
 488 CLASS="COMMAND"
 489 >Policies</B
 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
 492 ></DIV
 493 ><DIV
 494 CLASS="SECT1"
 495 ><HR><H1
 496 CLASS="SECT1"
 497 ><A
 498 NAME="AEN44"
 499 >Introduction</A
 500 ></H1
 501 ><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
 505 ><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
 510 ><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
 513 ></DIV
 514 ></DIV
 515 ><DIV
 516 CLASS="CHAPTER"
 517 ><HR><H1
 518 ><A
 519 NAME="AEN49"
 520 >Chapter 2. General Information</A
 521 ></H1
 522 ><DIV
 523 CLASS="SECT1"
 524 ><H1
 525 CLASS="SECT1"
 526 ><A
 527 NAME="AEN51"
 528 >What can we do ?</A
 529 ></H1
 530 ><DIV
 531 CLASS="SECT2"
 532 ><H2
 533 CLASS="SECT2"
 534 ><A
 535 NAME="AEN53"
 536 >What can Samba Primary Domain Controller (PDC) do ?</A
 537 ></H2
 538 ><P
 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
 542 ><P
 543 >The following is a list of included  features currently in Samba 2.2:</P
 544 ><P
 545 ></P
 546 ><UL
 547 ><LI
 548 ><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
 551         into the domain.</P
 552 ></LI
 553 ><LI
 554 ><P
 555 >Domain account can be viewed using the User Manager for
 556         Domains  ????</P
 557 ></LI
 558 ><LI
 559 ><P
 560 >Viewing resources on the Samba PDC via the Server Manager for Domains
 561         from the NT client. ??</P
 562 ></LI
 563 ><LI
 564 ><P
 565 >Windows 95 clients will allow user level security to be set
 566         but will not currently allow browsing of accounts.</P
 567 ></LI
 568 ><LI
 569 ><P
 570 >Machine account password updates.</P
 571 ></LI
 572 ><LI
 573 ><P
 574 >Changing of user passwords from an NT client.</P
 575 ></LI
 576 ><LI
 577 ><P
 578 >Partial support for Windows NT group and username mapping.</P
 579 ></LI
 580 ><LI
 581 ><P
 582 >Support for a LDAP password database backend.</P
 583 ></LI
 584 ><LI
 585 ><P
 586 >Printing.</P
 587 ></LI
 588 ></UL
 589 ><P
 590 ></P
 591 ><P
 592 ><B
 593 >These things are note expected to work in the forseeable future</B
 594 ></P
 595 ><UL
 596 ><LI
 597 ><P
 598 >Trust relationships</P
 599 ></LI
 600 ><LI
 601 ><P
 602 >PDC and BDC integration</P
 603 ></LI
 604 ><LI
 605 ><P
 606 >Windows NT ACLs (on the Samba shares)</P
 607 ></LI
 608 ><LI
 609 ><P
 610 >Offer a list of domain users to User Manager for Domains
 611         (or the Security Tab etc).</P
 612 ></LI
 613 ></UL
 614 ></DIV
 615 ><DIV
 616 CLASS="SECT2"
 617 ><HR><H2
 618 CLASS="SECT2"
 619 ><A
 620 NAME="AEN86"
 621 >Can I have a Windows 2000 client logon to a Samba controlled domain?</A
 622 ></H2
 623 ><P
 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
 626         W2K server.</P
 627 ></DIV
 628 ><DIV
 629 CLASS="SECT2"
 630 ><HR><H2
 631 CLASS="SECT2"
 632 ><A
 633 NAME="AEN89"
 634 >What's the status of print spool (spoolss) support in the NTDOM code?</A
 635 ></H2
 636 ><P
 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
 640 ></DIV
 641 ></DIV
 642 ><DIV
 643 CLASS="SECT1"
 644 ><HR><H1
 645 CLASS="SECT1"
 646 ><A
 647 NAME="AEN92"
 648 >CVS</A
 649 ></H1
 650 ><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
 654 ><DIV
 655 CLASS="SECT2"
 656 ><HR><H2
 657 CLASS="SECT2"
 658 ><A
 659 NAME="AEN95"
 660 >What are the different Samba branches available in CVS ?</A
 661 ></H2
 662 ><P
 663 >You can find out more about obtaining Samba's  via
 664         anonymous CVS from
 665         <A
 666 HREF="http://pserver.samba.org/samba/cvs.html"
 667 TARGET="_top"
 668 >       http://pserver.samba.org/samba/cvs.html"</A
 669 >. </P
 670 ><P
 671 ></P
 672 ><DIV
 673 CLASS="VARIABLELIST"
 674 ><P
 675 ><B
 676 >There are basically four branches to watch at the moment :</B
 677 ></P
 678 ><DL
 679 ><DT
 680 >HEAD</DT
 681 ><DD
 682 ><P
 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.
 688         </P
 689 ></DD
 690 ><DT
 691 >SAMBA_2_0</DT
 692 ><DD
 693 ><P
 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.
 698         </P
 699 ></DD
 700 ><DT
 701 >SAMBA_2_2</DT
 702 ><DD
 703 ><P
 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.
 708         </P
 709 ></DD
 710 ><DT
 711 >SAMBA_TNG</DT
 712 ><DD
 713 ><P
 714 >This branch is no longer maintained from the Samba sites.
 715                 Please see <A
 716 HREF="http://www.samba-tng.org/"
 717 TARGET="_top"
 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.
 722         </P
 723 ></DD
 724 ></DL
 725 ></DIV
 726 ></DIV
 727 ><DIV
 728 CLASS="SECT2"
 729 ><HR><H2
 730 CLASS="SECT2"
 731 ><A
 732 NAME="AEN118"
 733 >What are the CVS commands ?</A
 734 ></H2
 735 ><P
 736 >See <A
 737 HREF="http://pserver.samba.org/samba/cvs.html"
 738 TARGET="_top"
 739 >       http://pserver.samba.org/samba/cvs.html</A
 740 ></P
 741 ><P
 742 ></P
 743 ><P
 744 ><B
 745 >To get the Samba 2.2 version, tag SAMBA_2_2 you would do :</B
 746 ></P
 747 ><UL
 748 ><LI
 749 ><P
 750 > For example : <B
 751 CLASS="COMMAND"
 752 >cd /usr/local/src/</B
 753 ></P
 754 ></LI
 755 ><LI
 756 ><P
 757 > <B
 758 CLASS="COMMAND"
 759 >cvs -d :pserver:cvs@pserver.samba.org:/cvsroot
 760                         login</B
 761 ></P
 762 ></LI
 763 ><LI
 764 ><P
 765 > When prompted enter a password of <B
 766 CLASS="COMMAND"
 767 >cvs</B
 768 ></P
 769 ></LI
 770 ><LI
 771 ><P
 772 > <B
 773 CLASS="COMMAND"
 774 >cvs -d :pserver:cvs@pserver.samba.org:/cvsroot
 775                         co -r SAMBA_2_2 samba</B
 776 ></P
 777 ></LI
 778 ></UL
 779 ><P
 780 ></P
 781 ><P
 782 ><B
 783 >Then to update that directory at some later time,</B
 784 ></P
 785 ><UL
 786 ><LI
 787 ><P
 788 > <B
 789 CLASS="COMMAND"
 790 >cd /usr/local/src/samba</B
 791 ></P
 792 ></LI
 793 ><LI
 794 ><P
 795 > <B
 796 CLASS="COMMAND"
 797 >cvs -d :pserver:cvs@pserver.samba.org:/cvsroot login</B
 798 ></P
 799 ></LI
 800 ><LI
 801 ><P
 802 > When prompted enter a password of 'cvs'.</P
 803 ></LI
 804 ><LI
 805 ><P
 806 > <B
 807 CLASS="COMMAND"
 808 >cvs update -d -P</B
 809 ></P
 810 ></LI
 811 ></UL
 812 ></DIV
 813 ></DIV
 814 ></DIV
 815 ><DIV
 816 CLASS="CHAPTER"
 817 ><HR><H1
 818 ><A
 819 NAME="AEN149"
 820 >Chapter 3. Establishing Connections</A
 821 ></H1
 822 ><DIV
 823 CLASS="SECT1"
 824 ><H1
 825 CLASS="SECT1"
 826 ><A
 827 NAME="AEN151"
 828 ></A
 829 ></H1
 830 ><DIV
 831 CLASS="SECT2"
 832 ><H2
 833 CLASS="SECT2"
 834 ><A
 835 NAME="AEN153"
 836 >How do I get my NT4 or W2000 Workstation to login to the Samba controlled Domain?</A
 837 ></H2
 838 ><P
 839 >There is a comprehensive Samba PDC <A
 840 HREF="samba-pdc-howto.html"
 841 TARGET="_top"
 842 >HowTo</A
 843 >
 844      accessable from the samba web site
 845         under 'Documentation'. Its currently located at <A
 846 HREF="http://bioserve.latrobe.edu.au/samba"
 847 TARGET="_top"
 848 >       http://bioserve.latrobe.edu.au/samba</A
 849 >. Read it.</P
 850 ></DIV
 851 ><DIV
 852 CLASS="SECT2"
 853 ><HR><H2
 854 CLASS="SECT2"
 855 ><A
 856 NAME="AEN158"
 857 >What is a 'machine account' ?</A
 858 ></H2
 859 ><P
 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
 862 CLASS="FILENAME"
 863 >/etc/passwd</TT
 864 >
 865     and the other in (typically) <TT
 866 CLASS="FILENAME"
 867 >/usr/local/samba/private/smbpasswd</TT
 868 >. Under
 869     some circumstances these entries are made <A
 870 HREF="#AEN171"
 871 >manually</A
 872 >, the
 873     <A
 874 HREF="samba-pdc-howto.html"
 875 TARGET="_top"
 876 >HowTo</A
 877 > discusses ways of creating them automatically.</P
 878 ></DIV
 879 ><DIV
 880 CLASS="SECT2"
 881 ><HR><H2
 882 CLASS="SECT2"
 883 ><A
 884 NAME="AEN165"
 885 >"The machine account for this computer either does not exist or is not accessable."</A
 886 ></H2
 887 ><P
 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
 890 ><P
 891 >This problem is caused by the PDC not having a suitable machine account.
 892         If you are using the <B
 893 CLASS="COMMAND"
 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
 898 ><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
 907 ></DIV
 908 ><DIV
 909 CLASS="SECT2"
 910 ><HR><H2
 911 CLASS="SECT2"
 912 ><A
 913 NAME="AEN171"
 914 >How do I create machine accounts manually ?</A
 915 ></H2
 916 ><P
 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
 923         entry like this :</P
 924 ><P
 925 ><B
 926 CLASS="COMMAND"
 927 >doppy$:x:505:501:NTMachine:/dev/null:/bin/false</B
 928 ></P
 929 ><P
 930 >On a linux system for example, you would typically add it like this :</P
 931 ><P
 932 ><B
 933 CLASS="COMMAND"
 934 >adduser -g machines -c NTMachine -d /dev/null -s /bin/false -n
 935                 doppy$</B
 936 ></P
 937 ><P
 938 >Then you need to add that entry to smbpasswd, assuming you have a suitable
 939         path to the <B
 940 CLASS="COMMAND"
 941 >smbpasswd</B
 942 > programme, do this :</P
 943 ><P
 944 ><B
 945 CLASS="COMMAND"
 946 >smbpasswd -a -m doppy$</B
 947 ></P
 948 ><P
 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
 952 ></DIV
 953 ><DIV
 954 CLASS="SECT2"
 955 ><HR><H2
 956 CLASS="SECT2"
 957 ><A
 958 NAME="AEN184"
 959 >I cannot include a '$' in a machine name.</A
 960 ></H2
 961 ><P
 962 >A 'machine name' in (typically) <TT
 963 CLASS="FILENAME"
 964 >/etc/passwd</TT
 965 > consists
 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
 968 ><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
 971 CLASS="COMMAND"
 972 >vipw</B
 973 > to edit
 974     the entry, adding the '$'. Or create the whole entry with vipw if you like,
 975     make sure you use a unique uid !</P
 976 ></DIV
 977 ><DIV
 978 CLASS="SECT2"
 979 ><HR><H2
 980 CLASS="SECT2"
 981 ><A
 982 NAME="AEN190"
 983 >I get told "You already have a connection to the Domain...." when creating a
 984          machine account.</A
 985 ></H2
 986 ><P
 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
 991 ><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,
 995         and try again.</P
 996 ></DIV
 997 ><DIV
 998 CLASS="SECT2"
 999 ><HR><H2
1000 CLASS="SECT2"
1001 ><A
1002 NAME="AEN194"
1003 >I get told "Cannot join domain, the credentials supplied conflict
1004                 with an existing set.."</A
1005 ></H2
1006 ><P
1007 >This is the same basic problem as mentioned above, <A
1008 HREF="#AEN190"
1009 >        "You already have a connection..."</A
1010 ></P
1011 ></DIV
1012 ><DIV
1013 CLASS="SECT2"
1014 ><HR><H2
1015 CLASS="SECT2"
1016 ><A
1017 NAME="AEN198"
1018 >"The system can not log you on (C000019B)...."</A
1019 ></H2
1020 ><P
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
1024 ><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
1030 ></DIV
1031 ></DIV
1032 ></DIV
1033 ><DIV
1034 CLASS="CHAPTER"
1035 ><HR><H1
1036 ><A
1037 NAME="AEN202"
1038 >Chapter 4. User Account Management</A
1039 ></H1
1040 ><DIV
1041 CLASS="SECT1"
1042 ><H1
1043 CLASS="SECT1"
1044 ><A
1045 NAME="AEN204"
1046 >Domain Admins</A
1047 ></H1
1048 ><DIV
1049 CLASS="SECT2"
1050 ><H2
1051 CLASS="SECT2"
1052 ><A
1053 NAME="AEN206"
1054 >How do I configure an account as a domain administrator?</A
1055 ></H2
1056 ><P
1057 >See the NTDom <A
1058 HREF="samba-pdc-howto.html"
1059 TARGET="_top"
1060 >HowTo</A
1061 >.</P
1062 ></DIV
1063 ></DIV
1064 ><DIV
1065 CLASS="SECT1"
1066 ><HR><H1
1067 CLASS="SECT1"
1068 ><A
1069 NAME="AEN210"
1070 >Profiles</A
1071 ></H1
1072 ><DIV
1073 CLASS="SECT2"
1074 ><H2
1075 CLASS="SECT2"
1076 ><A
1077 NAME="AEN212"
1078 >Why is it bad to set "logon path = \\%N\%U\profile" in smb.conf? ?</A
1079 ></H2
1080 ><P
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
1083 ><P
1084 ></P
1085 ><UL
1086 ><LI
1087 ><P
1088 > user1 logs into the Windows NT machine.  Therefore the
1089                 [homes] share is set to \\server\user1.</P
1090 ></LI
1091 ><LI
1092 ><P
1093 > user1 works for a while and then logs out. </P
1094 ></LI
1095 ><LI
1096 ><P
1097 > user2 logs into the same Windows NT  machine.</P
1098 ></LI
1099 ></UL
1100 ><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
1105 ><P
1106 >A better solution is to use a separate [profiles] share and set the
1107         "logon path = \\%N\profiles\%U" </P
1108 ><DIV
1109 CLASS="NOTE"
1110 ><BLOCKQUOTE
1111 CLASS="NOTE"
1112 ><P
1113 ><B
1114 >Note: </B
1115 >Is this still a problem ????</P
1116 ></BLOCKQUOTE
1117 ></DIV
1118 ></DIV
1119 ><DIV
1120 CLASS="SECT2"
1121 ><HR><H2
1122 CLASS="SECT2"
1123 ><A
1124 NAME="AEN226"
1125 >Why are all the users listed in the "domain admin users" using the same profile?</A
1126 ></H2
1127 ><P
1128 >You are using a very very old development version of Samba. Upgrade.</P
1129 ></DIV
1130 ><DIV
1131 CLASS="SECT2"
1132 ><HR><H2
1133 CLASS="SECT2"
1134 ><A
1135 NAME="AEN229"
1136 >The roaming profiles do not seem to be updating on the server.</A
1137 ></H2
1138 ><P
1139 >There can be several reasons for this.</P
1140 ><P
1141 >Make sure that the time on the client and the PDC are synchronized.  You can accomplish
1142         this by executing a <B
1143 CLASS="COMMAND"
1144 >net time  \\server /set /yes</B
1145 > replacing server with the
1146         name of your PDC (or another synchronized SMB server). See <A
1147 HREF="#AEN333"
1148 >    about Setting Time</A
1149 ></P
1150 ><P
1151 >Make sure that the
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
1155 ><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
1158 ></DIV
1159 ></DIV
1160 ><DIV
1161 CLASS="SECT1"
1162 ><HR><H1
1163 CLASS="SECT1"
1164 ><A
1165 NAME="AEN237"
1166 >Policies</A
1167 ></H1
1168 ><DIV
1169 CLASS="SECT2"
1170 ><H2
1171 CLASS="SECT2"
1172 ><A
1173 NAME="AEN239"
1174 >What are 'Policies' ?.</A
1175 ></H2
1176 ><P
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
1181 ><P
1182 >On a samba PDC this list is obtained from a file called <B
1183 CLASS="COMMAND"
1184 >ntconfig.pol</B
1185 >
1186     and located in the <B
1187 CLASS="COMMAND"
1188 >[netlogon]</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
1191 HREF="#AEN260"
1192 >    below</A
1193 > for how  to get a suitable editor.</P
1194 ></DIV
1195 ><DIV
1196 CLASS="SECT2"
1197 ><HR><H2
1198 CLASS="SECT2"
1199 ><A
1200 NAME="AEN246"
1201 >I can't get system policies to work.</A
1202 ></H2
1203 ><P
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
1206 ><PRE
1207 CLASS="PROGRAMLISTING"
1208 >       [netlogon]
1209         ....
1210         locking = no
1211         public = no
1212         browseable = yes
1213         ....
1214     </PRE
1215 ><P
1216 >A policy file must be in the <B
1217 CLASS="COMMAND"
1218 >[netlogon]</B
1219 > share and must be
1220     readable by everyone and writeable by only root. The file must be created
1221     by an NTServer <A
1222 HREF="#AEN260"
1223 >Policy Editor</A
1224 >.</P
1225 ><P
1226 >Last time I (drb) looked in the source, it was
1227         looking for <TT
1228 CLASS="FILENAME"
1229 >ntconfig.pol</TT
1230 > first then several other combinations of upper
1231         and lower case. People have reported success using <TT
1232 CLASS="FILENAME"
1233 >NTconfig.pol</TT
1234 >,
1235         <TT
1236 CLASS="FILENAME"
1237 >NTconfig.POL</TT
1238 > and <TT
1239 CLASS="FILENAME"
1240 >ntconfig.pol</TT
1241 >.   These are the case
1242     settings that I (GC) use with the
1243         filename <TT
1244 CLASS="FILENAME"
1245 >ntconfig.pol</TT
1246 ></P
1247 ><PRE
1248 CLASS="PROGRAMLISTING"
1249 >        case sensitive = no
1250         case preserve = yes
1251         default case = yes
1252     </PRE
1253 ></DIV
1254 ><DIV
1255 CLASS="SECT2"
1256 ><HR><H2
1257 CLASS="SECT2"
1258 ><A
1259 NAME="AEN260"
1260 >What about Windows NT Policy Editor ?</A
1261 ></H2
1262 ><P
1263 >To create or edit <B
1264 CLASS="COMMAND"
1265 >ntconfig.pol</B
1266 > you must use the NT Server
1267     Policy Editor, <B
1268 CLASS="COMMAND"
1269 >poledit.exe</B
1270 >       which is included with NT Server
1271     but <I
1272 CLASS="EMPHASIS"
1273 >not NT Workstation</I
1274 >. There is a Policy Editor on a NTws
1275     but it is not suitable for creating <I
1276 CLASS="EMPHASIS"
1277 >Domain Policies</I
1278 >.
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.
1283         You need <TT
1284 CLASS="FILENAME"
1285 >poledit.exe, common.adm</TT
1286 > and <TT
1287 CLASS="FILENAME"
1288 >winnt.adm</TT
1289 >. It is convenient
1290     to put the two *.adm files in <TT
1291 CLASS="FILENAME"
1292 >c:\winnt\inf</TT
1293 > which is where
1294     the binary will look for them unless told otherwise. Note also that that
1295     directory is 'hidden'.</P
1296 ><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
1299     <B
1300 CLASS="COMMAND"
1301 >servicepackname /x</B
1302 >, ie thats <B
1303 CLASS="COMMAND"
1304 >Nt4sp6ai.exe /x</B
1305 >
1306     for service pack 6a.
1307         The policy editor, <B
1308 CLASS="COMMAND"
1309 >poledt.exe</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.
1314     </P
1315 ></DIV
1316 ><DIV
1317 CLASS="SECT2"
1318 ><HR><H2
1319 CLASS="SECT2"
1320 ><A
1321 NAME="AEN274"
1322 >Can Win95 do Policies ?</A
1323 ></H2
1324 ><P
1325 >Install the group policy handler for Win9x to pick up group policies.
1326     Look on the Win98 CD in <TT
1327 CLASS="FILENAME"
1328 >       \tools\reskit\netadmin\poledit</TT
1329 >. Install group policies on a Win9x client by double-clicking
1330         <TT
1331 CLASS="FILENAME"
1332 >grouppol.inf</TT
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
1336 ><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
1339 ></DIV
1340 ></DIV
1341 ><DIV
1342 CLASS="SECT1"
1343 ><HR><H1
1344 CLASS="SECT1"
1345 ><A
1346 NAME="AEN280"
1347 >Passwords</A
1348 ></H1
1349 ><DIV
1350 CLASS="SECT2"
1351 ><H2
1352 CLASS="SECT2"
1353 ><A
1354 NAME="AEN282"
1355 >What is password sync and should I use it ?</A
1356 ></H2
1357 ><P
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
1360     (typically in <TT
1361 CLASS="FILENAME"
1362 >/etc/passwd or /etc/shadow</TT
1363 >). In lots of situations
1364     thats OK, for example :</P
1365 ><P
1366 ></P
1367 ><UL
1368 ><LI
1369 ><P
1370 >The server is only accessible to the user via samba.</P
1371 ></LI
1372 ><LI
1373 ><P
1374 >Pam_smb or similar is installed so other applications
1375         still refer to the samba password.</P
1376 ></LI
1377 ></UL
1378 ><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
1383 ><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
1386 CLASS="COMMAND"
1387 >passwd</B
1388 > command,
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
1393 CLASS="COMMAND"
1394 >smbpasswd</B
1395 >),
1396     otherwise they will only be changing the unix password.</P
1397 ></DIV
1398 ><DIV
1399 CLASS="SECT2"
1400 ><HR><H2
1401 CLASS="SECT2"
1402 ><A
1403 NAME="AEN295"
1404 >How do I get remote password (unix and SMB) changing working ?</A
1405 ></H2
1406 ><P
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).
1411         </P
1412 ><P
1413 >Add these lines to smb.conf under [Global]</P
1414 ><PRE
1415 CLASS="PROGRAMLISTING"
1416 >
1417
1418                 unix password sync = true
1419                 passwd program = /usr/bin/passwd %u
1420                 passwd chat = *password* %n\n *password* %n\n *successful*
1421         </PRE
1422 ><P
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
1426 ></DIV
1427 ></DIV
1428 ></DIV
1429 ><DIV
1430 CLASS="CHAPTER"
1431 ><HR><H1
1432 ><A
1433 NAME="AEN301"
1434 >Chapter 5. Miscellaneous</A
1435 ></H1
1436 ><DIV
1437 CLASS="SECT1"
1438 ><H1
1439 CLASS="SECT1"
1440 ><A
1441 NAME="AEN303"
1442 ></A
1443 ></H1
1444 ><DIV
1445 CLASS="SECT2"
1446 ><H2
1447 CLASS="SECT2"
1448 ><A
1449 NAME="AEN305"
1450 >What editor can I use in DOS/Windows that won't mess with my unix EOF</A
1451 ></H2
1452 ><P
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
1455 ><P
1456 ></P
1457 ><UL
1458 ><LI
1459 ><P
1460 >UltraEdit at <A
1461 HREF="http://www.ultraedit.com"
1462 TARGET="_top"
1463 >www.ultraedit.com</A
1464 ></P
1465 ></LI
1466 ><LI
1467 ><P
1468 >VI for windows at <A
1469 HREF="http://home.snafu.de/ramo/WinViEn.htm"
1470 TARGET="_top"
1471 >        home.snafu.de/ramo/WinViEn.htm</A
1472 ></P
1473 ></LI
1474 ><LI
1475 ><P
1476 >The author prefers PFE at <A
1477 HREF="http://www.lancs.ac.uk/people/cpaap/pfe/"
1478 TARGET="_top"
1479 >            www.lancs.ac.uk/people/cpaap/pfe/</A
1480 > but its no longer being developed...</P
1481 ></LI
1482 ></UL
1483 ></DIV
1484 ><DIV
1485 CLASS="SECT2"
1486 ><HR><H2
1487 CLASS="SECT2"
1488 ><A
1489 NAME="AEN318"
1490 >How do I get 'User Manager' and 'Server Manager'</A
1491 ></H2
1492 ><P
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
1495 ><P
1496 ></P
1497 ><P
1498 ><B
1499 >Microsoft distributes a version of these tools called nexus
1500     for installation on Windows 95 systems.  The tools set includes</B
1501 ></P
1502 ><UL
1503 ><LI
1504 ><P
1505 >Server Manager</P
1506 ></LI
1507 ><LI
1508 ><P
1509 >User Manager for Domains</P
1510 ></LI
1511 ><LI
1512 ><P
1513 >Event Viewer</P
1514 ></LI
1515 ></UL
1516 ><P
1517 >Click here to download the archived file
1518         <A
1519 HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE"
1520 TARGET="_top"
1521 >        ftp://ftp.microsoft.com/Softlib/MSLFILES/NEXUS.EXE</A
1522 ></P
1523 ><P
1524 >The Windows NT 4.0 version of the 'User Manager for Domains'
1525         and 'Server Manager' are available from Microsoft via ftp from
1526         <A
1527 HREF="ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE"
1528 TARGET="_top"
1529 >        ftp://ftp.microsoft.com/Softlib/MSLFILES/SRVTOOLS.EXE</A
1530 ></P
1531 ></DIV
1532 ><DIV
1533 CLASS="SECT2"
1534 ><HR><H2
1535 CLASS="SECT2"
1536 ><A
1537 NAME="AEN333"
1538 >The time setting from a Samba server does not work.</A
1539 ></H2
1540 ><P
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.
1545         </P
1546 ><P
1547 >Anyone know what the registry settings are so this could be done with a Policy ?</P
1548 ></DIV
1549 ><DIV
1550 CLASS="SECT2"
1551 ><HR><H2
1552 CLASS="SECT2"
1553 ><A
1554 NAME="AEN337"
1555 >"trust account xxx should be in DOMAIN_GROUP_RID_USERS"</A
1556 ></H2
1557 ><P
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
1560 ><P
1561 >You are using one of the old development versions. Upgrade.
1562         (The message is unimportant, was a reminder to a developer)</P
1563 ></DIV
1564 ><DIV
1565 CLASS="SECT2"
1566 ><HR><H2
1567 CLASS="SECT2"
1568 ><A
1569 NAME="AEN341"
1570 >How do I get my samba server to become a member ( not PDC ) of an NT domain?</A
1571 ></H2
1572 ><P
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
1578 ><PRE
1579 CLASS="PROGRAMLISTING"
1580 >
1581
1582                 [global]
1583                 ...
1584                 security = domain
1585                 workgroup = { Put your domain name here }
1586                 password server = { Put the ip of the PDC here }
1587                 encrypt passwords = yes
1588                 ...
1589         </PRE
1590 ><P
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
1595 CLASS="EMPHASIS"
1596 >sleepy</I
1597 > to ask the PDC called <I
1598 CLASS="EMPHASIS"
1599 >grumpy</I
1600 >
1601         to do its authentication then <I
1602 CLASS="EMPHASIS"
1603 >grumpy</I
1604 > will need an entry in its smbpasswd
1605         (assuming it's also samba) that starts with <I
1606 CLASS="EMPHASIS"
1607 >sleepy$</I
1608 >. It would have to be
1609     created <A
1610 HREF="#AEN171"
1611 >manually</A
1612 >. </P
1613 ><P
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
1616 ><P
1617 >In either case we then join the domain. If the domain is called <I
1618 CLASS="EMPHASIS"
1619 >forest</I
1620 >
1621         then on sleepy we would join the domain by typing :</P
1622 ><P
1623 ><B
1624 CLASS="COMMAND"
1625 >smbpasswd -j forest</B
1626 ></P
1627 ><P
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
1630     might be <TT
1631 CLASS="FILENAME"
1632 >/usr/local/samba/private/FOREST.SLEEPY.SID</TT
1633 > and
1634     it contains the trust account password for the domain member. The permissions are
1635     (and should remain) "rw-------</P
1636 ><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
1639 CLASS="FILENAME"
1640 >/etc/passwd</TT
1641 >. Because authentication
1642     is being handled at the domain level the
1643         <TT
1644 CLASS="FILENAME"
1645 >/etc/passwd</TT
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
1649         <TT
1650 CLASS="FILENAME"
1651 >/etc/passwd</TT
1652 > does not need a home directory. A typical
1653         line in <TT
1654 CLASS="FILENAME"
1655 >/etc/passwd</TT
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
1659 ><PRE
1660 CLASS="PROGRAMLISTING"
1661 >jblow:x:542:100:Joe Blow:/dev/null:/bin/false</PRE
1662 ><DIV
1663 CLASS="NOTE"
1664 ><BLOCKQUOTE
1665 CLASS="NOTE"
1666 ><P
1667 ></P
1668 ><UL
1669 ><LI
1670 ><P
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 !
1673         </P
1674 ></LI
1675 ><LI
1676 ><P
1677 >The <TT
1678 CLASS="FILENAME"
1679 >username map = </TT
1680 > parameter might help you to avoid having
1681     all those accounts created.</P
1682 ></LI
1683 ><LI
1684 ><P
1685 >You should investigate the smb.conf parameter
1686             <TT
1687 CLASS="FILENAME"
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.
1691         Something like :</P
1692 ><PRE
1693 CLASS="PROGRAMLISTING"
1694 >    [Global]
1695     ....
1696     add user script = /usr/sbin/adduser -n -g users -c User -d /dev/null -s /bin/false %U
1697     ....
1698         </PRE
1699 ></LI
1700 ></UL
1701 ></BLOCKQUOTE
1702 ></DIV
1703 ></DIV
1704 ></DIV
1705 ></DIV
1706 ><DIV
1707 CLASS="CHAPTER"
1708 ><HR><H1
1709 ><A
1710 NAME="AEN376"
1711 >Chapter 6. Troubleshooting and Bug Reporting</A
1712 ></H1
1713 ><DIV
1714 CLASS="SECT1"
1715 ><H1
1716 CLASS="SECT1"
1717 ><A
1718 NAME="AEN378"
1719 >Diagnostic tools</A
1720 ></H1
1721 ><DIV
1722 CLASS="SECT2"
1723 ><H2
1724 CLASS="SECT2"
1725 ><A
1726 NAME="AEN380"
1727 >What are some diagnostics tools I can use to debug the domain logon process and where can I
1728         find them?</A
1729 ></H2
1730 ><P
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
1745 ><P
1746 ></P
1747 ><P
1748 ><B
1749 >Some usefull samba commands worth investigating:</B
1750 ></P
1751 ><UL
1752 ><LI
1753 ><P
1754 >testparam | more</P
1755 ></LI
1756 ><LI
1757 ><P
1758 >smbclient -L //{netbios name of server}</P
1759 ></LI
1760 ></UL
1761 ><P
1762 >An SMB enabled version of tcpdump is available from
1763     <A
1764 HREF="ftp://samba.org/pub/samba/tcpdump-smb/"
1765 TARGET="_top"
1766 >ftp://samba.org/pub/samba/tcpdump-smb/
1767     </A
1768 ></P
1769 ><P
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
1772         ( ie. <B
1773 CLASS="COMMAND"
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.
1777     </P
1778 ><P
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
1785 ></DIV
1786 ><DIV
1787 CLASS="SECT2"
1788 ><HR><H2
1789 CLASS="SECT2"
1790 ><A
1791 NAME="AEN394"
1792 >How do I install 'Network Monitor' on an NT Workstation or a Windows 9x box?</A
1793 ></H2
1794 ><P
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
1800 ><P
1801 >Initially you will need to install 'Network Monitor Tools and Agent' on the
1802     NT Server.  To do this </P
1803 ><P
1804 ></P
1805 ><UL
1806 ><LI
1807 ><P
1808 >Goto Start - Settings - Control Panel - Network - Services - Add </P
1809 ></LI
1810 ><LI
1811 ><P
1812 >Select the 'Network Monitor Tools and Agent' and click on 'OK'.</P
1813 ></LI
1814 ><LI
1815 ><P
1816 >Click 'OK' on the Network Control Panel.</P
1817 ></LI
1818 ><LI
1819 ><P
1820 >Insert the Windows NT Server 4.0 install CD when prompted.</P
1821 ></LI
1822 ></UL
1823 ><P
1824 >At this point the Netmon files should exist in <TT
1825 CLASS="FILENAME"
1826 >%SYSTEMROOT%\System32\netmon\*.*</TT
1827 >.
1828         Two subdirectories exist as well, <TT
1829 CLASS="FILENAME"
1830 >parsers\</TT
1831 > which contains the necessary DLL's
1832         for parsing the netmon packet dump, and <TT
1833 CLASS="FILENAME"
1834 >captures\</TT
1835 >.</P
1836 ><P
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
1839 ><P
1840 ></P
1841 ><UL
1842 ><LI
1843 ><P
1844 >Goto Start - Settings - Control Panel - Network - Services - Add</P
1845 ></LI
1846 ><LI
1847 ><P
1848 >Select the 'Network Monitor Agent' and click on 'OK'.</P
1849 ></LI
1850 ><LI
1851 ><P
1852 >Click 'OK' on the Network Control Panel.</P
1853 ></LI
1854 ><LI
1855 ><P
1856 >Insert the Windows NT Workstation 4.0 install CD when prompted.</P
1857 ></LI
1858 ></UL
1859 ><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
1864 ><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
1869 ></DIV
1870 ></DIV
1871 ><DIV
1872 CLASS="SECT1"
1873 ><HR><H1
1874 CLASS="SECT1"
1875 ><A
1876 NAME="AEN423"
1877 >What other help can I get ?</A
1878 ></H1
1879 ><P
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
1883 ><DIV
1884 CLASS="SECT2"
1885 ><HR><H2
1886 CLASS="SECT2"
1887 ><A
1888 NAME="AEN426"
1889 >URLs and similar</A
1890 ></H2
1891 ><P
1892 ></P
1893 ><UL
1894 ><LI
1895 ><P
1896 >Home of Samba site <A
1897 HREF="http://samba.org"
1898 TARGET="_top"
1899 >        http://samba.org</A
1900 >. We have a mirror near you !</P
1901 ></LI
1902 ><LI
1903 ><P
1904 > The <I
1905 CLASS="EMPHASIS"
1906 >Development</I
1907 > document
1908                 on the Samba mirrors might mention your problem. If so,
1909                 it might mean that the developers are working on it.</P
1910 ></LI
1911 ><LI
1912 ><P
1913 > Ignacio Coupeau has a very comprehesive look at LDAP with Samba at
1914                 <A
1915 HREF="http://www.unav.es/cti/ldap-smb-howto.html"
1916 TARGET="_top"
1917 >               http://www.unav.es/cti/ldap-smb-howto.html</A
1918 >
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
1922 ></LI
1923 ><LI
1924 ><P
1925 >  Lars Kneschke's site covers <A
1926 HREF="http://www.samba-tng.org"
1927 TARGET="_top"
1928 >        Samba-TNG</A
1929 > at
1930                 <A
1931 HREF="http://www.kneschke.de/projekte/samba_tng"
1932 TARGET="_top"
1933 >               http://www.kneschke.de/projekte/samba_tng</A
1934 >, but again, a
1935                 lot of it does not apply to the main stream Samba.</P
1936 ></LI
1937 ><LI
1938 ><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"
1942 TARGET="_top"
1943 >        http://bioserve.latrobe.edu.au/samba</A
1944 > going for a while yet.</P
1945 ></LI
1946 ><LI
1947 ><P
1948 >Misc links to CIFS information
1949         <A
1950 HREF="http://samba.org/cifs/"
1951 TARGET="_top"
1952 >http://samba.org/cifs/</A
1953 ></P
1954 ></LI
1955 ><LI
1956 ><P
1957 >NT Domains for Unix <A
1958 HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
1959 TARGET="_top"
1960 >        http://mailhost.cb1.com/~lkcl/ntdom/</A
1961 ></P
1962 ></LI
1963 ><LI
1964 ><P
1965 >FTP site for older SMB specs:
1966         <A
1967 HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
1968 TARGET="_top"
1969 >        ftp://ftp.microsoft.com/developr/drg/CIFS/</A
1970 ></P
1971 ></LI
1972 ></UL
1973 ><P
1974 ></P
1975 ><P
1976 ><B
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
1979 ></P
1980 ><UL
1981 ><LI
1982 ><P
1983 >CIFS/E Browser Protocol draft-leach-cifs-browser-spec-00.txt</P
1984 ></LI
1985 ><LI
1986 ><P
1987 >CIFS Remote Administration Protocol draft-leach-cifs-rap-spec-00.txt</P
1988 ></LI
1989 ><LI
1990 ><P
1991 >CIFS Logon and Pass Through Authentication draft-leach-cifs-logon-spec-00.txt</P
1992 ></LI
1993 ><LI
1994 ><P
1995 >A Common Internet File System (CIFS/1.0) Protocol draft-leach-cifs-v1-spec-01.txt</P
1996 ></LI
1997 ><LI
1998 ><P
1999 >CIFS Printing Specification draft-leach-cifs-print-spec-00.txt</P
2000 ></LI
2001 ><LI
2002 ><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
2005 ></LI
2006 ><LI
2007 ><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
2010 ></LI
2011 ><LI
2012 ><P
2013 >Microsoft's main CIFS page: http://www.microsoft.com/workshop/networking/cifs/</P
2014 ></LI
2015 ></UL
2016 ></DIV
2017 ><DIV
2018 CLASS="SECT2"
2019 ><HR><H2
2020 CLASS="SECT2"
2021 ><A
2022 NAME="AEN472"
2023 >How do I get help from the mailing lists ?</A
2024 ></H2
2025 ><P
2026 > There are a number of Samba related mailing lists. Go to <A
2027 HREF="http://samba.org"
2028 TARGET="_top"
2029 >http://samba.org</A
2030 >, click on your nearest mirror
2031         and then click on <B
2032 CLASS="COMMAND"
2033 >Support</B
2034 > and then click on <B
2035 CLASS="COMMAND"
2036 >        Samba related mailing lists</B
2037 >.</P
2038 ><P
2039 >For questions relating to Samba TNG go to
2040         <A
2041 HREF="http://www.samba-tng.org/"
2042 TARGET="_top"
2043 >http://www.samba-tng.org/</A
2044 >
2045             It has been requested that you don't post questions about Samba-TNG to the
2046         main stream Samba lists.</P
2047 ><P
2048 ></P
2049 ><P
2050 ><B
2051 >If you post a message to one of the lists please
2052          observe the following guide lines :</B
2053 ></P
2054 ><UL
2055 ><LI
2056 ><P
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.
2060                 </P
2061 ></LI
2062 ><LI
2063 ><P
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
2068 ></LI
2069 ><LI
2070 ><P
2071 >In addition to the version, if you obtained Samba via
2072         CVS mention the date when you last checked it out.</P
2073 ></LI
2074 ><LI
2075 ><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
2079                 size its html).</P
2080 ></LI
2081 ><LI
2082 ><P
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.
2085                 </P
2086 ></LI
2087 ><LI
2088 ><P
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
2095 ></LI
2096 ><LI
2097 ><P
2098 >You might include <I
2099 CLASS="EMPHASIS"
2100 >partial</I
2101 >
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
2104         error messages.</P
2105 ></LI
2106 ><LI
2107 ><P
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
2110 ></LI
2111 ><LI
2112 ><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
2117 ></LI
2118 ></UL
2119 ></DIV
2120 ><DIV
2121 CLASS="SECT2"
2122 ><HR><H2
2123 CLASS="SECT2"
2124 ><A
2125 NAME="AEN501"
2126 >How do I get off the mailing lists ?</A
2127 ></H2
2128 ><P
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"
2132 TARGET="_top"
2133 >http://samba.org</A
2134 >, click on your nearest mirror
2135         and then click on <B
2136 CLASS="COMMAND"
2137 >Support</B
2138 > and then click on <B
2139 CLASS="COMMAND"
2140 >        Samba related mailing lists</B
2141 >. Or perhaps see
2142         <A
2143 HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
2144 TARGET="_top"
2145 >here</A
2146 ></P
2147 ><P
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...)
2150     </P
2151 ></DIV
2152 ></DIV
2153 ></DIV
2154 ></DIV
2155 ></BODY
2156 ></HTML
2157 >