Why Can't I Log on to the DHCP Server with Active Directory Credentials?
Question
A systems administrator is setting up a new server that will be used as a DHCP server.
The administrator installs the OS but is then unable to log on using Active Directory credentials.
The administrator logs on using the local administrator account and verifies the server has the correct IP address, subnet mask, and default gateway.
The administrator then gets on another server and can ping the new server.
Which of the following is causing the issue?
A.
Port 443 is not open on the firewall B.
The server is experiencing a downstream failure C.
The local hosts file is blank D.
The server is not joined to the domain.
D.
Explanations
A systems administrator is setting up a new server that will be used as a DHCP server.
The administrator installs the OS but is then unable to log on using Active Directory credentials.
The administrator logs on using the local administrator account and verifies the server has the correct IP address, subnet mask, and default gateway.
The administrator then gets on another server and can ping the new server.
Which of the following is causing the issue?
A.
Port 443 is not open on the firewall
B.
The server is experiencing a downstream failure
C.
The local hosts file is blank
D.
The server is not joined to the domain.
D.
Based on the information provided, it appears that the server is not joined to the domain. This means that the server is not configured to authenticate users against the Active Directory domain, which is why the administrator is unable to log on using Active Directory credentials.
When a server is joined to a domain, it can use the domain's user accounts and security policies to authenticate users and manage access to network resources. However, if the server is not joined to the domain, it will rely on local user accounts and security policies, which can limit its functionality and create security vulnerabilities.
To resolve the issue, the administrator will need to join the server to the domain by configuring the server's network settings and joining it to the appropriate Active Directory domain. Once the server is joined to the domain, the administrator should be able to log on using Active Directory credentials and manage the DHCP server as needed.
It is important to note that the other options presented in the answer choices are unlikely to be the cause of the issue. Port 443 is used for HTTPS traffic and is not typically required for DHCP functionality. A downstream failure would impact network connectivity, but it would not prevent the administrator from logging on to the server using local credentials. A blank hosts file would not prevent the administrator from logging on to the server or configuring DHCP services.
