DHCP Question

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Hello Everyone,

I need some help....again. Being a noob is rough.

I plan on running a split scope scenario for some DHCP redundancy.

My DC's are on different networks, 172.18.2.0, and 172.18.4.0.
172.18.4.0 is the network using DHCP, the .2 network is all static and does not require DHCP.
This might be a total noob question but can I add a .4 network scope to the DC on the .2 Network, and have it work fine? Is there anything else I would need to do?

 

We have a switch sitting inbetween both networks with Bootp enabled.. will that allow IP requests from the .4 network to reach the DHCP server on the .2 network?

 

It should do yes.

 

Superscope?

 

Not much point in a superscope, as the .2 network is all *static*

 

Hey Sparky,

I didn't even know that was an option, what do you mean exactly? If I added the DHCP role to the DC on the .2 network it would act as a backup server servicing the .4 clients with IPs?

 

I see! Well I'll defeintely look into that option, although I think my manager would have a hernia if I even suggested setting up DHCP for the .2 network (Lots of internal apps hardcoded to point to static ips on the 2 network)

Thanks very much Sparky and Bluerinse!

 

I can't seem to get this to work. I don't think the DHCP requests are reaching the .2 network's DC, but I'm not sure.
Aside from making sure Bootp is configured correctly on the switch, is there anything else I need to do to get this working?

 

Hey Sparky,
For testing I pause DHCP on the .4 network server, then proceed to release and renew. No IP address is assigned, the client just ends up with the 169 private address.

 

When my manager originally asked me to do this the first thing I thought of was a relay agent, but I had only read about it in passing and have no Idea how to set one up. Is it pretty straight forward?

My Boss is more of the network admin, he manages the switches so I'll have to ask him about the BOOTP options, he just simply told me it was enabled, I don't know if it's just forwarding or relaying, looks like it isn't doing either right now.

And yes there is full resource access between the .2 and .4 network, printers, shared folders, RDP, ping etc.

 

Yeah I'm thinking the problem's on the switch, hopefully the switch can be fully configured to act as the relay agent and direct DHCP/BOOTP traffic directly the .2 network DC, I'll have to wait until my manager has time to check it out.
Thanks again Sparky

 

When configuring the switch you need to specify where the dhcp servers are configured, so as you want it to have redundancy you will add 2 dhcp servers, if the one fails it will go to the next one.
Obviously you will need layer 3 routing if the dhcp server is on different subnets.