Use fog with Windows Server 2008 R2 DHCP

[Carbonnier Alexandre]

@Sebastian-Roth

[Sebastian Roth]

@Carbonnier-Alexandre Ok, that looks fine if 192.168.21.195 is your FOG server. Can you PXE boot other machines? Is it just those NUCs having an issue?

[Carbonnier Alexandre]

@Sebastian-Roth I only have NUCs I will try with my laptop now and come back to you

[Sebastian Roth]

@Carbonnier-Alexandre Just be aware this is an PXE setup only capable of PXE booting UEFI machines! But from the output you posted the NUC actually does try to PXE in UEFI mode. Just saying this in case you can’t PXE boot the laptop either. Make sure it’s set to UEFI and you should see the UEFI specific message “Start PXE over IPv4” as well.

[george1421]

From the text you posted originally, one might think the nuc is pxe booting in bios mode. I know the nucs pxe boot because I have them on my campus and they image just fine with FOG.

Your 2008 dhcp server will be a tripping point for you since 2008 dhcp server doesn’t support dynamic pxe booting like 2012 dhcp server and later. There is a service you can install on your fog server to provide dynamic pxe booting while you keep using the main windows 2008 dhcp server. That linux service is call dnsmasq. I have a tutorial how to install dnsmasq on your fog server. It will take about 10 minutes to install and to make operational. https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

[Sebastian Roth]

@george1421 said in Use fog with Windows Server 2008 R2 DHCP:

From the text you posted originally, one might think the nuc is pxe booting in bios mode.

Why do you think so? I’d say the “Checking Media Presence, Media Present, Start PXE over IPv4” is clearly UEFI PXE boot.

[george1421]

@Sebastian-Roth said in Use fog with Windows Server 2008 R2 DHCP:

Why do you think so?

I would have to grab a nuc to prove it, but I would think it would say something about nbf if it was in uefi mode (having a picture would speak volumes). The dhcp server appears to be configured correctly for uefi systems, so as long as the nuc is on a routable network it should pxe boot.

[Carbonnier Alexandre]

@Sebastian-Roth Hi, i try with my laptop, and it display this

[Sebastian Roth]

@Carbonnier-Alexandre Well, NBP filezize is 0 Bytes is telling us it cannot properly receive the file via TFTP. Please follow the troubleshooting guide: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

[george1421]

@Carbonnier-Alexandre Your picture says a lot about the problem.

Can you install a ms windows native feature on your computer and plug it into this same subnet (192.168.21.x). Please add the windows feature tftp client to this test computer then once installed open a cmd window and key in the following tftp 192.168.21.195 GET ipxe.efi . We only care that the file is downloaded from the fog server. We don’t care about the file itself.

[Carbonnier Alexandre]

@george1421 I’m testing it tomorow, i’m not on my network now. Thanks guys

[Carbonnier Alexandre]

Hi,

I’m back, so i have already same problem. My NUC try to boot and display this :

My dhcp it’s already setup…

Need help. Please.

Thanks guys have a nice day.

[Sebastian Roth]

@Carbonnier-Alexandre Ok, client gets an IP and tries to connect to the TFTP server to get the PXE boot image file. This part times out. Either the server IP is incorrect (should be FOG server IP), the filename is wrong or a firewall is blocking the file transfer. Please post a picture of your DHCP server settings and let us know about your network setup! Is the FOG server in the 192.168.21.x network or in a different subnet?

[george1421]

@Carbonnier-Alexandre If your dhcp server is setup correctly (192.168.21.10) then lets grab a pcap (packet capture) of what the client is being told to do. While there are a few steps involved its the quickest way to get the answer.

https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

[Carbonnier Alexandre]

@george1421 I make tcpdump test and i have this

Thanks a lot. Have a nice day

[Carbonnier Alexandre]

@Sebastian-Roth my dhcp config

[george1421]

@Carbonnier-Alexandre Will you upload the pcap to a file share site and then either post the link here or DM me the link so I can look at the actual pcap file?

[george1421]

@Carbonnier-Alexandre But putting together just what I see in the screen shots, I think the target computer is a bios based one and you are sending ipxe.efi to it. Again the pcap will tell us exactly what is going on, but the error screen you showed us looks like a bios pxe boot screen but in dhcp option 67 you have ipxe.efi listed. A uefi boot screen should say something about NBF (network boot file) and not the message about PXE-M0F. At least that is what I think.

[Carbonnier Alexandre]

@george1421 sorry.

The file : output.pcap

Thanks for you help

[george1421]

@Carbonnier-Alexandre

The short answer is if you look in the pcap in the DHCP DISCOVER packet, then dhcp option 93, you will see the pxe booting computer is saying hello I’m a bios based system {IA x86 PC ( 0 ) }. You are sending the bootloader for a uefi system (ipxe.efi) which will not boot a bios based computer. Change dhcp option 67 to undionly.kpxe and the target computer will boot.