A different VPN/DHCP/DNS routing issue

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

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" <(E-Mail Removed)> wrote in message
news:6d5601c475a4$d3ee1b60$(E-Mail Removed)...
> 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

Hi Mike,
before you start testing DNS name resolution on client machine after DNS
reconfigurations always use first "ipconfig /flushdns" command which purges
the DNS resolver cache.

To verify DNS name resolution on client machine use command "nslookup
servername_to_ping" rather than ping command.

Ros

"Mike Busch" <(E-Mail Removed)> wrote in message
news:6d5601c475a4$d3ee1b60$(E-Mail Removed)...
> 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

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" <(E-Mail Removed)> wrote in message
>news:6d5601c475a4$d3ee1b60$(E-Mail Removed)...
>> 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
>
>
>.
>

Okay I tried your suggestion. But here's the interesting
thing. I have a server named Jupiter. It's just a file
server whose IP is 192.168.2.50. For whatever reason
that particular server is having trouble resolving even
though it's sister server, Saturn(same server with a
192.168.2.44 IP) has no problems resolving. Last night
on VPN I could not get to Jupiter, but I could get to
Saturn. this morning I could get to both via VPN. After
running the "ipconfig /flushdns" command I once again can
get to Saturn, but not Jupiter. here's some info:


C:\Documents and Settings\buschman>ping jupiter
Ping request could not find host jupiter. Please check
the name and try again.


C:\Documents and Settings\buschman>ping 192.168.2.50

Pinging 192.168.2.50 with 32 bytes of data:

Reply from 192.168.2.50: bytes=32 time=48ms TTL=127
Reply from 192.168.2.50: bytes=32 time=44ms TTL=127
Reply from 192.168.2.50: bytes=32 time=24ms TTL=127
Reply from 192.168.2.50: bytes=32 time=55ms TTL=127

Ping statistics for 192.168.2.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 55ms, Average = 42ms


C:\Documents and Settings\buschman>nslookup saturn
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 68.48.0.12: Timed
out
Server: nscache01.inflow.pa.bo.comcast.net
Address: 68.87.96.15

*** nscache01.inflow.pa.bo.comcast.net can't find saturn:
Non-existent domain


C:\Documents and Settings\buschman>ping saturn

Pinging saturn [192.168.2.44] with 32 bytes of data:

Reply from 192.168.2.44: bytes=32 time=23ms TTL=127
Reply from 192.168.2.44: bytes=32 time=24ms TTL=127
Reply from 192.168.2.44: bytes=32 time=24ms TTL=127
Reply from 192.168.2.44: bytes=32 time=22ms TTL=127

Ping statistics for 192.168.2.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 24ms, Average = 23ms


C:\Documents and Settings\buschman>nslookup saturn
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 68.48.0.12: Timed
out
Server: nscache01.inflow.pa.bo.comcast.net
Address: 68.87.96.15

*** nscache01.inflow.pa.bo.comcast.net can't find saturn:
Non-existent domain

C:\Documents and Settings\buschman>

Just FYI I am using Comcast at home as my ISP.

Any help would be appreciated.

Mike




>-----Original Message-----
>Hi Mike,
>before you start testing DNS name resolution on client
machine after DNS
>reconfigurations always use first "ipconfig /flushdns"
command which purges
>the DNS resolver cache.
>
>To verify DNS name resolution on client machine use
command "nslookup
>servername_to_ping" rather than ping command.
>
>Ros
>
>"Mike Busch" <(E-Mail Removed)> wrote in message
>news:6d5601c475a4$d3ee1b60$(E-Mail Removed)...
>> 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
>
>
>.
>