@Tom-Elliott Do the values in .fogsettings get applied only the first time installfog.sh is executed, or are they supposed to be applied on every subsequent run as well?
In my case, updating .fogsettings after the initial installation doesn’t seem to change anything, so I want to confirm whether this is expected behavior or if I’m missing something.

@Tom-Elliott said in Quick Registration and Invenotry not working:

@SotY I know roughly when the error was introduced (1.5.10.1748) and I even know where it’s happening, what I don’t always know is the why.

You are right. Last one working correctly that is available at github is 1.5.10.1734. 1.5.10.1751 doesn’t work.

It seems like the host nmed TEST was created/updated? I don’t see history showing it as successfully created, but maybe there’s just no history log of new host creation.

TEST was created manually from web GUI just to check if it’s working that way. It seems that history does not contain anything related to hosts registrations from ipxe, only from web. I tested this on both working and not working versions and neither have anything in history.

@mrowand How did you manage to boot from the network with this computer? I’ve already made several changes in the BIOS, but it doesn’t recognize Fog. I have other old computers that clone normally, but I can’t get this one to work. I’m on version 1.5.10.1733. What did you change in the BIOS to make the boot work?

Hello,

It’s working again.
I have update to the last version (1.6.0-beta.2273) but I’m not sure it’s fixed with this.
I have also clean DB using this : https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

Thank you.

Every time after updating to a new build, the first image works, but the next one doesn’t.

@Tom-Elliott said in FOG Client service disconnection, pending snapins are not even being detected:

@Jamaal The client lives on the Machine itself. not on the fog server.

Those logs live on teh Windows machine I forget the exact path but something like:

c:\program files\fog client\fog-error.log or something like that?

Yes, it’s c:\program files (x86)\fog\fog.log

I figured out the issue, lol. I was having a moment, but thanks for helping me out.

@george1421 said in PXE issues:

@Jamaal This problem is solvable but it make take some effort on your part.

Lets start with the basics.

For the DHCP IP zone where your pxe booting clients live, you need to set dhcp options 66 to the IP address of your fog server. And for dhcp options 67 that needs to be snponly.efi or snp.efi. With those settings configured on a MS Windows based dhcp server a pxe booting client should boot. Make sure on your dhcp server that is responding to bootp and dhcp requests. Its been a while since I messed with windows but on the dhcp server there should be a setting of dhcp bootp or both. Select both.

Now lets talk about WDS for a second. A WDS server can use dhcp options 66 and 67 as above, but it can also run a proxy dhcp service that tells the client to ignore the dhcp options and come talk to it for boot information after it gets an IP address for the dhcp server. This maybe called a netboot service or something like that on your WDS server. Its not part of the main WDS service. If this service is still enabled it will override any settings you make in dhcp for pxe booting.

So how do you figure this out to what’s wrong?

The easiest and most complicated issue is to identify what is flying down your network during the pxe booting process. You can do this with wireshark on a witness computer (computer not part of the pxe booting process). This witness computer can either be a ms windows or linux computer, the key is to have wireshark loaded. When you start up a capture use a capture filter of port 67 or port 68 or port 4011 That will limit what wireshark sees to only the dhcp packets. Make sure the witness computer is connected to the same subnet as the pxe booting computer.

Start the packet capture and then attempt to pxe boot the target computer. Continue to capture the packet until the pxe booting computer either reaches the fog iPXE menu or errors out. Then stop the capture.

In the top section you should see the DORA (discover, offer, request, and finally ack/nack) process. The process goes as follows:
Client -> Discovery
Server-> Offer
Client -> Request
Server -> Ack/Nack

In this process you are most interested in the one or more OFFER packets. In a normal network you should only see one OFFER packet. When WDS is involved you will see one OFFER packet from your main dhcp server and a second OFFER packet from your WDS server. If you are seeing the OFFER from your WDS server then you don’t have the proxy-dhcp service disabled, and that is causing your issue. If you are seeing two offer packets from two different dhcp servers, such as a primary / secondary setup make sure both dhcp server are configured to boot from FOG server.

