nerdexam
Fortinet

FCSS_NST_SE-7.4 · Question #20

Refer to the exhibit, which shows two entries that were generated in the FSSO collector agent logs. What three conclusions can you draw from these log entries? (Choose three.)

The correct answer is A. Remote registry is not running on the workstation. B. The user's status shows as "not verified" in the collector agent. E. A firewall is blocking traffic to port 139 and 445. Because the collector can't reach the workstation's registry, that host will remain in a "not verified" state in the FSSO collector agent. A failure to connect to the remote registry almost always means the Remote Registry service on the Windows box is stopped or disabled…

Authentication

Question

Refer to the exhibit, which shows two entries that were generated in the FSSO collector agent logs. What three conclusions can you draw from these log entries? (Choose three.)

Exhibit

FCSS_NST_SE-7.4 question #20 exhibit

Options

  • ARemote registry is not running on the workstation.
  • BThe user's status shows as "not verified" in the collector agent.
  • CDNS resolution is unable to resolve the workstation name.
  • DThe FortiGate firmware version is not compatible with that of the collector agent.
  • EA firewall is blocking traffic to port 139 and 445.

How the community answered

(41 responses)
  • A
    80% (33)
  • C
    12% (5)
  • D
    7% (3)

Explanation

Because the collector can't reach the workstation's registry, that host will remain in a "not verified" state in the FSSO collector agent. A failure to connect to the remote registry almost always means the Remote Registry service on the Windows box is stopped or disabled. Alternatively (or additionally), a host‑based or network firewall blocking SMB/RPC ports 139 or 445 will produce exactly this "failed to connect" error.

Topics

#FSSO#collector agent#remote registry#Windows authentication ports

Community Discussion

No community discussion yet for this question.

Full FCSS_NST_SE-7.4 Practice