NT4-based domain member server. Becoming a member server of an NT4-based domain issimilar to connecting to an Active Directory. The main difference is NT4-based domains do notuse Kerberos in their authentication method, making the smb.conf file simpler. In this instance,the Samba member server serves as a pass through to the NT4-based domain server.[global]workgroup = DOCSnetbios name = DOCS_SRVsecurity = domain[homes]comment = Home Directoriesvalid users = %Sread only = Nobrowseable = No[public]comment = Datapath = /exportforce user = docsbotforce group = usersguest ok = YesHaving Samba as a domain member server can be useful in many situations. There are timeswhere the Samba server can have other uses besides file and printer sharing. It may bebeneficial to make Samba a domain member server in instances where Linux-only applicationsare required for use in the domain environment. Administrators appreciate keeping track of allmachines in the domain, even if not Windows-based. In the event the Windows-based serverhardware is deprecated, it is quite easy to modify the smb.conf file to convert the server to aSamba-based PDC. If Windows NT-based servers are upgraded to Windows 2000/2003, thesmb.conf file is easily modifiable to incorporate the infrastructure change to Active Directory ifneeded.ImportantAfter configuring the smb.conf file, join the domain before starting Samba bytyping the following command as root:root# net rpc join -U administrator%passwordNote that the -S option, which specifies the domain server hostname, does not need to bestated in the net rpc join command. Samba uses the hostname specified by the workgroupdirective in the smb.conf file instead of it being stated explicitly.3.3. Domain ControllerChapter 14. Samba256
