Re: Persistent VPN name resolution problem

Tech-Archive recommends: Speed Up your PC by fixing your registry

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

Date: Thu, 11 Mar 2004 09:06:15 -0500
To: Jerry Paquette <nospampaquette@uwo.ca>

PS--Client machines have my WINS server address set in the TCP/IP setup
for VPN but not for the NIC. In any case WINS is getting the correct
address assigned by my server.

Jerry Paquette wrote:

> 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

  • RE: PPTP VPN connection problems
    ... The problem is that the VPN does not disconnect. ... However after some idle period I can not send packets across the connection. ... A ping to the server would result in "Request timed out". ... If I connect with the VPN client locally to the internet ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Ports to Open
    ... the VPN connection after you change the firewall before SBS. ... On the server, please stop the Routing and Remote Access service. ... Total GRE packets sent = 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2003 VPN Default Gateway Issues
    ... Ethernet adapter Local Area Connection: ... If the VPN server is configured to use a static IP address ... the default gateway on the client is not the problem. ...
    (microsoft.public.windows.server.networking)
  • RE: VPN Connectivity issues through LAN
    ... I understand that you cannot ping SBS after ... you can establish VPN connection from the remote LAN. ... You have to rerun the CEICW to make sure your SBS 2003 server have right ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)