Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN Trouble, cannot ping server names BUT can ping using IP

Status
Not open for further replies.

Starsystems11

Programmer
Nov 12, 2003
1
US
I cannot resolve any names across the VPN; however, I can ping using the ip.

My configuration is Windows 2003 Standard running VPN and as a DC. The server I'm trying to reach, is the mail server running NT 4.0 Server.

I'm assume the problem is with the default gateway. Once connected to the VPN it resolves the IP as 192.9.200.50 and the default gateway at 192.9.200.50, when the gateway should be 192.9.200.1.

What's really odd, is when I log in locally to the box. I can ping the mail server by the name. Yet when I connect through VPN it does not resolve the name, saying it's a DNS problem.

Any help would be appreciated, thanks.
 
quoted form
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.


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network and How to at
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top