• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6396
  • Last Modified:

No Name Resolution (NetBios or DNS) over PPTP VPN

Hi all,

I cannot resolve host names over my Windows 2000 Server PPTP VPN connection.

I can ping all hosts by IP Address, but pings by netbios hostname and FQDN's fail.

I can connect to the PPTP Server by hostname and access it's resources, however, I cannot connect to other nodes on the network by hostname.

Server OS is Windows 2000 Server SP3, All Network Clients are Windows XP.

Server is the DC running DHCP, DNS, WINS, RRAS and is also the primary file server.

I have a reverse lookup zone specified in DNS for 192.168.0.x

VPN is allocating IP Addresses to clients using DHCP, which has been configured to dish out the IP address of the server for WINS and DNS

Server is behind a Linksys Router. Router is configured to port forward 1723 (PPTP) to the PPTP Server. I assume I'm correct in saying that there should not have to be any other ports open - the PPTP should be all that is needed.

DNS functions as expected on the network - it's only causing problems over the VPN.

I'm hedging my bets on this being a configuration issue relating to DNS (hey, Microsoft recently said that 70% of AD problems were related to DNS).

This is the only server in the network.

DNS is running in AD Integrated mode.

From a client connected over the vpn, an nslookup of any node on the remote network results in a "non-existent domain" error.


Relevant info:

ipconfig /all on connected client


        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.10
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : 192.168.0.2
        Primary WINS Server . . . . . . . : 192.168.0.2

Default Gateway is blank here because I have chosen to untick the "use default gateway on remote network" checkbox under the advanced properties of the VPN. (interesting aside - even with this selected, I cannot ping websites, but I can still use IM and pickup email - DNS must be routing something bizarrely here)

nslookup gibbsdc (PPTP server - main server)

*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Can't find server name for address 192.168.0.2: No response from server
*** Default servers are not available
Server:  UnKnown
Address:  192.168.0.1

*** UnKnown can't find gibbsdc: Non-existent domain

So, I believe the technical term is buggered.

Any thoughts or suggestions? Can't think of any other salient facts to help you out further at this stage
0
EdGillett
Asked:
EdGillett
  • 2
  • 2
1 Solution
 
lrmooreCommented:
So it works better with the box checked to 'use default gateway on remote network'?
What is your local LAN ip subnet without the VPN? Is it also 192.168.0.x perchance?
0
 
EdGillettAuthor Commented:
Yes - Without VPN it is also 192.168.0.x

Actually, it doesn't work better with the box checked to "use default gateway on remote network" - but I can still use IM on the VPN'd client (although I can't ping websites ... it's routing something very bizarre I think?)
0
 
lrmooreCommented:
You're local LAN should be something other than the same as the remote LAN, or the subnet you get from the VPN client.
Try changing your local lan to something different, like 192.168.22.x
0
 
EdGillettAuthor Commented:
Having changed my local LAN to be in the 192.168.10.x range, I now have a working VPN.

I had read that elsewhere, but did not apply it for some reason.

It makes sense of course, but I was under the impression that the VPN somehow corrected for connections to the same range? Evidently not.

Anywho, our resident expert lrmoore gets the points for being right on the money.

It's always something simple ...

Thanks.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now