Using the DHCP helper (relay) feature will work. You can set up the multiple DHCP scopes on one or two (for redundancy) servers and the clients will pull the correct DHCP scopes when they hook up. Most modern desktop/laptop clients can handle the switch gracefully as they move from subnet to subnet. This is a common scenario.
Putting in DHCP is worth the effort. It will drastically reduce your day-to-day IP address maintenance. *********************** Charlie Kaiser charl...@golden-eagle.org Kingman, AZ *********************** > -----Original Message----- > From: Matthew W. Ross [mailto:mr...@ephrataschools.org] > Sent: Thursday, July 23, 2009 10:38 AM > To: NT System Admin Issues > Subject: DHCP and multiple Subnets; Multiple DHCP server or > DHCP-Relays? > > Hey list. > > Since nobody had a good network mailing list, I'll as my > question here. > > We have a large flat network which I'm looking at splitting > up. It was 10.x.x.x/8, looking to bring it to several > 10.20.x.x/16s. I've got my configuration of the router > figured out, except DHCP. We statically assign our IPs to > individual machines... but I don't see how that's possible > with a routed network like this... especially for mobile > users who move across subnets from time to time. > > I could install a DHCP server for each subnet, but this could > be tedious. Using my switch's DHCP-Relay seems like a good > idea, but if a user moves to a different subnet, won't that > user get an invalid IP address? > > Any other ideas on how to get past this? > > > --Matt Ross > Ephrata School District > > ~ Finally, powerful endpoint security that ISN'T a resource > hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
