Running Windows Server 2003 Enterprise Edition x64 behind a Linksys RV0041 router.
The OS is running a DHCP server for scope 192.168.0.10 - 192.168.0.254 (no static reservations)
The router is running a DHCP server for scope 192.168.1.100 - 192.168.1.199 (no static reservations)
The two systems permanently connected to the router have, in the TCP/IP settings for their LAN connections, static internal IP addresses corresponding to the scope controlled by the router.
My remote XP Pro system, when connected via VPN (also managed by the server OS), is assigned an IP like 192.168.1.206, which is not technically in either of those pools, so I'm not sure what is going on there.
Not only do I think two DHCP servers are unnecessary and possibly conflicting (please correct me if I'm wrong), but our DNS server (managed through the OS) has never consistently responded to remotely (VPN) connected requests for DNS names: from my remote XP Pro system, when connected to the network via VPN, I can navigate to \\192.168.1.x\share\... but not to \\server\share\... However, systems physically on the network can refer to servers by their DNS names (in TCP/IP for those network connections, localhost or the IP of the server hosting DNS is specified as the DNS server).
I would like to consolidate the DHCP servers to one and do it the right way, and hopefully resolve this DNS issue in the process. I hope one or more of you can help me do this the right way so that I don't screw anything up, as the servers are physically located some 200 miles from where I am right now.