VPN clients will often not resolve names for the remote domain to which you are connected, especially if connecting from a non-domain joined machine. There are numerous options to address this such as; using IP’s rather than names, adding entries to LMHost (NetBIOS) and/or Host (DNS) files, or using WINS. However DNS is the best and only practical solution since Server 2008. Though the VPN server should be configured to ‘hand out’ these options via DHCP to VPN client’s, in some configurations such as using a RRAS Static Address Pools, this is not possible. If so, there are two simple additions to the VPN network adapter required on the client machine. Under properties for the VPN/PPP adapter, go to the DNS tab under advanced TCP/IPv4 properties:
- Add the IP of the remote site’s DNS server, either under “DNS server addresses, in order of use”, or on the “Internet Protocol Version 4 (TCP/IPv4) Properties” page under “Preferred DNS server”, which will automatically add it to the former.
- Add the remote site’s internal DNS suffix to the “DNS suffix for this connection” box
Should you wish to explore the other options mentioned above (IP’s, Host & LMHost files, WINS), or need use those methods for legacy systems, you can read more about these on my other blog: http://msmvps.com/blogs/robwill/archive/2008/05/10/vpn-client-name-resolution.aspx