@george1421 I’m 99% sure it was the suggestion of something I found on the forums a long time ago, but simply forgot. Like I said, once everything calms down, I’m planning on rebuilding my FOG machine anyways, and blast away old images, especially since I can drop driver packs in now :)

@george1421 You are an absolute legend George. It works now and I was able to PXE boot from my client PC and upload it to the Hosts screen. I can view it on the network and everything is working correctly. Thank you so much!

@rwakc well, it would be technically possible to set up a method where you could be automatically imaging any device pxe booted from the network, and set up multiple dhcp scopes on different network ports, serving out different pxe boot files with embedded scripts. that way, you’d be able to choose what image the system gets imaged with by choosing what network you plug the device into.

@Tom-Elliott Sorry I was helping someone else in a chat session so I’m now just getting back to this. Taking Tom’s specilation that iPXE was not managing the boot files correctly on this system for some reason, I asked the OP to usb boot into FOS as a test. We’ve had to do this in the past with a few other systems that just failed to pxe boot properly. The OP was able to usb boot into FOS so that told me the kernel and the init.xz were fine. I created the boot image on Apr 6, so the kernel and inits were current of that time. Will this process work for now for imaging, yes. Is this a long term solution, I hope not. Hopefully either a iPXE kernel update or a firmware update on the target computer will fixed the issue so that PXE booting can continue to be used in the future.

@Sebastian-Roth According to this discussion (http://serverfault.com/questions/806875/how-to-tell-isc-dhcp-correct-zone-for-reverse-zone-ddns-update) it has to do with reverse dns lookups

Through chat had @jrm run a wget to download the bzImage’s from the fogproject server. OP stated these kernels worked.

@Wirefall [Moderator note:] I’ve forked this users post since the issue is similar to the OP of this thread, but deals with a different version of FOG. You can find your post here: https://forums.fogproject.org/topic/9201/fog-will-not-boot-failed-to-get-an-ip-via-dhcp

Well… This is embarrassing. Good news I fixed it, i get into the PXE menu now! :D I do have a different question now, when I click boot from hard disk in the pxe menu it doesn’t load the operating system, any ideas for that? For the issue relating to TFTP this is what happened: I set up a packet scan on both the DHCP and PXE server and after analyzing the packets i noticed there were two different packets sending a different option 66 and option 67. One was right pointing to the FOG server and Undionly.kpxe the other however pointed to the DHCP server. Apparently an old image deployment software was still working even though the options weren’t configure anymore. I removed these and everything worked great!

Thanks to all who participated in this thread. I killed the switch port that someone had a Netgear router hooked up to and everything is working fine now. FOG menu is showing up. I haven’t tried pulling down an image yet, but I have a good feeling. I will do my best to up-vote the proper answers even the earlier posts questioning the possibility of multiple DHCP servers. I had a feeling one was out there, but I didn’t think it would have a such a huge impact on FOG. Again thanks everyone for all the help!

@mcgill-eus if you follow the Upgrade to Trunk instructions exactly, you’ll get Release Candidate 6. RC-7 will probably be out sometime today though and I feel it highly important to move to that when it’s out, as it fixes some issues in 6.

You are trying to boot the I.S.O. over the network. The way I recommend you do this for pxe access in your company is to extract the content of the iso to a folder of your choosing then give proper access to the folder for the fog server using the exports file. examples can be provided if im understanding what your trying to do?

Bonjour Oui c’est bien FOG 1.2.0 et c’est bien la modification initrd=$imagefile qui à fait fonctionné sur MAC ######### Hy Yes it’s good FOG 1.2.0 and it is changing initrd=$imagefile who in fact worked on MAC

Thank you all. I will update in case resolved. Take care!

@Sebastian-Roth said in Impossible to boot on PXE......: Wireshark filter bootp && tftp is great for this This has been in the wiki for some time, here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

Hey, after tessting it really looks like the problem is on that SSD. Could deploy and upload on other clients. I guess the first imaging tool brokes it. But after all fog is better than that anyway. Thank you for your help!

@monasmith529 said: Yes it is a vm single nic vmxnet 3. No bridging. No bridging??? Wouldn’t work I guess. Could you please explain a little more about your setup when asking a question next time. We cannot properly help you otherwise.

@Tom-Elliott said: @Scott-B right but you don’t have anything in the advanced items. There is the login and it is working fine. But the advanced menu is its own configuration setting that you put your needs in. Ah… okay. I thought that was just called from fog.advancedlogin.

@Asthea I have it working right now. Thank you everyone for the assistance. I have no idea if the fetch command is even needed. I will test with it out and continue to clean it up. But I am grateful that it is working. Hi-5 all around. :UBUNTU kernel http://${fog-ip}/fog/service/ipxe/ubuntu/casper/vmlinuz.efi initrd http://${fog-ip}/fog/service/ipxe/ubuntu/casper/initrd.lz imgargs vmlinuz.efi boot=casper vga=normal root=/dev/nfs netboot=nfs nfsroot=${fog-ip}:/var/www/fog/service/ipxe/ubuntu/ fetch=http://${fog-ip}/service/ipxe/ubuntu/casper/filesystem.squashfs initrd=initrd.lz locale=en_US.UTF-8 keyboard-configuration/layoutcode=us mirror/country=US boot || echo failed to boot prompt goto MENU

@xcvtop said: @Wayne-Workman Hi I am going to try fedora. Is there a link to fedora 21 you would recommend as safe to download? or is it literally as simple to to install on Fedora 22 and change “yum” to “dnf” in the commands? The FedoraProject hosts torrent files for Fedora 21 and YES they are COMPLETELY legal to use - because the software is open source and free, and p2p is legal as well when used legally. The torrents hosed there are safe - and come with hash values of what the files should have. So what you get would be legit. Also - you can use Fedora 22 as well - and just change yum for dnf - and skip the MySQL stuff, the installer will install mariaDB instead of MySQL for Fedora 22. There are notes on this at the bottom of the article.