Two domains on one network

[detjo]

Why can’t two domains use the same network if DHCP is split to manage it?

 

Server 1: abc.com 192.168.1.1

DHCP: 192.168.1.2 - 125

 

Server 2: xyz.com 192.168.1.254

DHCP: 192.168.126 - 253

 

All on the same physical network in the same building, and users choose which domain, at login.

 

Or does that all fall apart because windows will only allow a computer to be a member of one domain?

[Steve21]

I mean for all intent and purpose they can It's trusted domains/forest etc (Not quite in the method you're talking as DHCP etc would run before the machines are logged in etc)

 

Or did you want the domains fully split, but just with an option to login to one or another?

 

Steve

[Roberto]

Why can’t two domains use the same network if DHCP is split to manage it?

 

Server 1: abc.com 192.168.1.1

DHCP: 192.168.1.2 - 125

 

Server 2: xyz.com 192.168.1.254

DHCP: 192.168.126 - 253

 

All on the same physical network in the same building,

 

All absolutely fine. You need to think about how DNS would work here - the DHCP server would need to send a DNS server address to the clients that could serve both domains but that’s perfectly do-able. Not even sure why you’d need to “split” dhcp (whatever that means exactly?).

 

and users choose which domain, at login.

 

Or does that all fall apart because windows will only allow a computer to be a member of one domain?

 

Ah. This is a problem. The computer can only be a member of one domain, so you’d have devices on one domain or the other and only allowing user logins from their respective domains if they were separate domains. This used to be a common scenario in education; separate ‘administrative’ and ‘curriculum’ domains and users totally used to be a thing.

 

However... what is possible is to have one AD forest containing multiple domains, where users from anywhere in the forest can log into domain devices anywhere in the forest.

 

I’d ask what problem you’re trying to solve here, any setup along the lines above are going to be a more complicated setup for you to design and support and for users to use than just having one domain. I’m willing to bet that this could all be solved, with careful design, in just one domain.

[Sydders01]

Hi @detjo I don't know for sure what you are trying to achieve but You can have two domains , a trust between them ,install Dhcp on only one of them and set your ranges .

[Protec]

Why do you have 2 Domains?

[fredbayker]

As @Sydders01 said, you can have a trust between the domains and your users would be able to login as long as they specified the domain either with the UPN or domain\username format.

They don’t need to be in the same forest to achieve this.

[Davit2005]

Why can’t two domains use the same network if DHCP is split to manage it?

 

Server 1: abc.com 192.168.1.1

DHCP: 192.168.1.2 - 125

 

Server 2: xyz.com 192.168.1.254

DHCP: 192.168.126 - 253

 

All on the same physical network in the same building, and users choose which domain, at login.

 

Or does that all fall apart because windows will only allow a computer to be a member of one domain?

 

trust relationship is prob the best way to do this, as long as the users are capable of pre-fixing the other different domain. Join the PC to the main one that is going to be used and then if the other domain needs to be used the just prefix it i.e xyz\USERNAME

 

I'd echo others and ask why, are you migrating to a new domain, is there 2 different orgs using same PCs?

Edited September 21, 2020 by Davit2005