220-1102 Question 804
Single answerVPNA user working from home reports that they can browse the internet normally, but after connecting to the company's VPN they cannot open internal file shares or reach the intranet by server name. The VPN client shows as connected, and the user can successfully ping an internal server by IP address. As the technician, which action is the BEST next step to restore access?
- A
Configure the VPN connection to use the company's internal DNS servers
- B
Disable the user's local Windows Firewall profile while connected to the VPN
- C
Replace the user's router because the internet connection is blocking SMB traffic
- D
Change the VPN type from L2TP/IPsec to PPTP for better compatibility
Show answer and explanation
Correct answer: A
Explanation
This scenario tests practical VPN troubleshooting. Because the VPN connects successfully and internal resources respond by IP address, the tunnel itself is working. The failure to access file shares or the intranet by server name indicates a DNS problem. In business VPN deployments, remote clients typically need access to internal DNS servers so they can resolve private hostnames, Active Directory resources, and intranet records. This aligns with common Microsoft and enterprise VPN best practices: verify IP connectivity first, then verify DNS settings and suffixes provided by the VPN. The best next step is to configure the VPN connection to use the company's internal DNS servers.
- A. Correct.
Correct. The user can reach an internal resource by IP address but not by server name, which strongly indicates a name resolution issue rather than a general VPN connectivity problem. A common fix is to ensure the VPN connection is assigning or using the organization's internal DNS servers so internal hostnames and intranet records can be resolved properly.
- B. Incorrect.
Incorrect. A local firewall can block traffic, but in this scenario the user can already reach an internal server by IP address through the VPN tunnel. That means the tunnel is functioning and traffic is passing. The symptom specifically points to DNS/name resolution, not general packet filtering by the local firewall.
- C. Incorrect.
Incorrect. The home router is unlikely to be the root cause because the VPN is connected and internal hosts are reachable by IP address. If the router were blocking the required traffic broadly, the user would be more likely to have VPN connection failures or no access to internal IP addresses at all. This option reflects a common mistake of blaming the internet connection instead of examining the specific symptom.
- D. Incorrect.
Incorrect. PPTP is outdated and considered insecure, and switching to it is not an appropriate troubleshooting step for this symptom. The issue is not that the tunnel cannot be established; it is that internal names are not resolving after connection. Best practice is to use secure VPN protocols and correct DNS configuration rather than downgrade security.