my w2k3 LAN consists of 3 routers, with which i want to segments the network into 3 subnets ( 192.168.1.0, 192.168.2.0, 192.168.3.0). these three subnets are within one physical location. i have a w2k3 domain controler with dhcp server configured. this dhcp is configured with 3 scopes for each of these subnets. also these routers addresses are configured according to the order above. and on the dhcp console, the individual subnets scope options are configured and pointed to the various routers in each subnet. but the problem is that all nodes in the entire LAN recieves 192.168.1.x address. how do i properly address this issue

You should let the routers provide dhcp to their subnets. Or... http://support.microsoft.com/?kbid=... Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

One of the routers are providing the ip address would be my guess. Disable the dhcp service is the device that is providing the 192.168.1.x range. You would want the 2003 server to provide dhcp as you can provide much more control over the clients as well as a greater range of dhcp services.

the thing is that i want to centralize dhcp deployment from the w2k3 server. currently all the routers are disabled to issue ip addresses. but all these machines are recieving their ip address just from scope1. while no addresses are being deployed from scope2 and scope3 (i.e 192.168.2.0, 192.168.3.0 respectively) which are in the dhcp console - w2k3 server. as i said before i configured scope1 pointing it to router1, scope2 pointing it to router2 and configured scope3 pointing it to router3. but things are not working as expected.

Think about it for a minute. A dhcp request is a broadcast. How is the dhcp server going to know who gets what ip address? There is no way in MS dhcp server that I know of EXCEPT to do ip reservations. This is where you use dhcp to statically map a ip address to the mac address of the workstation. This is why I suggested you do dhcp from your routers so each router would serve their own subnet. It's a common practice. Alternately you can [quoted from the link I provided] "A DHCP (Dynamic Host Configuration Protocol) server can provide IP addresses to clients spanning multiple subnets if the router that separates them can act as an RFC 1542(BOOTP) relay agent. If the router cannot function as relay agent, each subnet that has DHCP clients requires a DHCP server." See if your routers support boottp and the relay agent. Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

you need to add a NIC on the server for each segment and connect each network card to the router and give each network card on the server a static ip according to the segment so NIC 1 Would have 192.168.1.x connected to the router in segment 1 and NIC 2 Would have 192.168.2.x connected to the 2nd router in segment 2 and NIC 3 Would have 192.168.3.x connected to the 3rd router in segment 3 that should do the trick

thanks Wonderer, but allowing the routers to assign the ip addresses already has defeated the real aim of a centralized management. you see; this network will grow about 4 times in size shortly, spanning a couple of buildings within the same location and i worry of losing the ablility to manage the network from a single point. ok you mentioned relay agent. so if i configured the routers to act that way does it mean these various subnets will be assigned ip addresses according to the various Scopes configured in the dhcp console? i want to get that clear