This is the Test setup with one server and one workstation. Network connection: ZoomX5 DSL --> Switch_A. Server_X & workstation_J(ws_j) connect to Switch_A. Domain Controller (AD): Server_X DHCP & DNS is on Server_X, with ONE NIC. Static IP from the DSL router is 10.0.0.20 DHCP is configuring to 10.0.0.20, with Scope 192.168.0.0 and Address Pool 192.168.0.1 – 254. DHCP is authorized. There is a green arrow. Status is Active. Problem: workstation_j (or ws_j) cannot acquire IP from DHCP. Therefore, I set a static IP of 10.0.0.21. Added ws_j to the domain then restart pc. Changed ws_j NIC IP to DHCP enable, but ws_j cannot acquire DHCP with range 192.168.0.1 - 254. Tested DNS in command prompt with ping and nslookup. The only Warning in Event Viewer is: Event Type: Warning Event Source: DhcpServer Event ID: 1056 Description: The DHCP service has detected that it is running on a domain controller and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This is not a recommended security configuration. Credentials for Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the DHCP Administrative tool. This is for Dynamic DNS. I heard that Dynamic DNS is not very secure. Server_X DNS is for internal use only. Do I REALLY need to set the credentials for Dynamic DNS? Thank for all your help.

Got to hit the books man. "Static IP from the DSL router is 10.0.0.20 DHCP is configuring to 10.0.0.20, with Scope 192.168.0.0 and Address Pool 192.168.0.1 – 254. DHCP is authorized." is wrong DSL router lan should be 192.168.0.1 for gateway. You never include the gateway address nor any static server addresses [or network equipment] in the dhcp scope. Why? Because you don't want dhcp assigning addresses that will conflict with static assignments. "Dynamic DNS is not very secure" what are you talking about? What is "insecure" about ms server dhcp updating MS server dns? The 10.x.x.x network has nothing to do with your 168.x.x.x lan. If I read this correctly this is you Wan ip address. Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

If what I posted is confusing, then let me stated differently. Forget about what I posted ealier. Let me state what I like for this setup and you all assist me on it. Current setup: Servers and clients get IP from Linksys Router. It does not matter if one server goes down. Clients still get access to internet, and access DFS plus file sharing. Please explain the best implementation for the propose setup, .... Propose Setup: 1. Clients get internet and access DFS and file sharing when one of the DC is down or for mantenance. 2. I want Server 2003 DC to provide DHCP to clients. I need more control over client TCP/IP. I only have limited control with Router DHCP. Please give me a detail setup including hardware needed. I have searched all over the net and read through a server 2003 book. It did not mention the setup I needed. Thank you so much everyone.