fedora-docs-l10n/fedora-system-administrat/rawhide/pages/_partials/servers/Samba — Indonesian @ Fedora Weblate: For more information on Kerberos, and the [command]#/etc/krb5.conf# file, see …

Translation

English type: Plain text

Indonesian

Needs editing

Skip

	English	Indonesian	Actions
	[printers] comment = All Printers path = /var/spool/samba printer admin = john, ed, @admins create mask = 0600 guest ok = yes printable = yes use client driver = yes browseable = yes
	Domain Member Server
	indexterm:[Samba,server types,Domain Member] A domain member, while similar to a stand-alone server, is logged into a domain controller (either Windows or Samba) and is subject to the domain's security rules. An example of a domain member server would be a departmental server running Samba that has a machine account on the Primary Domain Controller (PDC). All of the department's clients still authenticate with the PDC, and desktop profiles and all network policy files are included. The difference is that the departmental server has the ability to control printer and network shares.
	Active Directory Domain Member Serverindexterm:[Samba,smb.conf,Active Directory Member Server example]
	To implement an Active Directory domain member server, follow procedure below:
	Adding a Member Server to an Active Directory Domain
	Create the `/etc/samba/smb.conf` configuration file on a member server to be added to the Active Directory domain. Add the following lines to the configuration file:
	[global] realm = EXAMPLE.COM security = ADS encrypt passwords = yes # Optional. Use only if Samba cannot determine the Kerberos server automatically. password server = kerberos.example.com
	With the above configuration, Samba authenticates users for services being run locally but is also a client of the Active Directory. Ensure that your kerberos `realm` parameter is shown in all caps (for example `realm = EXAMPLE.COM`). Since Windows 2000/2003/2008 requires Kerberos for Active Directory authentication, the `realm` directive is required. If Active Directory and Kerberos are running on different servers, the `password server` directive is required to help the distinction.
	Configure Kerberos on the member server. Create the `/etc/krb5.conf` configuration file with the following content:
	[logging] default = FILE:/var/log/krb5libs.log
	[libdefaults] default_realm = AD.EXAMPLE.COM dns_lookup_realm = true dns_lookup_kdc = true ticket_lifetime = 24h renew_lifetime = 7d rdns = false forwardable = false
	[realms] # Define only if DNS lookups are not working # AD.EXAMPLE.COM = { # kdc = server.ad.example.com # admin_server = server.ad.example.com # master_kdc = server.ad.example.com # }
	[domain_realm] # Define only if DNS lookups are not working # .ad.example.com = AD.EXAMPLE.COM # ad.example.com = AD.EXAMPLE.COM
	Uncomment the `[realms]` and `[domain_realm]` sections if DNS lookups are not working.
	For more information on Kerberos, and the [command]#/etc/krb5.conf# file, see the [citetitle]_Using Kerberos_ section of the [citetitle]_link:++https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System-Level_Authentication_Guide/Using_Kerberos.html++[Red{nbsp}Hat{nbsp}Enterprise{nbsp}Linux{nbsp}7 System Level Authentication Guide]_.
	To join an Active Directory server, type the following command as `root` on the member server:
	~]# net ads join -U administrator%password
	The [command]#net# command authenticates as `Administrator` using the NT LAN Manager (NTLM) protocol and creates the machine account. Then [command]#net# uses the machine account credentials to authenticate with Kerberos.
	The security option
	Since `security = ads` and not `security = user` is used, a local password back end such as `smbpasswd` is not needed. Older clients that do not support `security = ads` are authenticated as if `security = domain` had been set. This change does not affect functionality and allows local users not previously in the domain.
	Windows NT4-based Domain Member Serverindexterm:[Samba,smb.conf,NT4-style Domain Member example]
	The following `/etc/samba/smb.conf` file shows a sample configuration needed to implement a Windows NT4-based domain member server. Becoming a member server of an NT4-based domain is similar to connecting to an Active Directory. The main difference is NT4-based domains do not use Kerberos in their authentication method, making the `/etc/samba/smb.conf` file simpler. In this instance, the Samba member server functions as a pass through to the NT4-based domain server.
	An Example Configuration of Samba Windows NT4-based Domain Member Server
	[global] workgroup = DOCS netbios name = DOCS_SRV security = domain
	Having Samba as a domain member server can be useful in many situations. There are times where the Samba server can have other uses besides file and printer sharing. It may be beneficial to make Samba a domain member server in instances where Linux-only applications are required for use in the domain environment. Administrators appreciate keeping track of all machines in the domain, even if not Windows-based. In the event the Windows-based server hardware is deprecated, it is quite easy to modify the `/etc/samba/smb.conf` file to convert the server to a Samba-based PDC. If Windows NT-based servers are upgraded to Windows 2000/2003/2008 the `/etc/samba/smb.conf` file is easily modifiable to incorporate the infrastructure change to Active Directory if needed.
	Make sure you join the domain before starting Samba
	After configuring the `/etc/samba/smb.conf` file, join the domain before starting Samba by typing the following command as `root`:
	~]# net rpc join -U administrator%password
	Note that the [option]`-S` option, which specifies the domain server host name, does not need to be stated in the [command]#net rpc join# command. Samba uses the host name specified by the `workgroup` directive in the `/etc/samba/smb.conf` file instead of it being stated explicitly.
	Domain Controller

Loading…

None

String added in the repository

English

Indonesian 0 characters edited Current translation Empty

2 months ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Indonesian
No related strings found in the glossary.

String information

Source string description

type: Plain text

Source string location

./pages/_partials/servers/Samba.adoc:499

String age

2 months ago

Last updated

2 months ago

Source string age

a year ago

Translation file

po/id/rawhide/pages/_partials/servers/Samba.po, string 146