Now what do you do if you only have one OFFER packet and its still not working. This is where you need to select the OFFER packet and then look at the data in the parameters box. There will be the bootp fields of next-server and boot-file these need to be configured for the fog server IP and snp.efi. Then in the dhcp options section options 66 and 67 need to be set correctly. If one or the other sections are not set correctly you will get random machines not booting while others are.

If you can’t figure it out save the packet capture file “be sure you only captured the dhcp process” and up load the file to a file share site and post the link here and one of us will take a look to see what’s wrong. But I think from what I covered here you should be able to figure out what the pxe booting client is being told to do incorrectly.

George,

I ran the idea with the system administrator at my job and of course he was doubtful (conceited), he turned off the server thinking that would solve the issue. I ended up looking at an older forum and made a USB with the ipce file and booted up the machines that were given me issues and that worked. You guys can close this and mark as resolved. Again, I appreciate your guidance on this.

There are multiple new problems related to this issue.

First one is buildipxe.sh script and ipxe with commits after 01/14/26. It does not enable USB_HCD_USBIO correctly.:

sed -i 's+//#define USB_HCD_USBIO+#define USB_HCD_USBIO+g' config/usb.h sed -i 's+//#undef USB_KEYBOARD+#define USB_KEYBOARD+g' config/usb.h sed -i 's+//#undef USB_EFI+#undef USB_EFI+g' config/usb.h

but it doesn’t work correctly with latest ipxe source files because of the tabs. It should be:

sed -i 's+//#define USB_HCD_USBIO+#define USB_HCD_USBIO+g' config/usb.h sed -i 's+#undef USB_KEYBOARD+#define USB_KEYBOARD+g' config/usb.h

USB_EFI is already defined in the source, so last sed is not needed.

But after fixing this and compiling, keyboard does not work anyway. There were significant commits to ipxe source on 1/15/26. They changed usb.h along with defaults. I was able to make it work again by going back to 6cccb3bdc00359068c07125258d71ce24db5118a commit, enabling USB_HCD_USBIO in usb.h and disabling “#define USB_CMD” in general.h that FOG uses (without this it won’t compile giving error about multiple definition of `usbio_driver’).

Adding the menu manually with the above settings resolved the issue for me.

@Tom-Elliott I’m having this issue currently running Fog version 1.5.10.1593 and OS version 10.0.19044 Build 19044. I’ve tried all of these steps and a plethora of others but have been unable to successfully capture a final image. Do you have any other ideas to try?

In Reports Menu, Imaging Log You will find this information.

After upgrading to 1.5.10.1754 it works just fine.
Thanks for bug tracking and improvement!

@thezman007 I would say the pcap file you provided is a model of how a proxy dhcp and dhcp server should interact. The first part of the pcap is perfect.

The second part starting at second #19. The client issues a dhcp discover and the dnsmasq answers right away, the client had to issue a second discover request before the main dhcp server @ 2.2 address responded. This pattern is repeated at the end of the pcap (you can see this if you look at the pcap with wireshark).

So this is only me reading the tea leaves but I think there is something up with your main dhcp server because its being slow to respond to dhcp requests. Understand I only can see 25 second pcap but I find it abnormal. When things go sideways (and it probably will) get a pcap of the failure, that’s going to tell us what’s missing.

I’m going to remove your pcap from your post because its not needed now.

@Tom-Elliott Thanks Tom, yes that looks to have sorted it out thankyou…

@Clebboii Following up if you’d be willing to let us know?

Thank you!

@Tom-Elliott I can confirm that it works with v1.5.10.1760. 🎉 Thank you very much! 🙇

@The-Dealman Awesome thank you! and we did publish 1754 specifically due to this issue (manually running the automated processes just in case your org is worried at all 🙂 )