For Samba 3 to be able to work as a PDC, some modifications are needed in its main configuration file. Select the THREE options below that show the required actions for this task.

Question

Options

• AThe Samba server has to be a logon server. This can be configured by the domain logons
• BThe Samba server needs to have the logon and the account creation scripts, to properly
• CThe Samba server must be a Domain Master Browser. To configure this, the domain master
• DThe time server = yes directive needs to be configured, so Samba will behave as a WINS
• EThe security = user directive must be set.

• A
  74% (14)
• B
  11% (2)
• D
  16% (3)

Explanation

To configure Samba 3 as a Primary Domain Controller (PDC), three directives work together: security = user (E) establishes user-level authentication, which is the foundation PDC auth requires; domain logons = yes (A) enables Samba to process Windows domain logon requests from clients; and domain master = yes (C) designates the server as the Domain Master Browser, allowing it to maintain the authoritative browse list across the entire domain - all three are mandatory for PDC operation.

Option B is wrong because logon/account creation scripts are optional enhancements to the PDC experience, not required for the server to function as a PDC at all.

Option D is wrong on two counts: time server = yes makes Samba serve time to Windows clients - it has nothing to do with WINS (that's wins support = yes), and neither role is required for PDC functionality.

Memory tip: Remember the three PDC pillars with "SDL" - Security=user (who you are), Domain master (who owns browsing), Logons (who can log in). If any pillar is missing, the PDC collapses.

No community discussion yet for this question.