Question on MS VPN Client and DNS resolution
Krish
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
Rahisuddin Shah
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" <no...@no-reply.com> wrote in message
news:r92dnY8YD_vIWWTX...@giganews.com...
Krish
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" <rahisud...@discussions.microsoft.com> wrote in
message news:%23daMKf7...@TK2MSFTNGP02.phx.gbl...
Ace Fekay [MCT]
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/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-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.
Rahisuddin Shah
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" <no...@no-reply.com> wrote in message
news:bsudnTAhK5TK8WHX...@giganews.com...
Krish
You are a genius! It worked. Thanks so much.
Regards.
Krish
"Rahisuddin Shah" <rahisud...@discussions.microsoft.com> wrote in
message news:OggSVx%23YKH...@TK2MSFTNGP06.phx.gbl...
Krish
Thanks for an excellent article. My server is not a DC. But I found the
article to be very useful.
Thanks.
Krish
"Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org> wrote in message
news:uzLm%2349YK...@TK2MSFTNGP04.phx.gbl...
Ace Fekay [MCT]
> 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