Emily Bennett
How To Set Up a DHCP Server on Windows Server 2022 Inside Proxmox
If you’re trying to get a proper DHCP server running on your Windows Server 2022 VM inside Proxmox, you might run into some headaches. Maybe the VM’s acting like it’s supposed to hand out IPs, but clients are still stuck with static IPs or aren’t getting anything at all. Or maybe you just want to avoid manual IP management for every device in your network. Setting up DHCP on Windows Server is pretty straightforward in theory, but sometimes the devil is in the details — especially with virtual environments. This guide is all about walking through the steps and throwing in some tips from the trenches to make sure your DHCP actually works.
How to Fix DHCP Not Assigning IPs Properly on Windows Server 2022 in Proxmox
Ensure the DHCP Server Role Is Properly Installed and Authorized
First up, it’s easy to overlook the fact that even if you install the DHCP role, it’s not automatically trusted by Active Directory (if you’re running a domain). You need to “authorize” the DHCP server in AD for it to start handing out IPs to clients, especially in a domain environment.
– Head over to your Windows Server 2022 inside the VM.
– Open the Server Manager (click the Start menu > Server Manager) or just search for it.
– From the menu, go to Tools > DHCP to open the DHCP Management Console.
– Right-click on the DHCP server name (it might show as [your server name]), then select Authorize.
– Wait a moment, then refresh or reopen the console and see if it turns into authorized (it will show a green icon).
This step helps because, on some setups, Windows just refuses to give out IPs until it trusts itself in AD. Think of it like the server’s own way of double-checking if it’s legit.
Check Windows Firewall and Network Settings
Next, firewall issues are more common than you’d think. Even on a fresh install, Windows Firewall might block DHCP traffic on ports 67/68.
– Go to Settings > Update & Security > Windows Security > Firewall & network protection.
– Click Allow an app through firewall.
– Make sure DHCP Server or DHCP service is allowed through.
– Alternatively, manually open ports 67 and 68 UDP in the firewall.
Because, of course, Windows has to make it harder than necessary.
Verify DHCP Service is Running
Sometimes, the service just isn’t running after install.
– Hit Ctrl + Shift + Esc to bring up Task Manager, then go to Services tab, or open Services from the start menu.
– Find DHCP Server and ensure it’s running.
– If not, right-click and select Start.
If DHCP isn’t running, clients won’t get anything.
Reboot and Recheck
Sometimes, just rebooting the VM after setting everything up makes a huge difference. Not sure why it works, but on some setups, it’s like Windows has to get its ducks in a row.
– Restart your Windows Server VM inside Proxmox, then check again if clients are receiving IP addresses.
Create a New DHCP Scope Carefully
If DHCP is running but it’s not handing out addresses properly, double-check your scope configuration.
– Open DHCP Management Console (Start > Windows Administrative Tools > DHCP).
– Right-click IPv4 and pick New Scope.
– Give it a memorable name, then set your start and end IP addresses — make sure the range fits within your network’s subnet.
– Set the subnet mask.
– Don’t forget to specify the correct Default Gateway (your router’s IP).
– Also, if you’re using VLANs or multiple subnets, ensure your DHCP scope matches the actual network.
– Activate the scope immediately. If you don’t, clients won’t get IPs!
Check Network Connectivity and Virtual Network Settings
In Proxmox, VM networking is another common cause of DHCP failures.
– Verify that your VM’s network interface is attached to the correct virtual bridge or VLAN.
– Make sure the VM’s network adapter (virtio, e1000, or Intel e1000e) is compatible with your network setup.
– Confirm that your physical network gear isn’t blocking DHCP broadcast packets (some switches/security settings can block or filter DHCP traffic).
– You can use a command like `ping ` or `ipconfig /all` inside the VM to confirm it has network connectivity.
Check the DHCP Server Logs
If things still aren’t working, look into the DHCP logs:
– They’re typically located in `:\Windows\System32\dhcp`.
– See if there are errors or requests coming in.
Sometimes, you see requests, but the server’s just not responding, which points to misconfiguration or firewall issues.
Extra: Make sure the Virtual Network isn’t Isolated
Also, Proxmox’s network setup can isolate your VM from the host or other network segments.
– If your VM’s network is on an internal or host-only network, DHCP requests might never leave the VM.
– Switch to a Bridged mode (like VT network bridge) so your DHCP server can talk to actual devices.
Wrap-up
Getting DHCP working on Windows Server 2022 inside Proxmox probably involves a few layers — install, authorize, firewall, network, and scope. Sometimes, it’s the little details, like forgetting to authorize the server or accidentally blocking ports. After fixing those, things usually fall into place. On one setup, it worked right after a reboot; in another, I had to double-check the VLANs and network adapter types.
Summary
- Authorize the DHCP server in Active Directory
- Check Windows Firewall and port access
- Ensure DHCP service is running
- Verify network connectivity and VM network settings
- Configure the DHCP scope accurately and activate it
- Review DHCP logs if issues persist
Conclusion
Once those fundamentals are covered, DHCP usually plays nice and hands out IPs without fuss. The common pitfalls are mostly around authorization and network blocking — all of which can be checked with a few clicks or commands. Hopefully, this saves some time wrestling with it on your end. Fingers crossed this helps!