Persistent VPN name resolution problem

From: Jerry Paquette (nospampaquette_at_uwo.ca)
Date: 03/11/04 

Date: Thu, 11 Mar 2004 08:53:48 -0500

Let me try this again with a bit more precision in the hope that someone
can help me.

At home I have two computers (both recent, high-end P4s) running XP pro.
  Connection is DSL and the two home computers (laptop wireless) run
through a LinkSys BEFW1134 router (non-VPN=one VPN connection at a time
only) At the other end my office computer is configured as a Win2K
(SP4) server and is a subdomain of a large academic domain. Clients can
connect to VPN without problem. No problem with mapping back from host
to clients once VPN connection is established. I cannot, however, ping
or use terminal server by machine name directly to clients connected to
VPN although connection works fine by ip# if I look it up manually in WINS.

My server is assigning ip#s in the 172.xx.xx.xx range. The home router
is assigning ip#s starting with 192.168.1.100. Now the problem is that
if I ping on the home machine name ping tries to use the router rather
than server-assigned ips and, of course, nothing happens as below.

Pinging client_name.my_subdomain_name.next_level_subdomain
name.domain_name.ca [192.168.1.100] with

Request timed out.
Request timed out.
Request timed out.
Request timed out.

I thought that if the ip#s being assigned by the VPN host were different
from those assigned by the router this shouldn't happen!

Does anyone know what's going on here and how to fix it? I've spent a
lot of time ferreting through various related postings on Google but
none seem to get to the heart of this particular problem.

Thank you for any help.

Relevant Pages

  • Persistent VPN name resolution problem
    ... At home I have two computers ... Connection is DSL and the two home computers run ... connect to VPN without problem. ... My server is assigning ip#s in the 172.xx.xx.xx range. ...
    (microsoft.public.windows.server.networking)
  • Re: Remote desktop not connecting through VPN (only for my home ma
    ... We have a number of staff who connect using remote desktop through VPN to ... I on the other hand have never been able to get remote desktop to work from ... What about connection to SBS itself? ... I dont have any other computers at home and I connect the broadband modem ...
    (microsoft.public.windows.server.sbs)
  • VPN & RDP
    ... who VPN into the server daily. ... Network>Microsoft Windows Network and select the domain, only the computers ... initiates the VPN connection, the remote assistance/RDP connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Branch Offices - URGENT!!
    ... the best way is to keep the remote computers as ... will make a VPN connection to the central office (terminating the VPN to a ... are on the road without network connection there will be no problem as they ... The network is a native Windows 2003 server ...
    (microsoft.public.windows.server.active_directory)
  • Re: Persistent VPN name resolution problem
    ... PS--Client machines have my WINS server address set in the TCP/IP setup ... > connect to VPN without problem. ... > to clients once VPN connection is established. ... > My server is assigning ip#s in the 172.xx.xx.xx range. ...
    (microsoft.public.win2000.networking)