@george1421 Alright, I will be sure to keep that in mind! But As today is Friday and I’ve already stayed int almost 3 hours too long than I’'ll try to get some rest over the weekend and have a new crack at it on Monday.

Huge thank you for all your help!

Hi once again!

Our problem, as it stands today, is solved. We ended up trying to install the FOG server on the same subnet with the host machines, which worked. After that we tried putting the machine back on the subnet where all our VMs are located. That broke it. Later the network admin realized that during his configuration he accidentally left a space after the IP on option 66. After that was fixed things stated working out.

So in the end what I was chasing was a typo.

A big thanks to @george1421 for being as helpful as You could during the troubleshooting process.

I am now happily deploying my Windows 10 images.

A little bit of an update:

I ended up contacting our “helpdesk” where my problem got directed to the coolest guy I have ever had the opportunity to work with.

We wound up installing FOG-server on another machine on the same subnet as the hosts (10.252.80.0/22). After doing this everything works as expected.

We are still working on getting it to work across different subnets. Is there any possibility that the FOG server configuration might be at fault when dealing with communication across subnets?

@george1421 Oh yeah, of course! My bad. I totally agree on the fact that it’s a problem with our infastructure. As far as I can tell FOG is doing what it is supposed to do just fine.

I also shot an email to our network administration explaining the whole situation. Let’s see where that lands us.

@george1421 Now that I’ve read through your last response again, there is one thing that is confusing me. If i create this dedicated imaging network, then how would I point host machines to PXE boot on this network?

@george1421 Alright, I will be sure to keep that in mind! But As today is Friday and I’ve already stayed int almost 3 hours too long than I’'ll try to get some rest over the weekend and have a new crack at it on Monday.

Huge thank you for all your help!

Well… that sucks

Alright, well, I’m just going to try putting the FOG machine in the same subnet with the host machine and see if that is going to change anything.

EDIT Deleted rant

First of all, thank you!

Latest fresh FOG install config:

* Here are the settings FOG will use:
 * Base Linux: Redhat
 * Detected Linux Distribution: CentOS Linux
 * Server IP Address: 10.254.10.29
 * Server Subnet Mask: 255.255.255.0
 * Interface: ens192
 * Installation Type: Normal Server
 * Internationalization: 0
 * Image Storage Location: /images
 * Using FOG DHCP: No
 * DHCP will NOT be setup but you must setup your
 | current DHCP server to use FOG for PXE services.

 * On a Linux DHCP server you must set: next-server and filename

 * On a Windows DHCP server you must set options 066 and 067

 * Option 066/next-server is the IP of the FOG Server: (e.g. 10.254.10.29)
 * Option 067/filename is the bootfile: (e.g. undionly.kpxe)


 * Are you sure you wish to continue (Y/N)

Attached are 2 files.“Output 4” is from the FOG machine itself and the other one (67,68,69,4011Capture1) is from Wireshark scanning the same ports at the same time.

0_1525439990605_output4.pcap
0_1525440047448_67,68,69,4011capture1.pcap

EDIT: I did some additional testing and I’ll post these results as code snippets for easier referencing:

FOG machine on a 10.254.10.1/24 subnet
0_1525443426142_output5.pcap

Host machine subnet 10.252.80.0/22
0_1525443818489_67,68,69,4011capture2.pcap

As far as I myself can understand there is no actual PXE communication going on in the 10.252.80.0/22 subnet.

I am pretty sure I had Dnsmasq service disabled, but just to be on the safe side I am doing a complete nuke n’ pave as I’m typing this. I already have Wireshark setup on the same subnet. I shall post the results as soon as I get them.

Hello FOG community!

I have been trying to set up FOG for a good week now, but it feels like I’m constantly running into a brick wall. Head first.
I’ve tried searching this forum, but I’ve come up with nothing so far

My FOG machine: Centos 7 VM on a ESXI host. 10.254.10.29
The Host machine(s) I’ve been trying to PXE boot with: Dell Latitude 5480, HP EliteDest 800 G3 SFF. Both are on DHCP and usually get an address from the 10.252.80.0/22 range.

Our schools DHCP, AD and all the other fun stuff is centrally managed by an external company. The DHCP server serves all the schools in our city (450 000 people). I’ve asked them to make the required modifications to the DHCP server. Here is the e-mail ticket I sent them:
Windows Server DHCP
Option 66 (066 Boot Server Host Name)
String Value: 10.254.10.29
Option 67 (067 Bootfile Name)
String Value: undionly.kpxe

They ended up replying that they have made the modifications that I asked for and that can probably be backed up by the fact that before the changes were made I was getting a TFTP timeout error.

Now that these changes have been made I’ve been stuck on a “PXE-M0F: Exiting Intel Boot Agent” error. I have tried configuring a Dnsmasq FOG server, but that hasn’t worked either. So far I’ve done a fresh install of Centos and reinstalled FOG for 4 times with 2 kinds of configurations:

• Directing FOG to a Windows DHCP server
• Using proxy DHCP (Dnsmasq)

Both of these have still had me stuck on the PXE-M0F error.

Just in case, here is a full transcript when I try PXE booting:

Intel Boot Agent CL v0.1.09
Copyright 1997-2013, Intel Corporation
CLIENT MAC ADDR: A4 4C C8 10 F7 FB GUID: 44454C4C 3300 1031 8052 B2C04F364832
CLIENT IP: 10.252.80.249 MASK: 255.255.252.0 DHCP IP: 10.254.255.16
GATEWAY IP: 10.252.80.1
TFTP.
PXE-M0F: Exiting Intel Boot Agent.
No Boot Device Found. Press any key to reboot the machine_

Please do ask for any other kinds of information that is needed. Any help is much appreciated.

EDIT: Here are the settings used by the current FOG install:

 * Here are the settings FOG will use:
 * Base Linux: Redhat
 * Detected Linux Distribution: CentOS Linux
 * Server IP Address: 10.254.10.29
 * Server Subnet Mask: 255.255.255.0
 * Interface: ens192
 * Installation Type: Normal Server
 * Internationalization: 0
 * Image Storage Location: /images
 * Using FOG DHCP: No
 * DHCP will NOT be setup but you must setup your
 | current DHCP server to use FOG for PXE services.

 * On a Linux DHCP server you must set: next-server and filename

 * On a Windows DHCP server you must set options 066 and 067

 * Option 066/next-server is the IP of the FOG Server: (e.g. 10.254.10.29)
 * Option 067/filename is the bootfile: (e.g. undionly.kpxe)

EDIT 2: I am able to connect to TFTP from Windows CMD on the client machines and copy the undionly.kpxe file with no problems.

PS C:\Windows\system32> tftp 10.254.10.29 get undionly.kpxe
Transfer successful: 97715 bytes in 13 second(s), 7516 bytes/s

EDIT 3: At this point I’m just trying everything:

[root@FOG-server bin]# systemctl disable firewalld
Removed symlink /etc/systemd/system/multi-user.target.wants/firewalld.service.
Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.

No good, I’ll re-enable it.

EDIT 4: I tried tcpdump described in this : guide by @george1421 . I ended up having to modify the capture command a little bit to make it work though. Here’s what I used:

tcpdump -i any -w /var/output.pcap port 67 or port 68 or port 69 or port 4011

I’ll attach the dump files for the curious:
2_1525419413445_output3.pcap
1_1525419413445_output2.pcap
0_1525419413445_output.pcap

After having a look at these I discovered that my host machine is requesting to read the file “boot\pxeboot.com”, from the correct location (the IP of my FOG machine (10.254.10.29)). Is this right? Or is this the root of all evil?