2 DHCP on same subnet

I wonder if its possible to choose from where to pick up ip-adress.My scenario:
Dlink router with dhcp for all equipment in house. Ip range 192.168.0.100-192.168.0.200
Homelab: Active Directory with dhcp+dns. Dhcp scope with ip range 192.168.0.50-192.168.0.99.
If a client join the homelab , is it possible to pick up the ip from the dhcp scope instead of the router?
Thank You.

I'll explain my setup if it can be of any use to you
I have limited router coverage, so I have two
one operating on 192.168.0.xxx
the other on 192.168.3.xxx
each is clearly identified any so you know which you are logging on to
and receive the appropriate ip address
separating them more widely like this , I don't have to mess with the masks
which is what I think you have to do
to make your setup work properly

...T

Once you go Slack, you never go back!
Slack since 1995

Stop hovering to collapse...Click to collapse...Hover to expand...Click to expand...

I wonder if its possible to choose from where to pick up ip-adress.My scenario:
Dlink router with dhcp for all equipment in house. Ip range 192.168.0.100-192.168.0.200
Homelab: Active Directory with dhcp+dns. Dhcp scope with ip range 192.168.0.50-192.168.0.99.
If a client join the homelab , is it possible to pick up the ip from the dhcp scope instead of the router?
Thank You.

Click to expand...

"Active Directory"..........so it is a Domain controller and every machine in your house logs in to the Domain???
You do not need to have another DHCP in the router. Shut is down. I have 11 machines at home. I do not use Domains anymore, even though I run WIN2K8 R2 with my mail server on it.
My Cisco router handle IP's for anyone, including wireless clients.

Not sure what your current set up is. You appear to have slpit addresses in the same subnet. You do not have a subnet, unless your mask is away from classful behaviour.

I'll explain my setup if it can be of any use to you
I have limited router coverage, so I have two
one operating on 192.168.0.xxx
the other on 192.168.3.xxx
each is clearly identified any so you know which you are logging on to
and receive the appropriate ip address
separating them more widely like this , I don't have to mess with the masks
which is what I think you have to do
to make your setup work properly

...T

Click to expand...

For what you are saying, you already have two very different and distinctive networks...........(provided you use the standard classful mask for class C address space= 255.255.255.0). So you have networks 192.168.0.0/24 and 192.168.3.0/24.

Ideally, a 'lab' should be its own segment. Two differently-configured dhcp on the same wire is just asking for headaches. Your clients will get IP, dns and gateway from whichever of them responds first.

“Those who desire to give up freedom in order to gain security will not have, nor do they deserve, either one.” - Benjamin Franklin
"I gave what was the least untruthful answer" - James Clapper, previous US Director National Intelligence, explaining why he lied to Congress
"If you have nothing to hide, you have nothing to fear" - Barack Hussein Obama, previous US President
"You have nothing to fear if you have nothing to hide" - Joseph Goebbels, Nazi Minister of Propaganda and Enlightenment​

Stop hovering to collapse...Click to collapse...Hover to expand...Click to expand...

Will try to be more clearly
My configs are as described above, but the router is giving the ip's
I am asking, is it possible, when a client connects to my domain controller "homelab", can the client get its ip from the Dhcp scope with ip range 192.168.0.50-192.168.0.99 instead of the router?
If I must choose 2 different segments, can my computer have access to both networks?
If it's too bad solution with my idea, any suggestion is appreciated.
Thank You

Just turn off DHCP in the router and the clients will start getting their IP addresses from whatever other DHCP server is serving that subnet. So if HomeLabDC01 is your DHCP server and the scope is active and authorized in AD clients will start getting DHCP from there even if they are not attached to AD. DHCP doesn't care about a domain it is broadcasting "IPs, I have IPs", like a vendor at a football game selling beer. It is only doing it on the subnet the scope is advertising. So if you are advertising 192.168.0.50-99/24 then clients will only get an address in that scope unless you get fancy and start using VLANs.