nerdexam
CompTIA

LX0-104 · Question #637

The configuration below is contained in the Samba main configuration file: [homes] comment = Home folder writable = yes browseable = no valid users = %S However, an attempt at listing the share with s

The correct answer is A. One of the reasons is that the browseable directive was set to no, denying the share listing to B. If the smbclient command was executed by an authenticated user, the share would be listed.. The [homes] share was not listed by smbclient because browseable = no hides it from general browsing, and smbclient may not have been executed by an authenticated user.

Administrative Tasks

Question

The configuration below is contained in the Samba main configuration file: [homes] comment = Home folder writable = yes browseable = no valid users = %S However, an attempt at listing the share with smbclient didn't work. Which TWO options below could be possible reasons for this?

Options

  • AOne of the reasons is that the browseable directive was set to no, denying the share listing to
  • BIf the smbclient command was executed by an authenticated user, the share would be listed.
  • CThe configurations above are correct, but the administrator forgot to reload the configuration
  • DThe real problem is in the valid users directive, which allows access to the share, but denies
  • EThe writable option is in the wrong place in the configuration file.

How the community answered

(59 responses)
  • A
    64% (38)
  • C
    20% (12)
  • D
    5% (3)
  • E
    10% (6)

Why each option

The `[homes]` share was not listed by `smbclient` because `browseable = no` hides it from general browsing, and `smbclient` may not have been executed by an authenticated user.

AOne of the reasons is that the browseable directive was set to no, denying the share listing toCorrect

The `browseable = no` directive explicitly prevents the `[homes]` share from being listed when clients attempt to browse for available shares, making it invisible to general discovery.

BIf the smbclient command was executed by an authenticated user, the share would be listed.Correct

Even with `browseable = no`, an authenticated user can directly access their home share (e.g., `smbclient //server/username`). If the `smbclient` command was executed by an unauthenticated user or as a general browse (`smbclient -L //server`), the share would not be listed due to the need for authentication for user-specific shares.

CThe configurations above are correct, but the administrator forgot to reload the configuration

While reloading configuration is often necessary, the `browseable = no` setting and `valid users = %S` behavior are fundamental configurations that directly explain the issue if the configuration was active.

DThe real problem is in the valid users directive, which allows access to the share, but denies

The `valid users = %S` directive correctly allows access to the share for the authenticated user whose name matches the share, it does not cause a listing denial that overrides `browseable = no`.

EThe writable option is in the wrong place in the configuration file.

The `writable = yes` option is correctly placed within the share definition in `smb.conf`.

Concept tested: Samba share browseability and authentication

Source: https://www.samba.org/samba/docs/current/manpages/smb.conf.5.html

Topics

#Samba configuration#smb.conf#share access#troubleshooting

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full LX0-104 Practice