220-1102 Question 120
Single answerhostnameA technician renames a Windows 10 workstation from WS-104 to ACCT-PC07 so it matches the company's naming standard. After the reboot, users report they can sign in locally, but coworkers who try to access the PC by typing \ACCT-PC07 into File Explorer receive a 'Windows cannot access' error. However, \192.168.1.57 still works. Which action is the BEST next step to restore access by hostname?
- A
Flush and re-register the workstation's DNS records so the new hostname resolves correctly
- B
Disable and re-enable the network adapter so the old hostname is removed from the NIC
- C
Change the computer back to WS-104 because SMB file sharing does not support renamed hosts
- D
Run CHKDSK on the workstation to repair file system errors affecting name resolution
Show answer and explanation
Correct answer: A
Explanation
This scenario tests practical troubleshooting of hostnames in a Windows network. When a system is reachable by IP address but not by its hostname, the issue is typically name resolution, not basic connectivity or SMB itself. After changing a computer name, the new hostname must be reflected in DNS so other clients can resolve it. In Windows environments, a technician may use commands such as ipconfig /flushdns and ipconfig /registerdns, then verify resolution with tools like ping, nslookup, or Test-NetConnection. This aligns with common Microsoft best practices for troubleshooting DNS-related hostname issues on domain or business networks.
- A. Correct.
Correct. Access by IP address working while access by the new hostname fails strongly suggests a name resolution problem rather than a file sharing or connectivity problem. After a hostname change, the system may need to update DNS records so other devices can resolve the new name to the correct IP address. In a Windows environment, flushing stale cached entries and re-registering DNS records is an appropriate next troubleshooting step.
- B. Incorrect.
Incorrect. Resetting the adapter may renew network connectivity, but it does not directly address the underlying issue of other systems still resolving the old or missing DNS hostname. The NIC itself does not store the computer name in a way that would typically cause this symptom.
- C. Incorrect.
Incorrect. Windows SMB file sharing works with renamed computers. Renaming a host is a normal administrative task. The problem is not that the system was renamed, but that name resolution for the new hostname has likely not propagated or updated properly.
- D. Incorrect.
Incorrect. CHKDSK checks disk and file system integrity. The scenario points to a hostname resolution issue because access by IP address succeeds, which indicates the share service and network path are likely functioning.