I have a small office setup with four domain controllers, about 60 domain-joined computers, around 20 laptops (which are not domain-joined), and approximately 40 mobile devices. All desktops are set with static IP addresses between 192.168.0.20 and 192.168.0.100, with a default gateway of 192.168.0.1 and DNS at 192.168.0.11 and 192.168.0.12. We also have two unmanaged D-Link switches with 48 and 24 ports.
Currently, we use a load balancing router with an IP of 192.168.0.1 that provides DHCP services for the IP range from 192.168.0.161 to 192.168.0.240, which connects to Wi-Fi laptops and mobile devices.
As our number of desktops grows, we're considering setting up a DHCP server on a Windows Server 2019 machine. My questions are:
1. Is it possible to configure the DHCP server on the Windows Server with a scope from 192.168.0.20 to 192.168.0.100 just for the desktop machines? How do I configure the desktops to obtain IP addresses via this new DHCP server? Also, how do I ensure that the Wi-Fi laptops and mobiles receive their IPs through the router?
2. Can I have two DHCP servers with overlapping IP ranges on the same network? If so, what's the best practice for setting up the DHCP server? Should I run it on the server or keep it on the router? Thanks in advance!
5 Answers
To have your desktops obtain addresses from the new DHCP server, you just need to set them to use DHCP in their network settings. For the laptops and mobiles, you'd typically configure an IP helper on your router to forward DHCP requests to your server.
However, having two DHCP servers on the same subnet with overlapping scopes is a recipe for disaster. You’ll just get lots of IP conflicts and erratic behavior! If you must have two servers, ensure they have distinct scopes.
Having two DHCP servers on the same network serving the same range can lead to conflicts. Generally, if you want to use two DHCP servers, they should be configured for failover. It's unusual to have one serve only desktops and another for mobile devices unless you specifically need that for isolation.
If your router’s DHCP capabilities meet your needs, it might be easier to stick with that for now. Otherwise, the Microsoft DHCP server gives you more features and meshes well with Active Directory.
Segregating your network for different devices is definitely a good idea. It helps with managing traffic, security, and efficiency. If integration is a challenge, it might be time to look into upgrading to hardware that can better handle multiple segments and DHCP configurations.
If you're managing the router, consider splitting your network into different segments for workstations and mobile devices. This way, each segment can have its own DHCP scope. Just make sure that random MAC address generation on the laptops doesn’t happen, as this can cause issues with leases and IP assignment.
You really shouldn’t run two DHCP servers unless absolutely necessary. It complicates things. One DHCP server can effectively manage everything if set up correctly, and it can reduce IP conflicts. If there's significant growth, consider restructuring your network to segment devices by type for better control.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures