tomdevlin
asked on
DNS - Windows 2K3 Domain Controller Resolving to Wrong IP Address
I have a Windows 2K3 Domain Controller(Server1A) that is also running Routing and Remote Access, so my users can make VPN connections. The NIC card of this server is configured static for 192.168.1.249. The internal address under RRAS -> IP Routing -> General is 192.168.1.150. When I do an NSLOOKUP for server1a both these addresses are displayed. Server1A is also identified on my DNS Server (same box) with a separate for both addresses. The problem is that many my client machines (XP SP2) are seeing 192.168.1.150 when I ping server1A. This causes my logon script not to run and also causes problems accessing network shares. I think the solution may be to delete the 192.168.1.150 record on the DNS, but I am hesitant to do this because I do not know the impact this may have on RRAS. So I am looking for advise on how to get server1A to consistently resolve to 192.168.1.249 without messing up my RRAS setup. Thanks for your indulgence on these newbie questions
Is this machine multi homed?
ASKER
No. It has only one NIC card with the single IP of 192.168.1.249.
So what interface is assigned the .150 address? Is it a secondary IP on the server's nic? I would change the RRAS to use the default IP f the server and drop that other a record.
ASKER
x.150 is the first address in the static address pool configured on the RRAS server for VPN clients. It is not a secondary IP on the server's NIC. This is what is puzzling, because x.150 is showing up on the DNS server.
Drop the record and see what happens. You can always add it back.
ASKER
Dropping the record solves the problem (but only temporarily) and does not interfere with the functioning of RRAS. This problem is specific to servers which are running RRAS and DNS or WINS. The problem is that the IP address of PPP connection established when a VPN client connects is picked up by DNS and/or WINS. The server name is sometimes incorrectly resolved to the PPP IP instead of the true IP of the server causing problems connecting to shares and logon problems (in this case because it was my DC/GC). The solution involves deleting the PPP IP record from DNS and WINS + making the registry changes described in this MS article 292822. Hope this help anybody else how has this same problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have this exact same issue, would the original poster please note on if this was ever fixed?