Why does it not detect the windows domain?

While enabling the Identity Awareness blade the Identity Awareness wizard does not automatically detect the windows domain.

Why does it not detect the windows domain?
A . Security Gateways is not part of the Domain
B . SmartConsole machine is not part of the domain
C . SMS is not part of the domain
D . Identity Awareness is not enabled on Global properties

Answer: B

Explanation:

To enable Identity Awareness:

Log in to SmartDashboard. From the Network Objects tree, expand the Check Point branch. Double-click the Security Gateway on which to enable Identity Awareness. In the Software Blades section, select Identity Awareness on the Network Security tab.

The Identity Awareness Configuration wizard opens.

Select one or more options. These options set the methods for acquiring identities of managed and unmanaged assets. AD Query – Lets the Security Gateway seamlessly identify Active Directory users and computers. Browser-Based Authentication – Sends users to a Web page to acquire identities from unidentified users. If Transparent Kerberos Authentication is configured, AD users may be identified transparently. Terminal Servers – Identify users in a Terminal Server environment (originating from one IP address).

See Choosing Identity Sources.

Note – When you enable Browser-Based Authentication on a Security Gateway that is on an IP Series appliance, make sure to set the Voyager management application port to a port other than 443 or 80.

Click Next.

The Integration With Active Directory window opens.

When SmartDashboard is part of the domain, SmartDashboard suggests this domain automatically. If you select this domain, the system creates an LDAP Account Unit with all of the domain controllers in the organization’s Active Directory.