Hi, I have just setup a new lab in my house, basically i have a domain controller which has hyper-v machines on, DNS, RRAS, NPS amd DHCP.
The problem is that i have just switched off my routers DHCP server and now devices aren’t able to receive addresses from this server for a reason which i have no clue about!
I have configured a dns dynamic update credentials account and configured in the DNSUpdateProxy group along with entering their credentials on the DHCP section to.
I’m looking at wireshark and all it is giving out is discover messages from the devices that are requesting an address.
On the RRAS server i have 4 ports, 3 for VPN and 1 for PPPoe and have configured the server to use DHCP on the IPv4 tab.
When i logon to a hyper-v machine, unless those accounts have previously logged on i cannot logon to them to because network connectivity is limited!
I’m genuinely stumped and need this sorted pretty quickly to be honest!
P.S, the event logs are showing no signs of errors and kerberos seems to be giving my dns dynamic update credentials account tickets successfully to which would indicate there is no problem with the account!
4 Spice ups
Your DC is running on physical with the hyper-v role installed? The DC should be a VM.
If your machines are domain joined, can you ping the Hyper-V box? Can you ping the DC?
Is everything on the same subnet or different subnets?
Everything is on the same subnet but the hyper-v machines are domain joined and are not getting addresses along with every other device that isnt domain joined such as tablets etc…
This would all work if i just switched my routers DHCP server back on but i dont want to do that, i want my hyper-v machines etc… to all get addresses from this DHCP on my DC.
I’d like to add that my DHCP server on my DC did work when my router DHCP’s server was on to…strange!
You may need to uncheck the dhcp guard in your vm settings for the dhcp server. If all network adapters on the same network as your dhcp server that should do it. If not, you need to enable dhcp relay on your switch or router.
Also make sure your dhcp server has a static ip on the same network as everything else. Your hyperv host also needs a static ip as well… Because that starts up before the VMs on it, which includes your dhcp server.
1 Spice up
Hi, I have just setup a new lab in my house, basically i have a domain controller which has hyper-v machines on, DNS, RRAS, NPS amd DHCP.
Your bare metal should have only Hyper - V role, and can’t be a DC. Better keep your DC as a VM on it.
The problem is that i have just switched off my routers DHCP server and now devices aren't able to receive addresses from this server for a reason which i have no clue about!
Does other machines joined on the DC ?. Firewall or any AntiVirus blocking issue ?. Does client machines pinging the DC with name and IP ?
Okay so after a LOT! of digging, i think i found the problem. A setting on a GPO had been configured on the firewall settings on the domain profile to block incoming connections. Obviously this was being applied to my DC as well and thus was the reason why my hyper-v host couldn’t contact the DNS on it. What a nightmare!
