I just came on board with a company and they have in "interesting" scenario. I'm in the North American Division and we have about 100 users throughout our branches all over the US. They are/were in the process of implementing an MPLS (Verizon PIP) network which is nice, however they have always been on a STATIC IP addressing scheme, even for PC's etc. So right now there are 7 branch offices all static, set up as follows.
Site 1 - 192.168.145.0/25 - NYHQ (my location) GW- 192.168.145.1
Site 2 - 192.168.142.0/25 - NY2 GW-192.168.142.1
Site 3 - 192.168.142.128/25 - Atlanta GW -192.168.142.129
Site 4 - 192.168.141.128/25 - Chicago - GW 192.168.141.129
Site 5 - 192.168.144.128/25 - LA - GW 192.168.144.129
Site 6 - 192.168.144.0/25 - SanFran - GW 192.168.144.1
Site 7 - 192.168.143.0/25 - Houston - GW 192.168.143.1
Currently there are 3 DC's that users at these locations authenticate to which are in NYHQ, LA, and Chicago. These are also the DNS servers.
Is it possible to move from Static addressing above to DHCP using only these 3 boxes?
Each of the 7 sites has a router provided by Verizon during the PIP installation which is the Default Gateway for these sites, configured STATICALLY on each box.
I can't think of any straight forward or "nice" way of getting to DHCP.
I was messing around earlier and since I have one of the DC's in my office, i added the DHCP role to it (2008 server), set up a scope 192.168.145.0/24 with the correct DNS settings, and GW etc. It handed out a DHCP address to a windows 7 machine i had on the network, but the Win7 box didn't allow internet access and I couldn't even ping the GW or DC.
Any suggestions (aside from the routers doing DHCP)? Not having DHCP for PC's is a nightmare when having them spread out through the entire country, not to mention trying to keep track of each machines IP in a spread sheet.
Thanks in advance! Let me know if you need more info.
-reminder: I walked into this, no idea why it's configured this way