SK0-004 · Question #815
A user was set up with a new computer and is now unable to access a file share on the server. The user was previously able to access the file share from the old computer. The administrator knows the…
The correct answer is A. Ping the server from this computer to see if there is a response. When a new computer cannot access a specific file share but can reach other network resources, the first troubleshooting step is to confirm basic connectivity to the specific server by pinging it before investigating higher-layer issues.
Question
A user was set up with a new computer and is now unable to access a file share on the server. The user was previously able to access the file share from the old computer. The administrator knows the user can access other network resources, and the user's security permissions remain the same. Which of the following is the NEXT logical step for the administrator to troubleshoot this issue?
Options
- APing the server from this computer to see if there is a response
- BLog in to another computer as this user and attempt to browse to the share
- CLog in to this computer as a different user and attempt to browse to the share
- DCheck security permissions on the file share for this user
How the community answered
(53 responses)- A79% (42)
- B8% (4)
- C11% (6)
- D2% (1)
Why each option
When a new computer cannot access a specific file share but can reach other network resources, the first troubleshooting step is to confirm basic connectivity to the specific server by pinging it before investigating higher-layer issues.
Pinging the server directly tests Layer 3 (IP) connectivity to the specific host in question, following the bottom-up OSI troubleshooting methodology. Even though the user can access other network resources, the file server could still be unreachable from the new computer due to a misconfigured NIC, missing route, or host-based firewall rule introduced during the new machine's setup.
Logging in as the user on another computer tests whether the problem is user-specific versus machine-specific, but this step skips verifying that the server is even reachable from the new computer first.
Logging in as a different user on the new computer tests whether the issue is machine-specific versus user-specific, but this is premature before confirming basic network reachability to the server.
The question explicitly states the user's security permissions remain the same, so re-checking permissions is redundant and not the next logical step.
Concept tested: Systematic bottom-up OSI network troubleshooting methodology
Topics
Community Discussion
No community discussion yet for this question.