search for: wdsmfg

...other server would be providing DHCP and WDS would be providing TFTP/PXE. I'd argue for your setup what you really want is straight MS DHCP service (to provide DHCP). and point it to your NAS (for TFTP). Except that wouldn't work for your known servers. About proxyDHCP. I'm loading wdsmfg.efi as the network boot program (NBP). So some of my tested configurations do the std D-O-R-A to the DHCP server and then immediately do a TFTP read request from my TFTP server. Loading the boot\x64\wdsmgfw.efi. However, then it does RA - RA - RA to the WDS server (proxyDHCP port 4011). I'm c...

...other server would be providing DHCP and WDS would be providing TFTP/PXE. I'd argue for your setup what you really want is straight MS DHCP service (to provide DHCP). and point it to your NAS (for TFTP). Except that wouldn't work for your known servers. About proxyDHCP. I'm loading wdsmfg.efi as the network boot program (NBP). So some of my tested configurations do the std D-O-R-A to the DHCP server and then immediately do a TFTP read request from my TFTP server. Loading the boot\x64\wdsmgfw.efi. However, then it does RA - RA - RA to the WDS server (proxyDHCP port 4011). I'm c...

...ng DHCP and WDS would be providing TFTP/PXE. I'd argue for > your setup what you really want is straight MS DHCP service (to > provide DHCP). and point it to your NAS (for TFTP). > > Except that wouldn't work for your known servers. > > About proxyDHCP. I'm loading wdsmfg.efi as the network boot program > (NBP). So some of my tested configurations do the std D-O-R-A to > the DHCP server and then immediately do a TFTP read request from my > TFTP server. Loading the boot\x64\wdsmgfw.efi. > > However, then it does RA - RA - RA to the WDS server (proxy...