Question

Difficulty: MediumTroubleshooting Routing, Default Gateways, and ACLs

A client workstation on VLAN 20 (10.20.0.50/2410.20.0.50/24) is unable to access an HTTPS service hosted on a server in VLAN 50 (10.50.0.100/2410.50.0.100/24). Following the CompTIA network troubleshooting methodology, in what sequence should a network technician perform the following steps to diagnose and resolve this connectivity issue?

  1. 1Verify local network layer settings with `ipconfig /all` and test ICMP connectivity to the local default gateway (10.20.0.110.20.0.1).
  2. 2Execute `traceroute 10.50.0.100` from the workstation to identify the exact router hop where packet forwarding fails.
  3. 3Inspect the inbound and outbound Access Control Lists (ACLs) on the intervening router interface to check for TCP port 443 filtering.
  4. 4Modify the interface ACL by inserting an explicit `permit tcp any host 10.50.0.100 eq 443` rule prior to the implicit deny statement.
  5. 5Attempt an HTTPS connection to 10.50.0.10010.50.0.100 from the workstation browser to confirm end-to-end functionality.

Answer

The correct troubleshooting sequence follows the standard CompTIA methodology: verify local IP settings and gateway connectivity (`item_1`), trace the routing path to find the drop location (`item_2`), inspect ACL statements on the dropping interface (`item_3`), apply the necessary ACL permit modification (`item_4`), and verify service restoration from the client (`item_5`).
The correct sequence strictly adheres to the standard CompTIA network troubleshooting methodology: 1) Identify the problem starting with local gateway verification (`item_1`), 2) Establish a hypothesis of remote routing/filtering failure via `traceroute` (`item_2`), 3) Test hypothesis by evaluating ACL rules on the gateway router (`item_3`), 4) Implement the solution by updating the ACL permit statement (`item_4`), and 5) Verify full system functionality by testing client HTTPS access (`item_5`).

Step-by-Step Solution

1
Gather information and test local network parameters.
Confirms the host has a valid IP address, subnet mask, and functional default gateway.
Always eliminate local physical and link-layer issues before investigating remote infrastructure.
2
Perform path tracing to locate remote routing failures.
Pinpoints the specific gateway router dropping traffic destined for 10.50.0.10010.50.0.100.
Traceroute isolates whether the fault is a missing static route, dynamic routing failure, or packet filtering.
3
Analyze gateway router configuration and ACL rules.
Identifies an unintended ACL drop or implicit deny blocking TCP port 443.
Testing the hypothesis requires checking security rules applied to the routed interfaces.
4
Apply the corrective configuration change to the ACL.
Permits HTTPS traffic through the router interface.
Implements the solution plan by placing explicit permit rules before implicit deny matches.
5
Verify complete system functionality.
Ensures the application is accessible and no unintended side effects were created.
Verification confirms the root cause was properly resolved.

Key Concept

CompTIA Network Troubleshooting Methodology applied to Routing, Default Gateways, and ACLs
Rate this question