Enabling DHCP across non–RFC 1542 router: Sales and Engineering are on separate subnets; Sales1 and Engineering1 run DHCP. The router cannot relay DHCP/BOOTP. How can you allow each DHCP server to support clients on the other subnet?

Introduction / Context:
DHCP broadcast packets do not cross routers unless the router supports BOOTP/DHCP relay (RFC 1542). When a router lacks relay capability, a Windows server on each subnet can act as a relay agent to forward DHCP requests (broadcasts) to the appropriate DHCP servers via unicast.

Given Data / Assumptions:

• Two subnets: Sales and Engineering.
• Sales1 and Engineering1 are DHCP servers; the router does not relay.
• Servers Engineering2 and Sales2 are available on each subnet.

Concept / Approach:
Deploy the DHCP Relay Agent (a Routing and Remote Access Service component) on one Windows server per subnet. Configure each relay to forward client broadcasts to the IP addresses of the DHCP servers. This enables cross-subnet leases without changing the router.

Step-by-Step Solution:

Verification / Alternative check:
Monitor DHCP server logs for relayed requests from the other subnet and confirm clients obtain correct scopes and options.

Why Other Options Are Wrong:

• Router option in scopes does not make the router a relay.
• RIP enables routing but does not translate/forward DHCP broadcasts.
• Running extra DHCP servers without scopes is ineffective and can cause conflicts.

Common Pitfalls:
Forgetting to add all DHCP server IPs in the relay agent or not binding the correct interface will prevent forwarding.

Final Answer:
Install and configure the DHCP Relay Agent service on Engineering2 and Sales2