A critical server was replaced by the IT staff the previous night. The following morning, some
users are reporting that they are unable to browse to the Internet upon booting their
workstations. Users who did not shut down their workstations the previous day are able to
connect to the Internet. A technician looks at the following report from a workstation with no
Internet connectivity:
IP Address: 192.168.1.101
Netmask: 255.255.255.0
DHCP Server: 192.168.1.1
DNS Server: 192.168.1.2
Default Gateway: 192.168.1.1
Given the above report, which of the following is the cause of why some workstations are
unable to browse the Internet?
A.
The workstation has an APIPA address.
B.
The DHCP server is unavailable.
C.
The default gateway router is misconfigured.
D.
The DHCP server is misconfigured.
Explanation:
Reference:
http://knowurtech.netfirms.com/networking/how_dhcp_works.html
why ?
0
0
A = WRONG
0
0
Sorry.
A = WRONG because the IP is class C (I believe), but it is definitely not 169 aka APIPA
B = WRONG because some users are able to connect
C and D are the only two options left, and they both share the same IP. So, either the gateway is wrong or the server is wrong. Since there is no mention to gateway configuration changes, and it is a valid IP, we can assume that the configuration error happened on the server side
0
0
This is a tricky question! The answer really has nothing to do with the specific addresses, so don’t waste your time focusing on them. The configuration is correct. Class C private IP, class C subnetmask, correct DNS, and default gateway. The answer is D because the machines that didn’t shut down still have the same IP address from the DHCP server. The machines that had to reboot were given new IP addresses from the DHCP server, therefore, the configuration for them is different.
0
0
Chris I get that but what is misconfigured (DHCP)on the user or server side. Answer said that the DHCP is misconfigured, deceiving.
0
0