Question 106 of 464
N10-009 Network Troubleshooting Practice Question
A user reports that they can access the internet but cannot connect to an internal file server at IP address 192.168.1.50. The technician successfully pings the file server's IP address from the user's workstation. The file server is on the same subnet as the user. What is the most likely cause of this issue?
⚠ Common exam trap
Test-takers frequently assume a successful ping guarantees full connectivity, but ICMP and application traffic use different protocols and ports, so a firewall can block one while allowing the other.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The file server's firewall is blocking the file-sharing protocol while allowing ICMP.
The technician can ping the file server (ICMP success) but the user cannot connect to it using the file-sharing protocol (e.g., SMB on TCP/445). This indicates network-layer reachability is fine, but the application-layer service is blocked. The most likely cause is the file server's host-based firewall (e.g., Windows Defender Firewall) allowing ICMP Echo Requests while blocking inbound SMB traffic, which is a common misconfiguration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The file server has an incorrect default gateway configured.
Why it's wrong here
For devices to communicate within the same local subnet, a default gateway is not required because traffic can be directly forwarded using MAC addresses resolved via ARP. The problem states the user can ping the file server, implying they are on the same local network segment. An incorrect default gateway on the file server would only impact its ability to reach destinations outside its local subnet, such as the internet, but would not prevent local file-sharing connections or ICMP pings from a client on the same subnet.
When this WOULD be correct
A user on a different subnet cannot reach the file server, but can ping other external hosts. The file server's default gateway is misconfigured, preventing return traffic from routing back to the user's subnet.
- ✗
The user's workstation has an incorrect DNS server configured.
Why it's wrong here
DNS (Domain Name System) is responsible for resolving human-readable hostnames into IP addresses. The problem implies the user is attempting to connect to the file server using its IP address, or at least that the connection failure is not due to name resolution. If the connection attempt uses a direct IP address, DNS is entirely bypassed. Therefore, an incorrect DNS server configuration on the user's workstation would only prevent access to resources by hostname, not by IP address, and would not explain the inability to connect to a file share via IP while still being able to ping it.
When this WOULD be correct
A user reports they can access the internet by IP address but cannot browse websites by domain name. The workstation has a static IP with an incorrect DNS server IP, preventing name resolution.
- ✓
The file server's firewall is blocking the file-sharing protocol while allowing ICMP.
Why this is correct
The scenario describes successful internet access and successful ping to the file server, but failure to connect to an internal file share. This indicates that basic network connectivity (Layer 3) is present, as evidenced by ICMP (ping) working. However, the application-layer protocol for file sharing (e.g., SMB on TCP port 445 for Windows shares) is being blocked. A firewall on the file server itself is designed to filter traffic at higher layers, allowing specific protocols like ICMP while denying others, such as file-sharing protocols, thereby preventing the connection despite successful pings.
- ✗
The user's workstation has a duplicate IP address assigned.
Why it's wrong here
A duplicate IP address on the user's workstation would lead to severe network instability and intermittent connectivity issues, often manifesting as complete loss of network access or frequent disconnections. When two devices on the same subnet claim the same IP, ARP conflicts occur, causing packets to be misrouted or dropped. Since the user can successfully ping the file server and access the internet, a duplicate IP address is highly improbable, as such a fundamental network conflict would prevent even basic ICMP communication.
When this WOULD be correct
A user reports intermittent connectivity and cannot access any network resources. The technician finds that the workstation's IP address conflicts with another device on the network, causing packet loss and disconnections.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The N10-009 exam frequently reuses these exact scenarios with slightly different constraints.
✓The file server's firewall is blocking the file-sharing protocol while allowing ICMP.Correct answer▾
Why this is correct
The scenario describes successful internet access and successful ping to the file server, but failure to connect to an internal file share. This indicates that basic network connectivity (Layer 3) is present, as evidenced by ICMP (ping) working. However, the application-layer protocol for file sharing (e.g., SMB on TCP port 445 for Windows shares) is being blocked. A firewall on the file server itself is designed to filter traffic at higher layers, allowing specific protocols like ICMP while denying others, such as file-sharing protocols, thereby preventing the connection despite successful pings.
✗The file server has an incorrect default gateway configured.Wrong answer — click to see why▾
Why this is wrong here
The user can ping the file server's IP, indicating layer-3 connectivity. An incorrect default gateway on the file server would prevent traffic from leaving its subnet, but since both are on the same subnet, the gateway is not needed for local communication.
★ When this WOULD be the correct answer
A user on a different subnet cannot reach the file server, but can ping other external hosts. The file server's default gateway is misconfigured, preventing return traffic from routing back to the user's subnet.
Why candidates choose this
Candidates often associate connectivity issues with gateway misconfiguration, overlooking that same-subnet communication does not require a gateway.
✗The user's workstation has an incorrect DNS server configured.Wrong answer — click to see why▾
Why this is wrong here
The user can access the internet, which requires DNS resolution, so the DNS server configuration is correct. The issue is with internal file server access, not name resolution.
★ When this WOULD be the correct answer
A user reports they can access the internet by IP address but cannot browse websites by domain name. The workstation has a static IP with an incorrect DNS server IP, preventing name resolution.
Why candidates choose this
Candidates often associate connectivity issues with DNS, especially when symptoms involve accessing resources by name versus IP, but here the user can access the internet (which uses DNS) and the file server is accessed by IP.
✗The user's workstation has a duplicate IP address assigned.Wrong answer — click to see why▾
Why this is wrong here
A duplicate IP address would cause intermittent connectivity or complete loss of network access, but the user can access the internet and ping the file server, which rules out an IP conflict.
★ When this WOULD be the correct answer
A user reports intermittent connectivity and cannot access any network resources. The technician finds that the workstation's IP address conflicts with another device on the network, causing packet loss and disconnections.
Why candidates choose this
Candidates may confuse symptoms of IP conflicts (e.g., connectivity issues) with the specific scenario where only file sharing fails, overlooking that ping works fine.
Analysis generated from the official N10-009blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This N10-009 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the N10-009 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.