0

We are able to connect successfully to PPTP VPN (Standard Windows VPN) but once connected, ping through hostnames will not resolve to their IPs. For internal, this is working perfectly. This is only happening on remote computers that are joining the network through VPN. We would like to add some DNS A record to save the users from remembering the IPs of the file servers. However, we are facing this problem. Any advise on this guys on how we could fix this issue?

Let me know if you need further details. THANKS!!!!

Improve this question
10
  • 1
    What DNS servers are being assigned to the VPN clients? Are they pinging by single-label name or by FQDN?
    – joeqwerty
    Mar 5, 2015 at 20:44
  • Actually, the PPTP VPN server also holds the DNS role so what the clients are getting are the ones configure on the DNS server settings of the server for its LAN adapter. Pinging by single label nor FQDN doesnt work. We always get "Ping request could not find host." result.
    – Vance
    Mar 5, 2015 at 22:23
  • OK, so what DNS servers are the VPN server using? Are they the DNS servers for your AD?
    – joeqwerty
    Mar 5, 2015 at 22:28
  • The VPN server uses its LAN IP (10.1.10.10) as Primary DNS server and (8.8.8.8) as the secondary one. Yeah, I believe 10.1.10.10 is a DNS server of the AD but if I need to confirm, how do I double check this?
    – Vance
    Mar 5, 2015 at 22:54
  • 1. If your machines are joined to an AD domain then none of them should use external DNS servers (8.8.8.8). 2. Log onto your domain controller and find it's ip address. That's the ip address that all of your domain joined clients should use for DNS, including your VPN server. This DNS server will then be assigned to the VPN clients and should resolve your name resolution problem.
    – joeqwerty
    Mar 6, 2015 at 2:10

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .