DNS and RAS on windows 2k3

[mark]

Hi,

I'm running a VPN server on our windows 2003 server domain controller
along with DNS, DHCP and Active Directory. I recently ran a windows
update (the last update would have been in May) and I started to
encounter networking problems.

The windows XP machines on my network started accessing the domain
contoller by a different ip address. I tracked this to a message in the
event log saying that RAS had acquired ip address 192.168.0.24 to be
used on the Server Adapter (event id 20088). Looking in the DNS
records, the server now had two ip address, what RAS had chosen and the
original 192.168.0.1.

I tried changing RAS to use a pool of address intead of DHCP, but it's
now changing the address to be 192.168.0.100 instead. The problems
occur because client machines try to use the RAS ipaddress ahead of the
real ip address and run in to problems because they can't authenticate
users, or access the web server running on the server.

I'm sure that RAS is meant to acquire an ip address for the server
adapter, but how do I prevent the LAN machines from using this as the
default?

thanks!

Mark

 

[Robert L [MS-MVP]]

Correct. Enabling RRAS make the DC as multihomed server and you may have a connection issue. what you may do is Disable NetBIOS for all RRAS connections. check this page for the details.

Name resulotion on VPN
Name Resolution and Connectivity Issues on W2K Domain Controller with RRAS and
DNS Installed "No domain server was available" while the dialup connection is ...
www.chicagotech.net/nameresolutionpnvpn.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi,

I'm running a VPN server on our windows 2003 server domain controller
along with DNS, DHCP and Active Directory. I recently ran a windows
update (the last update would have been in May) and I started to
encounter networking problems.

The windows XP machines on my network started accessing the domain
contoller by a different ip address. I tracked this to a message in the
event log saying that RAS had acquired ip address 192.168.0.24 to be
used on the Server Adapter (event id 20088). Looking in the DNS
records, the server now had two ip address, what RAS had chosen and the
original 192.168.0.1.

I tried changing RAS to use a pool of address intead of DHCP, but it's
now changing the address to be 192.168.0.100 instead. The problems
occur because client machines try to use the RAS ipaddress ahead of the
real ip address and run in to problems because they can't authenticate
users, or access the web server running on the server.

I'm sure that RAS is meant to acquire an ip address for the server
adapter, but how do I prevent the LAN machines from using this as the
default?

thanks!

Mark