Re: DNS and NetBIOS names not resolving over a PPTP VPN using RRAS

Also this one.
How to enable name resolution
For a VPN client to can resolve full computer name and NetBIOS name of computers on a remote network automatically, you can enable broadcast name resolution ...
www.howtonetworking.com/VPN/vpnnameresolution1.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
<Nonapeptide@xxxxxxxxx> wrote in message news:33e9303b-2192-479d-9aad-811e990b50b7@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 26, 9:49 pm, Nonapept...@xxxxxxxxx wrote:
Short question: How does one enable the resolution of DNS and NetBIOS
names on a remote network from a client over a PPTP VPN?

Backstory:

I have a PPTP VPN facilitated by a Windows Server 2003 machine with
RRAS. VPN traffic is forwarded through a firewall to the RRAS machine.
NetBIOS and DNS names other than the server's are not being resolved
even though they once were. In other words, the command 'net view
[RRAS server name]' will respond, however 'net view [any other
computer name on the VPN's network]' will not respond. I get the error
message "System error 53 has occurred. The network path was not
found." Virtually the same thing happens with DNS. 'ping [RRAS
server]' resolves nicely, but pinging anything else gets "Ping request
could not find host accounting. Please check the name and try again."

As I said, there was a time in the recent past that DNS and NetBIOS
resolved over the VPN connection. I’m not aware of any changes that
have been made that would affect this. I've tried setting the remote
gateway as the default gateway and even setting the DNS server on the
VPN's network as my primary DNS server and still can't get any DNS
names to resolve. However, using nslookup with the remote location's
DNS server will get each name in question to resolve. Hmmmm.

Oddly enough, I have an entirely different PPTP VPN connection (this
time the VPN facilitator is an ISA 2004 server) that behaves the way
that I want it to. DNS and NetBIOS names resolve with or without the
remote gateway being my default gateway and without the remote DNS
servers being on the list of my LAN interface’s DNS servers and with
the option to register my connection’s addresses in DNS left
unchecked. There is no discernable difference between the connectoids
for the two VPN connections.

Again, how does one get remote NetBIOS and DNS names to resolve
through a VPN connection? I thought I knew, but apparently I
don't. :-|

I forgot to mention that using \\IP_Address\ from the VPN client to an
IP address on the remote netework is successful. That may have been
obvious, but I figured I'd say it anyway.

.

Relevant Pages

  • Re: Setting Up LMHost File? (DNS problem on VPN).
    ... If routing and name resolution worked before, what is different about the way you have set up the VPN connection? ... We have around 17 remote sites so using a DC for each would be expensive, and I can't see a benefit at the moment. ... also the DNS server. ... which includes the DNS. ...
    (microsoft.public.windows.server.networking)
  • Re: NS and domain A record affecting AD
    ... The AD domain name doesn't resolve to the IP address of a local Domain ... Controller, but to other remote domain controllers, what ... dcdiag checked out ok. ... loaded the DNS service on this DC? ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS not authoritative for domain
    ... I am using an internal DHCP server which is also my DNS and WINS ... I have configured a PPTP VPN using ISA to test whether or not I had an issue ... >> I can correctly resolve short and FQDN inside my domain. ...
    (microsoft.public.windows.server.dns)
  • Re: NS and domain A record affecting AD
    ... dc11.child.company.org resolves fine on all DNS servers. ... Could that be the cause for slow logons, are there other known issues with ... If the remote dc's are on a slow link you may not even get your gpo's ... If local clients can not resolve AD domain name to ...
    (microsoft.public.windows.server.active_directory)
  • Re: NS and domain A record affecting AD
    ... Clients are pointing to the local dc for both WINS and DNS, ... If the remote dc's are on a slow link you may not even get your gpo's ... If local clients can not resolve AD domain name to ...
    (microsoft.public.windows.server.active_directory)
Loading