Inconsistant DNS resolution problems on 2003 RRAS server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Paul M. Landry (paul_at_lyme.com)
Date: 12/26/04

  • Next message: Herb Martin: "Re: Inconsistant DNS resolution problems on 2003 RRAS server" 
    Date: Sat, 25 Dec 2004 21:49:25 -0500

    Hello all,
    I've been troubleshooting a client's RRAS server, running on a Windows 2003
    server.
    This server is a dedicated Dial-in and VPN server, and is not a Domain
    Controller, DNS or DHCP server.
    Just plain old RRAS.
    Has anyone seen the following problem?
    RRAS is set up to problem 26 VPN connections.
    Typically there are about seven RRAS connections going at any one time.
    All VPN clients are Windows XP Pro SP2 clients, and they are all configured
    exactly the same.
    However, some clients are resolving DNS names differently that others.

    Once connected to the VPN, pinging a either FQDN or just machine name these
    names resolve to the IP address internal to the network. I.e
    pioneer.mydomain.com and PIONEER both resolve to 192.168.100.9.
    This is what I want to happen.

    On some other VPN clients, however, when pinging the address, these clients
    are getting back the Globally routable IP address of this server.

    As stated above, the VPN settings on each client are exactly the same.
    I've verified this with WebEx sessions to check the settings myself.

    I don't know if this is related, but I've noticed that when VPN clients
    connect, they always get the same IP address they had from prior
    connections.
    I've not set anything up explicitly to do this in the RRAS server, so I
    suspect some kind of caching.

    I need all clients to resolve names to the internal IP addresses.
    Does anyone know of any fixes or work-arounds for this.?

    Thanks,

    Paul Landry

  • Next message: Herb Martin: "Re: Inconsistant DNS resolution problems on 2003 RRAS server"

    Relevant Pages

    • RE: VPN Clients Not Registering in AD DNS
      ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
      (microsoft.public.windows.server.sbs)
    • RE: SBS VPN connects but no shares..
      ... VPN clients can no longer access internal resources after you install ... Windows Server 2003 Service Pack 1 on a computer that is running ISA Server ... How to configure a VPN connection to your corporate network in Windows XP ...
      (microsoft.public.windows.server.sbs)
    • RE: VPN issue
      ... I understand that you cannot initialize the VPN ... Could you please let me know if this is a Premium SBS server box with ISA ... To support the PPTP VPN clients behind the ISA server, ...
      (microsoft.public.windows.server.sbs)
    • Re: SBS VPN Strengthening
      ... to my other clients, so a software only configuation would be preferred. ... Have SBS 2003 along with Server 2003 at various sites, ... each location and they would establish the VPN between those offices. ... connect to remote offices you could use a hub and spoke method VPN or use ...
      (microsoft.public.windows.server.sbs)
    • Re: VPN Error 733, Event Log Error 20050 with SBS 2003 - revisited
      ... the VPN from within the LAN with anti-virus ... It seems that I need to look at repairing the whole of RRAS. ... disable or uninstall any antivirus software on the RRAS Server. ... check if there are some firewall between remote VPN client and RRAS server. ...
      (microsoft.public.windows.server.sbs)