VPN Problems with Name Resolution using DNS services

Cause 1 A DNS server may not be configured for IPsec connections on the Contivity VPN Switch.
Action 1 Validate that the Contivity VPN client has been configured with a DNS entry. For NT 4.0, open a Command Prompt and enter IPCONFIG /ALL. Verify that a DNS server entry is listed. For Windows 95, from the Start menu on the taskbar, select Run and enter WINIPCFG. Select "Contivity VPN Adapter" from the pull down list of Adapters, then click More Info. Record the information displayed under DNS Server entry and verify it with the network administrator.

Cause 2 The hostname being resolved has both a public and a private IP address. This is commonly referred to as a Split-Horizon DNS.
Action 2 Open a Command Prompt and ping the host you are trying to reach with a fully-qualified hostname (for example, www.vpnclient.com). If you receive a response, verify that the IP address returned on the first line (for example, www.vpnclient.com [207.78.33.329] is an IP address from the remote corporate network. If it is not, notify your network administrator that the internal hostname should be modified so that it is not the same as the external hostname.

Cause 3 The retail release (a.k.a. "release 1") of Windows 95 contained a bug that prevented use of more than one DNS server. This problem was fixed in OS Release2.
Action 3 If you are using a release of Windows earlier than Release 2 of Windows 95, then you need to upgrade.


Home