Name Resolution on VPN

Can ping FQDN but not host name
Can't ping VPN client by name
Connection issues on DC, ISA, DNS and WINS server as VPN server
How to assign DNS and WINS on VPN client manually
How does RAS assign IP settings to a RAS Client?
Name resolution Issue in a VPN client
Name Resolution and Connectivity Issues on W2K Domain Controller with RRAS and DNS Installed
"No domain server was available" while the dialup connection is active
VPN server is a Virtual Multihomed Server
VPN client don't appear in Network Neighborhood/My Network Places
VPN clients can't browse remote computers in Network Neighborhood/My Network Places

Can ping FQDN but not host name

Symptoms: after establishing VPN, you can't ping the server name. However, you can ping FQDN, for example, server1.chicagotech.net.

Cause: Missing the DNS suffixes. Add the DNS suffixes to the VPN client or setup WINS. For the consultants,, refer to 072604RL

Can't ping VPN client by name

Symptom: you can ping the vpn client by ip but when attempting to ping a vpn client from remote LAN, you get time out.

Resolution: 1) if you have correct DNS and WINS settings, you should be able to ping vpn client by name.
2) If you get the time out with a different ip (for example, ping ip is 192.168.100.7 and real ip is 192.168.100.13), check the dns and wins records and delete the 192.168.100.7.
3) If the dns and wins records don't show the client record, make sure it points to the same and correct dns and wins.
4) If the VPN client doesn't register its DNS, you may need to go the VPN connection properties>networking>TCP/IP. On the DNS tab, enter the DNS server IP in DNS suffix for this connection and check Register this connection's addresses in DNS. Or use ipconfig /registerdns command.
5) Also make sure all computers are pointing to the same DNS.

Connection issues on DC, ISA, DNS and WINS server as VPN server

Symptom: You have a Windows 2000/2003 server is configured as VPN running DNS, WINS, you may experience some connection issues. 1) the internal computers can't ping the server by name; 2) if the server is a DC and Master Browser, you may have a computer browsing issue; 3) you may receive Event ID: 4319 - A duplicate name has been detected on the tcp network; 4) You may receive error messages like "No Logon Servers Available to Service your Logon Request" when you try to open file shares or map network drives to the Routing and Remote Access server; 5) if the server is also a DC, you may not be able to logon the domain; 6) if the server is also running ISA, you cannot browse the Web from client computers on the local network, regardless of whether the computers are configured to use Web Proxy or the Microsoft Firewall Client. For example, "The page cannot be displayed" may appear in the Web browser with a "cannot find server or DNS" error message.

Cause: When a VPN client connects to the VPN server, the server creates a PPP adapter to communicate with the remote computer. The server may then register the IP address of this PPP adapter in the DNS or the WINS database. When the internal computers try to connect to the IP address of the PPP adapter, them cannot reach the PPP adapter, then the connections fail.

How to assign DNS and WINS on VPN client manually

Name resolution is big issue in VPN access. If your VPN server doesn't setup correctly or the VPN client can't receive the VPN DNS and WINS settings, you may setup them yourself. To do this, go to the VPN connection>properties>TCP/IP properties>Advanced. Click DNS and WINS tabs to assign the VPN server's DNS and WINS.

Name resolution Issue in a VPN client

To assign the DNS and WINS to a VPN client for name resolution, you should configure VPN server with the IP addresses of the appropriate DNS and WINS servers. The VPN client inherits the DNS and WINS configured on the VPN server. If name resolution does not work from the VPN server, it will not work for VPN clients.

Name Resolution and Connectivity Issues on W2K Domain Controller with RRAS and DNS Installed

Symptoms: You may experience some name resolution and connectivity issues if the W2K domain controller is configured with RRAS and DNS. After a remote client establishes a connection by using Dial-Up Networking, one or more of the following symptoms may occur: 1. Internal clients may no longer be able to browse the Web.
2. A "cannot find server or DNS" error occurs when using nslookup.
3. When using PING to ping the name of the server on an Internal client, it returns any other address other than the IP address that is bound to the server's internal adapter.
4. You cannot browse through the list of computers in Network Neighborhood or My Network Places.
5. You may receive Event ID: 4319, Source: Netbt. Description: A duplicate name has been detected on the tcp network. The IP address of the machine that sent the message is in the data. Use NBTSTAT with a switch of N in a command window to see which name is in a conflict state.
6. W2K/XP clients cannot map a network drive to the server. The client may receive the following error message: No Logon Servers Available to Service your Logon Request.

Resolutions: 1. Install the latest service pack.
2. Make sure the clients have correct DNS and WINS settings.
3. Disable NetBIOS for all RRAS connections.
4. Double-click on the entries for the servername[00h], and servername[20h] to verify that there is only 1 IP address on them.

Note: Refer to MS Q292822

"No domain server was available" while the dialup connection is active

Symptom: you have windows 2000 domain controller with DNS, DHCP, WINS and Dialup connection. Whenever the dialup connection is active, none client can't logon and gets a message "No domain server was available to to validate your password. You may not be able to gain access to some network resources"

Resolution: On the server, make sure you don't have "Register this connection's addresses in DNS" checked under TCP/IP Advanced DNS settings. To check this, go to the Properties of the dialup connection> the Properties of the TCP/IP>Advanced>DNS, uncheck "Register this connection's addresses in DNS"

VPN server is a Virtual Multihomed Server

After enabling RRAS on a DC with WINS and DNS server, you may have some Master Browser or/and WINS issues. That reason is that VPN server is a Virtual Multihomed Server. The resolution is to disable NetBIOS Over TCP/IP on all interfaces including RRAS interfaces except the internal interface.

VPN client don't appear in remote LAN's Network Neighborhood/My Network Places

Normally, VPN clients don't appears in Network Neighborhood/My Network Places on the LAN. If you want the VPN clients to appear on the LAN browse list, you may need to install NetBEUI on the RAS server and RAS clients. This peculiarity is a known problem with RAS, but no fix is available at press time.