We have a server running Windows Server 2008. It runs DC, DNS etc and has RRAS configured. Users can VPN OK, with no issues. Under normal operation server can be found at .3, however once a VPN user connects, a new DNS record is created, .90, and any attempts to access the server via path name (\server) are reouted to .90 instead of .3. As .90 isn't the server but the VPN, users mapped drives no longer work. Deleting the DNS entry at .90 solves the problem again until the next time the VPN is logged in, in which case the DNS record is recreated and all the problems occur again.
To solve this, we have moved the RRAS to another server running 2003. This does not create a new DNS record. As far as I can tell, this is a Server 2003 v 2008 difference, and 2003 does not put a new record into the DNS.
Can anyone shed any light on this? Why does 2008 add a DNS record and 2003 does not? Is there a way to disabled 2008 putting another record in the DNS and thus prevent breaking the internal network?
Thanks, Andy
Best Answer
See if this works.