Another interesting little tidbit. In FOG when I got to Other Information and attempt to set a master password an error message appears
“PXE menu update failed. Unable to connect to tftp server”
FYI - I received this message yesterday and did stop and restart the tftp server via Terminal by typing in sudo stop tftpd-hpa and sudo start tftpd-hpa
Hello Chad,
There is no file except Default in /tftpboot/pxelinux.cfg/
What other information can I provide?
That was awesome! Now the .12 machines are able to get to the FOG menu but there is still ONE issue. I was able to register the host but imaging failed.
“Unable to connect to tftp server”
is the error now.
Almost there 
No, I don’t even get the FOG menu. It errors out trying to find pxelinux. I believe the error is No Image File Found.
The gateway for those which will not PXE boot is a .12 address of course and .10 for the ones that will PXE boot.
The same DHCP server supports both. I verified that one right off
Thanks for helping Chad. I really need it!
Yes, that is the exact scenario.
Hello Chad,
Yes I do have a DHCP server which (if it matters) does have a 192.168.10.* address. There is no problem whatsoever accessing network resources, etc just can get machines with this 192.168.12.* address to PXE boot. Image file not found. So I am assuming that something else needs to be set on my FOG server.
Fresh install, the second time I’v had to do this, of Ubuntu 11.04 and current FOG.
After the install I took my master image computer and successfully booted into PXE, completed host registration and inventory, assigned a task to upload the image, all good.
Then when trying to deploy the image to a brand new HP desktop of same make model etc I can not get it to PXE boot. Here is what I have noticed that may be an issue. The IP address of the FOG server, DNS, DHCP etc all are 192.168.10.* but the company does also deply 192.168.12.* addresses.
The failing desktop DOES have a 192.168.12.* address. I’ve changed it to a static IP address of 10.192.168.** but even then it will not boot into PXE. I have manually registered the desktop into FOG and it does not resolve.
One thing that I did during the FOG setup is to set the Subnet/netmask to 255.255.255.0 maybe it should be 255.255.0.0 to be able to resolve those machines with the .12 address? If so I can’t figure out how to change it in the FOG configuration.
Any help, please give specific instructions, would be greatly appreciated.
Erin
Thank you Eclat2k, Thank you sooo much!
I believe I do have the same problem. I am posting my dhcpd.conf information below. I’m not sure of the exact way I should type in the the interface eth0
Can you please help me edit? I will also do a search to see if I can figure out the proper way to enter it. The sample listed here is missing.
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 192.168.10.195;
subnet 192.168.10.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.10.10 192.168.10.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 192.168.10.5;
option routers 192.168.10.1;
filename “pxelinux.0”;
}
Hi Leroy,
I’m having the same problem as you did. I can not PXE boot anymore. I can’t find the dhcpd.conf file you mentioned. And I wonder about exactly what folders are suppose to be where.
For example in FOG, other information, the TF TP Server information states tht the FOG_PXE_BOOT_IMAGE is located at fog/images/init.gz but I do not see a fog folder at the root.
Could we share some screen shots or something. I’ve been at this for four solid days.
Thanks!