Awesome help george 1421!!! That was my issue all along was that I was not using the /var/www/html/iso, but I was pointing directly to just /iso. It all makes sense now. Thanks for all the help!!! WinPE is successfully booting for me!!! Great work FOG and thank you for the advanced menu!!!

So I have an issue getting the x:\windows\system32> to even ping my fog server for net use. I am currently using fog to boot into winpe, so I know that the pc’s network works just fine. Before I add the drivers (which I took off the originial machine) I am currently using drvload x:\ drivers\card to load the drivers. Then I use wpeutil IntializeNetwork to get everything up and running again, but there is still not network activity. The error I receive is PING: transmit failed. General failure. Any help would be greatly appreciated.

Awesome help george 1421!!! That was my issue all along was that I was not using the /var/www/html/iso, but I was pointing directly to just /iso. It all makes sense now. Thanks for all the help!!! WinPE is successfully booting for me!!! Great work FOG and thank you for the advanced menu!!!

I am having the same exact issue right now also. I have become so frustrated that I actually have built my own WinPE PXE boot server and if I can’t resolve this, I may just have to retire the fog and just move on to doing everything through my PXE server using just .wim files. I really like the user friendliness of fog, but I could always just automate everything with the WinPE iso. Please help solve this because I don’t want to give up on fog.

My working fog server is using fog 1.2.0 on ubuntu 14.04 . The server I am not creating is an exact replica in the settings, so I am confused as to why I am running into this problem. It may be hardware because my nic is realtek and I heard a lot of issues with realtek nics and linux. Not really sure. Any guidance is appreciated. Thanks.

I had a similar problem where my passwords were all correct, but the usernames were incorrect. What I did was change the username to the username of the server, in my case it was ubuntu because that is what I called it, and it fixed the problem. Are you logging in under the fog user on the server? If you got to Fog Configuration -> Fog Settings -> TFTP Server -> verify the username and password is correct to the username and password that you are using on the server. Also go to Storage Management -> Click on your Storage Node -> Verify it is the same username and password as in TFTP Server. I am not sure if you set up a password for MySQL or not, but I left mine blank, so you may have to change the username and password in Fog Configuration -> Fog Settings -> Fog Storage Nodes to match that. I seriously had this same issue, but once I figured out that I was using my ubuntu user and changed the appropriate username and password, it all worked just great. Hope that this helps out.

[quote=“Jaymes Driver, post: 36692, member: 3582”]Personally, I would use the DNSMasq and stop messing with the scope and dns settings. DNSMasq works in such a way it only issues ips to machines looking to PXE boot so it won’t work like a DHCP server. And best of all, when you pull the fog server, nothing else in your network is affected.

DNSMasq is made so that users that don’t have the ability or the know how to edit the scope and DNS settings can still use some of the services.

I’m not saying your settings are wrong in any way. I had all my settings correct and STILL met proxy boot issues, particularly the Error you are experiencing.

I work in a Novell environment, Novell Netware 6.5 to be exact, which has strict limitations on a boot file name. In order to use the undionly.kpxe in fog I had to set up and enable DNSMasq to get my network to resolve my boot file and server. I had to do this for a number of reasons other than just Novell’s limit too. I have other technicians in my network that use WDS to image. Except their settings override mine. I also have IP helpers in my network, that override my boot settings that are set up for the WDS. DNSMasq has proven to be a wonderful solution many times worth it’s weight in gold. I know you want to save it for the last ditch effort, personally, I would be using it FIRST before I tried anything else (after of course adding my boot file and server to the scope and dhcp settings.)

Either way, Good luck and I hope you solve your issue.[/quote]
Another thing that I wanted to add is that I do have the ability to tftp the undionly.kpxe file from the client pc and also on the server. I don’t know if that means anything, but just wanted to acknowledge that I can do that. Thanks

[quote=“Jaymes Driver, post: 36692, member: 3582”]Personally, I would use the DNSMasq and stop messing with the scope and dns settings. DNSMasq works in such a way it only issues ips to machines looking to PXE boot so it won’t work like a DHCP server. And best of all, when you pull the fog server, nothing else in your network is affected.

DNSMasq is made so that users that don’t have the ability or the know how to edit the scope and DNS settings can still use some of the services.

I’m not saying your settings are wrong in any way. I had all my settings correct and STILL met proxy boot issues, particularly the Error you are experiencing.

I work in a Novell environment, Novell Netware 6.5 to be exact, which has strict limitations on a boot file name. In order to use the undionly.kpxe in fog I had to set up and enable DNSMasq to get my network to resolve my boot file and server. I had to do this for a number of reasons other than just Novell’s limit too. I have other technicians in my network that use WDS to image. Except their settings override mine. I also have IP helpers in my network, that override my boot settings that are set up for the WDS. DNSMasq has proven to be a wonderful solution many times worth it’s weight in gold. I know you want to save it for the last ditch effort, personally, I would be using it FIRST before I tried anything else (after of course adding my boot file and server to the scope and dhcp settings.)

Either way, Good luck and I hope you solve your issue.[/quote]
Hello Jaymes,

All honesty, I do want to use the DNSMasq, but I am not a professional by any means with Linux so creating something to be used for Fog makes me nervous because it is just something else that can go wrong. In addition to the guide, could you give me extreme specifics for creating the DNSMasq and then I will create it and use it because I am extremely fed up with this at this point. Thanks.

[quote=“Junkhacker, post: 36687, member: 21583”]did you install a desktop or server version of Ubuntu?[/quote]
So I tried something different and did a fresh install of Ubuntu 14.04 LTS desktop and then installed fog 1.2.0 and after I confirmed that all of my settings are the same as my previous server, I am still getting No Bootfile error. I know, use DNSMasq, and I am about to, but right now I want to figure out why one works perfectly, but the other does not. Any ideas, or show me how to proper link the tftpboot to that location as listed above would be greatly appreciated. Thanks everyone for your help with my issue. I really do appreciate everyone’s help.

I tried to link the /tftpboot folder to /var/lib/tftp using:
ln -s /tftpboot /var/lib/tftp
I still receive the same error message. Did I link the folder properly? Haven’t had to do that before so just researched it and that’s what it said to do to link.

[quote=“Tom Elliott, post: 36661, member: 7271”]Have you attempted to use tftp command line to see if you can even receive the file?

Have you verified that firewall (ubuntu usually defaults to ufw, fedora 20+/centos 7 seem to use firewalld, iptables is flushed and disabled?) Have you ensured selinux (only relevant from what I can tell on RedHat based distros) is disabled and disabled properly? (Meaning verified with sestatus)

Have you tried linking the tftpboot to /var/lib/tftp? (For some reason, some distro’s are really pushing to put the files here now.)[/quote]
Hello Tom,

Thank you for your help. I have disabled ufw, but I did notice an SELinux folder on the computer, which I did not have on my Ubuntu 14.04 LTS that I have set up for my other fog server. I did the steps to disable SELinux, but not sure how to check because when I type sestatus it says it is not installed. I will try linking the tftpboot to /var/lib/tftp and see if that works (crossing my fingers) and get back to let you know if it works. Thanks everyone for the help!