SK0-004 · Question #309
An administrator has just installed a new NIC into the server. The system POSTs fine and the NIC is recognized by the OS, but it does not receive an IP address. Which of the following is the MOST…
The correct answer is C. The patch cable has not been seated properly. Because the OS already recognizes the NIC and drivers are functioning, the failure to obtain an IP address points to a physical layer connectivity problem - most likely a cable that is not fully seated.
Question
An administrator has just installed a new NIC into the server. The system POSTs fine and the NIC is recognized by the OS, but it does not receive an IP address. Which of the following is the MOST likely cause of this?
Options
- AThe NIC is not on the HCL.
- BThe driver is incorrect on the server.
- CThe patch cable has not been seated properly.
- DThe NIC is not seated properly.
How the community answered
(41 responses)- A7% (3)
- B2% (1)
- C85% (35)
- D5% (2)
Why each option
Because the OS already recognizes the NIC and drivers are functioning, the failure to obtain an IP address points to a physical layer connectivity problem - most likely a cable that is not fully seated.
If the NIC were not on the HCL, the OS would typically fail to recognize it or install a generic driver with limited functionality - not cleanly recognize it as described.
An incorrect driver would most likely prevent proper OS recognition or cause device errors, not result in a fully recognized device that simply lacks an IP address.
A patch cable that is not properly seated will prevent the NIC from establishing a physical link, meaning the switch or DHCP server never becomes reachable. Without a live link, the NIC cannot complete a DHCP discover-offer-request-acknowledge exchange and will remain without an IP address. This is confirmed by the fact that the NIC is recognized by the OS, eliminating driver and hardware seating issues.
If the NIC were not properly seated in its slot, the system would likely not POST cleanly or the OS would fail to detect the device entirely.
Concept tested: Physical layer NIC connectivity and DHCP troubleshooting
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-network-connection-issues
Topics
Community Discussion
No community discussion yet for this question.