DHCP, DNS Problem, IP coming from wrong DHCP server

Hello,

My head really hurts with this one. I have 2 SBS Sites.

Site one Server IP address 10.0.0.2 - DHCP running on network

Site two Server IP address 192.168.0.1 - Static ip addresses on
network, small site. VPN dial in connections are given out from range
192.168.0.201 and above.

Both of these sites are connected over a VPN link in ISA server.

What I'm finding in the last few days though is that the DNS server on
site one is showing references for 192.168.0.201, then 202 etc which
link back to the servername of site one ... which should be 10.0.0.2

What then happens is that some of the XP machines then try to resolve
the servername back to one of the 192.168.0.x addresses which then
effectivly puts them off the network.

Removing the entry from the DNS and rebooting the XP machine cures it
for a few hours or so.

Ive checked the LAT on site one and all thats in there is the 10.0.0.x
range.

Any idea where I can go from here?

Rgrds,
JOn

 

Hi,
This seems to be the issue described on the following KB article:

292822 Name resolution and connectivity issues on a Routing and Remote
Access
http://support.microsoft.com/?id=292822

The changes mentioned there should help avoid the server registering its
RRAS interface on DNS causing name resolution issues.
What most likely is happening is that your RRAS server is configured with a
static pool on the 192.168.0.x (most likely starting in the 200 range)
network also and it is assigning those IPs to the remove VPN connections.

In regards to the LAT, I would add the 192.168.0.x remote network if you
want them to have full access to the resources through that interface.

Regards,
Damian

--
Damian N. Leibaschoff, MS IST, MCSE
Microsoft Corporation

Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via

your newsreader so that others may learn and benefit

from your issue.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

Many thanks for the pointer Damian. I've just made the changes and
hopefully this will resolve the issue.

Rgrds,
Jon