Firewall Update Breaks Internet Access: Which Setting Is at Fault?
A technician is troubleshooting internet connectivity issues after a firewall update. Users report that they can access local network resources, such as printers and shares, but cannot access the internet. Which of the following settings is most likely causing the issue?
Community Insight
It tests whether you can separate a local-layer failure from a routing failure; the trap is blaming the IP addressing scheme instead of the exit path off the subnet.
When users can still reach printers and file shares but lose all internet access after a firewall update, the fault lies at the boundary between the local subnet and outside networks. This page establishes why the default gateway — not static addressing, the subnet mask, or VLANs — is the answer.
Choosing static IP assignments (A), assuming fixed addressing is fragile, when in fact static hosts on the same subnet would still reach printers and shares exactly as reported.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
In this scenario the successful ping to printers and access to shares prove that Layer 2 switching, the subnet mask, and the host portion of the IP configuration are all intact — the machines are on the right subnet talking to the right peers. The only thing that has changed is the path off that subnet, which is exactly the job of the default gateway. A firewall update commonly rewrites or clears the gateway entry, resets the interface address the LAN points at, or drops the NAT/route that sends traffic outward, and any of those leaves internal traffic untouched while killing internet reachability. Option B therefore matches every symptom in the question: local resources fine, outbound traffic dead. Verifying the configured gateway against the firewall/router LAN interface, then confirming the host can ARP and ping it, is the first diagnostic step.Why the Other Options Are Wrong
Static IP assignments (A) do not by themselves prevent internet access — a statically addressed host with a correct gateway, mask, and DNS resolves and browses normally, so this cannot explain a sudden failure that left local traffic working. A subnet mask error (C) would break local communication too, since hosts would misjudge whether the printer or file server is on-link; the scenario explicitly says shares and printers still work. VLANs (D) are a segmentation mechanism, and a VLAN mistake would typically isolate users from local servers or drop them off the segment entirely rather than cleanly preserving LAN access while removing only the internet. None of these three explains the precise split the users describe.Community Comment Notes
Nearly every commenter converged on B, and their reasoning aligns with the routing-boundary analysis above. As one learner put it, "The gateway is the door out of your local network." Elle expanded on the firewall angle, noting "After the firewall update the default gateway settings could have changed," which is precisely the failure mode the question is built around. ishan94 reached the same conclusion, arguing the update "most likely altered or corrupted the default gateway setting." A lone vote for static IP assignments reflects the classic distractor pull toward any option containing an addressing term, but no comment supported it technically.Exam Strategy
Split the symptom into layers before reading the options: local-only success means addressing, mask, and switching are healthy, so only the egress path is suspect. On 220-1201, any stem pairing a firewall or router change with 'LAN works, internet doesn't' is pointing at the default gateway.
Frequently Asked Questions
Why can users still reach printers and shares if the default gateway is wrong?
Printer and share traffic stays inside the local subnet, so it is delivered by MAC address via switching and never touches the gateway.
Would a wrong subnet mask still let internet access work?
No. An incorrect mask usually breaks local delivery as well, because hosts misjudge whether a destination is on-link or must be sent to the gateway.
Related Analysis
Practice All 220-1201 Questions
Access 105 questions with complete answers and detailed explanations.
View Full 220-1201 Practice Test →