Learn why a workstation can ping a file server but cannot access file sharing, even on the same subnet, as required for the CompTIA A+ Core 1 220-1101 exam. Understand how a blocked SMB port (TCP 445) prevents file sharing despite network connectivity.
Table of Contents
Question
A workstation cannot connect to a file server on the same subnet. The server is pingable, but file sharing is inaccessible. What is the most likely cause?
A. Incorrect subnet mask
B. Blocked SMB port
C. Disabled file sharing service
D. Faulty Ethernet cable
E. Incorrect DNS settings
Answer
B. Blocked SMB port
Explanation
If the server is pingable but file sharing is inaccessible, the Server Message Block (SMB) port (e.g., 445) is likely blocked by a firewall, preventing file sharing access.
When a workstation can successfully ping a file server on the same subnet but cannot access shared files, the most likely cause is that the Server Message Block (SMB) port—typically TCP port 445—is blocked by a firewall on the server or network device. Ping uses ICMP, which confirms basic network connectivity, but file sharing relies on SMB, which requires specific ports to be open.
If TCP port 445 is blocked, SMB traffic cannot reach the server, making shared folders inaccessible even though the server responds to pings. This scenario is common in environments with strict firewall policies or after recent security changes. Verifying and allowing SMB traffic through the firewall will restore file sharing functionality.
Other causes, such as incorrect subnet mask or DNS issues, would typically affect connectivity more broadly, not just file sharing.
CompTIA A+ Core 1 220-1101 certification exam practice question and answer (Q&A) dump with detail explanation and reference available free, helpful to pass the CompTIA A+ Core 1 220-1101 exam and earn CompTIA A+ Core 1 220-1101 certification.