Issues with Windows DHCP Server
-
Hi All,
I’ve recently deployed FOG into it’s own subnet - and things are working great there where FOG is allowed to run it’s own DHCP server.
However I’d like to start moving machines out onto other subnets, which we manage via Windows DHCP Server.
I’ve configured Option 66 and 67, as well as option 150 (hoping that would fix things!) but the machine boots from the network and gets to asking for a TFTP server. You specify one, and it times out, then says chainloading failed.
Pic here if you’re interested: https://photos.app.goo.gl/44BQhe3ArNk3ngGRA
Loving FOG so far by the way, but getting this to work will avoid us having to manually re-configure boot order options (as windows seems to happily chuck itself at the start of the boot order all the time!).
TIA
Alexis
-
@AlexisPHC Ok the pictures tells us a good story. Your dhcp server is working perfectly. Well its not working but its not your dhcp server’s fault at the moment.
from the 10.1.6.x subnet can you ping the FOG server?
Is there some some kind of screening router between your 10.1.6.x network and your 10.1.22.x networks?On a computer on the 10.1.6.x subnet, take a windows computer, disable the windows firewall. Then install the tftp client on the windows computer. From a command prompt key in
tftp get 10.1.22.1 snponly.efiand see if you can pull that tftp image.10.1.22.1 is suspicious since typically the .1 or .254 is the default router for a subnet. It doesn’t need to be, but typically it is. Is the .1 address correct for the fog server?
I feel this is a routing issue between the two subnets.
-
@george1421 thanks - good steps to check.
Yes, I can ping from that subnet, and I can also tftp the file from one of my linux hosts on that subnet with no issues. There is a router in between, but it’s not filtering traffic to my knowledge. It is passing DHCP requests to our windows DHCP server for that subnet/vlan however.
And yes, the ip address is correct, the router is sat on 10.1.22.254.
