220-801 · Question #151
A technician has replaced the NIC in a computer running Windows XP Professional and has properly installed the device driver. The computer indicates the card has network connectivity, but the…
The correct answer is B. Use ipconfig to check the current settings and Network Connections to make changes. When a NIC has link-level connectivity but cannot reach the Internet, the next step is to verify and correct the TCP/IP configuration (IP address, subnet mask, default gateway, DNS) using ipconfig and Network Connections.
Question
A technician has replaced the NIC in a computer running Windows XP Professional and has properly installed the device driver. The computer indicates the card has network connectivity, but the technician is unable to access the Internet. Which of the following should the technician do NEXT to finish the NIC installation?
Options
- AChange the computer and DNS server's IP addresses in the Action Center
- BUse ipconfig to check the current settings and Network Connections to make changes
- CAssign the NIC an APIPA address using ipconfig and the network setup wizard
- DReboot the computer and configure the necessary network settings in the BIOS
How the community answered
(40 responses)- A3% (1)
- B78% (31)
- C8% (3)
- D13% (5)
Why each option
When a NIC has link-level connectivity but cannot reach the Internet, the next step is to verify and correct the TCP/IP configuration (IP address, subnet mask, default gateway, DNS) using ipconfig and Network Connections.
Action Center (formerly Security Center in XP context) does not contain controls for changing IP addresses or DNS settings; it is a system notification and security tool.
Network connectivity at the link level (card detected, cable connected) does not guarantee correct TCP/IP configuration. Using ipconfig /all reveals the current IP address, subnet mask, default gateway, and DNS settings, and the Network Connections control panel in Windows XP allows the technician to manually set or correct those values - the most likely cause of Internet access failure after a NIC replacement.
An APIPA address (169.254.x.x) is automatically assigned when DHCP fails and indicates no valid network configuration; intentionally assigning one would prevent Internet access, not restore it.
Network IP configuration (gateway, DNS, IP address) is not configured in the system BIOS; BIOS manages hardware-level settings and boot order, not OS-level TCP/IP parameters.
Concept tested: TCP/IP configuration verification after NIC replacement
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/tcp-ip-addressing-and-subnetting
Topics
Community Discussion
No community discussion yet for this question.