Re: A different VPN/DHCP/DNS routing issue

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

From: Mike Busch (mbusch_at_remove.wisor.com)
Date: 07/30/04


Date: Fri, 30 Jul 2004 06:55:00 -0700


Ok you mention the LAN interface under RRAS. I see three
things under RRAS that look like they would be what you
are talking about;

Venus->Network Interfaces->Local Area Connection
and
Venus->IP Routing->General->Local Area Connection
and
Venus->IP Routing->IGMP->Local Area Connection

However the most likely candidate(Venus->Network
Interfaces->Local Area Connection) does not give me
access to properties and infact just about everything is
greyed out so there's not much for me to configure
there. My guess is I have to disable RRAS to edit this
field. Is this true? Is this where the incorrect DNS
info is?

Thanks,
Mike

>-----Original Message-----
> VPN clients do not get this info from DHCP. The
name server address
>(DNS and/or WINS), like the IP address, is part of the
PPTP negotiation at
>connection time. It comes directly from the RRAS server
itself. Usually it
>will give the client the DNS address which is configured
on the RRAS
>server's LAN interface.
>
> After the client connects it can get the DNS info
configured in DHCP by
>using a dhcpinform request. For this to work, the RRAS
server needs to have
>the DHCP relay agent configured.
>
>"Mike Busch" <mbusch@remove.wisor.com> wrote in message
>news:6d5601c475a4$d3ee1b60$a501280a@phx.gbl...
>> I know I asked a similar questions about VPN routing
>> earlier today and I really appreciate the answers i
got.
>> I'll report back if that work when the specific user
who
>> had the problem lets me know. but know I have a couple
>> of users with the same issue. My ew VPN server is
>> dishing out incorrect DNS information. My DHCP should
>> dish out the following DNS info:
>>
>> Primary: 192.168.2.60
>> Secondary: 192.168.2.62
>> Tertiary: 216.181.1.2
>>
>> The tertiary is our ISP's DNS server. the other two
are
>> local. My users can ping any IP address but they can
>> resolve names. If you Ip config all you'll get the
>> following:
>>
>> IP: 192.168.2.198 (this is within the DHCP scope so
>> that's good)
>> Subnet: 255.255.255.0
>> DNS: 216.181.1.2
>>
>> Obviously my ISP is not going to know that "Jupiter" is
>> 192.168.2.50. Why is my tertiary DNS server being used
>> as not just the primary, but the only DNS server?
>>
>> I tried to go into the VPN Client, leave IP as DHCP and
>> manually configure the DNS settings. After that when
you
>> ipconfig you get the DNS as follows:
>>
>> 216.181.1.2
>> 192.168.2.62
>> 192.168.2.60
>>
>> It's really wacky and all backwards! Pings still work
>> the same.
>>
>> For whatever reason he can resolve the name of one
>> machine that he uses quite often. I'm guessing there
is
>> some local host file that resolves that servername for
>> him.
>>
>> Totally confused. Any advice would be appreciated.
>>
>> Mike
>
>
>.
>



Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: Domain controllers
    ... other DNS was still on the zones transferred to the new domain controller. ... Both DHCP and WINS databases CAN be move -- there are KB ... from one server to another -- search Googgle against Microsoft ...
    (microsoft.public.win2000.active_directory)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... All you need to do is make sure there are no other DHCP servers running on ... The only time I have seen the connectcomputer error you mentioned about DNS ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: MY DNS TROUBLES
    ... Event 5504 is logged when a Windows Server 2003-based DNS server receives a ... This way, the DHCP ... in the DNS correctly. ... Force DHCP to register all records, Forward and PTR, (whether a client ...
    (microsoft.public.windows.server.general)
  • Re: Sending hostname with DHCP
    ... default route and the default dns host. ... Below is my /etc/resolv.conf created by the dhcp client. ... > This seems to depend on the client as much as the server. ...
    (Fedora)