Re: Question on MS VPN Client and DNS resolution

When you connect to VPN, how your machine getting IP address?
Are you using DHCP server for IP address or you just have given a range in
RRAS for client IP?

try using DHCP server instead.

thanks
Rahisuddin Shah





"Krish" <> wrote in message
news: ...
> Folks,
>
> I was wondering if you can help me out with this issue:
>
> I have a Windows 2003 server setup as VPN server. Let us call it Beavis.
> Beavis has two nics. Remote Access and VPN service is tied to only one of
> these nics.
>
> 1. When I ping Beavis from my VISTA machine, it pings fine with one of
> the
> NICs' address, 192.168.1.200.
>
> 2. When I connect to Beavis using VPN and ping, it pings with one of the
> address ranges assigned for VPN service's use.
> 192.168.9.10 (I used a different series address for the VPN).
>
> 3. When I disconnect the VPN, I am unable to ping Beavis by name. I can
> still ping Beavis' one of the NICs by its IP address, 192.168.1.200, which
> is not tied to the VPN service. I restarted my DNS client service and am
> still unable to ping Beavis by name.
>
> What can I do to fix this issue? Any help will be highly appreciated.
>
> Krish
>

let try it this way
1. Create a DHCP scope for 192.168.9.0/24
2. Configure the DHCP scope with Gateway, DNS, WINS etc
3. On RRAS server configure RAS to use DHCP Relay and set the DHCP Server IP
Address, RAS will block 10 IPs
4. When client connect to VPN, check the IP Config

It should work. Since I dont have that environment right now so can not test
it.

thanks
Rahisuddin Shah



"Krish" <> wrote in message
news: ...
> Hello Rahisuddin,
>
> Thanks for the reply.
>
> My VPN server allocates IP addresses from a static pool. Can't use DHCP
> because DHCP is already assigning 192.168.1 series numbers to the entire
> LAN.
>
> Okay, let me tell you why I am ysing 192.168.9 series for VPN. Many of my
> colleagues connect to this VPN from outside. Most of them have home
> routers, which typically use 192.168.1 series. This used to mess up their
> routing completely. I switched the VPN client range to use 192.168.9
> series to avoid this issue.
>
> Regards.
>
> Krish
>
> "Rahisuddin Shah" <> wrote in
> message news:%...
>> When you connect to VPN, how your machine getting IP address?
>> Are you using DHCP server for IP address or you just have given a range
>> in RRAS for client IP?
>>
>> try using DHCP server instead.
>>
>> thanks
>> Rahisuddin Shah
>>
>>
>>
>>
>>
>> "Krish" <> wrote in message
>> news: ...
>>> Folks,
>>>
>>> I was wondering if you can help me out with this issue:
>>>
>>> I have a Windows 2003 server setup as VPN server. Let us call it
>>> Beavis.
>>> Beavis has two nics. Remote Access and VPN service is tied to only one
>>> of
>>> these nics.
>>>
>>> 1. When I ping Beavis from my VISTA machine, it pings fine with one of
>>> the
>>> NICs' address, 192.168.1.200.
>>>
>>> 2. When I connect to Beavis using VPN and ping, it pings with one of the
>>> address ranges assigned for VPN service's use.
>>> 192.168.9.10 (I used a different series address for the VPN).
>>>
>>> 3. When I disconnect the VPN, I am unable to ping Beavis by name. I can
>>> still ping Beavis' one of the NICs by its IP address, 192.168.1.200,
>>> which
>>> is not tied to the VPN service. I restarted my DNS client service and
>>> am
>>> still unable to ping Beavis by name.
>>>
>>> What can I do to fix this issue? Any help will be highly appreciated.
>>>
>>> Krish
>>>
>>
>