Re: Question on MS VPN Client and DNS resolution

"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
>


This is because of the multiple registrations for the server name in DNS. It
is using Netmask ordering, which will provide the closest subnet in a
response. This is default, and something you do not want to change.

There are ways around this, that include registry modifications, however,
what concerns me is if this Windows 2003 server is a DC. If it is, it will
require quite a few registry changes to make it work. This scenario is
called a multihomed DC (it has more than one NIC, IP address, and/or RRAS is
installed on the DC). THis is problematic scenario and configuration. This
is because of the way AD and DNS work. If this is a DC, please read the
following blog for a complete understanding of what is going on, reasons why
it works, and your options.

Multihomed DCs with DNS, RRAS, multiple IPs, and/or PPPoE adapters
http://msmvps.com/blogs/acefekay/arc...-adapters.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"Krish" <> wrote in message
news: ...
> Hello Ace,
>
> Thanks for an excellent article. My server is not a DC. But I found the
> article to be very useful.
>
> Thanks.
>
> Krish

Good to hear. I hope it was helpful to resolve the issue. With a non-DC
and/or non-DNS server, you can simply uncheck the 'register this connection'
checkbox in the NIC properties that you do not want to register into DNS.
But as you read, a DC is much more complicated.

Cheers!

Ace