I didn’t put in my DHCP server IP. I put in the actual fog server IP. I do not know if that was the correct thing to do, but everything is running now.

I really just followed this guide to setting up DNSMasq.

[URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’][I][SIZE=12px]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/SIZE][/I][/URL]

I didn’t do step 7 or 8 on the guide. Instead, I jumped down to the section “DNSMASQ settings for IPXE” and continued from there.

To be able to edit and create files, I used “sudo gksu nautilus.” I used gedit (text editor) to create the ltsp.conf file and saved it to my desktop. Then using “sudo gksu nautilus” in terminal allowed me to move the ltsp.conf from my Desktop to /etc/dnsmasq.d/ltsp.conf. Make sure to edit ltsp.conf for your setup. For example:

The boot filename, Server name, Server Ip Address

dhcp-boot=undionly.kpxe,[B]x.x.x.x[/B]

Change the [B]x.x.x.x[/B] to your fog server IP address.

I also changed the IP address in this section to point to my fog server.

This range(s) is for the public interface, where dnsmasq functions

as a proxy DHCP server providing boot information but no IP leases.

Any ip in the subnet will do, so you may just put your server NIC ip here.

Since dnsmasq is not providing true DHCP services, you do not want it

handing out IP addresses. Just put your servers IP address for the interface

that is connected to the network on which the FOG clients exist.

If this setting is incorrect, the dnsmasq may not start, rendering

your proxyDHCP ineffective.

dhcp-range=[B]10.0.0.10[/B],proxy

I hope that helps you.

[QUOTE]You could always try DNSMasq to proxy serve your bootfile and server, sometimes this can alleviate issues with finding the correct files.

[URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/URL][/QUOTE]

This did it!!! Finally, thank you so much. :):D Now that it boots Fog every time, I can learn how to actually use it instead of installing it. Thank you so much.

Wouldn’t the kernels be up to date with the newest fog (1.2)? Or is that something that has to be done manually?

[url=http://postimg.org/image/8b02epwkt/][img]http://s30.postimg.org/8b02epwkt/20140725_113435.jpg[/img][/url]

I get an error. 3c092003

We have 3 different clients. The HP Pavilion a1610n, HP Pavilion P6-2011, and Lenovo Ideacentre K33B.

A new update: I tried the same thing with a laptop and have the same issue.

As an experiment, I tried to chain load the virtual Ubuntu 13.10 with fog 1.2. The reasoning is because the old pxelinux.0 worked on the old test vm, but not the undionly.kpxe on fog 1.2. As a result, I can get it to boot the fog menu every couple of times, but not consistently. I am attaching a picture to show what it does. If it does boot to fog, it will configure real fast and boot. Otherwise, it does like the picture shows and goes to “press a key to reboot” after a few seconds.

[url]http://postimg.org/image/578ihklj1/[/url]

I did not think about that. Should I try virtualbox or something else?

Just out of curiosity, I have Fog server configured with “Bridged: Connected directly to the physical network” with “Replicate physical network connection state” checked. I currently have Fog with a separate IP address as the physical machine. Should they have the same IP or should it be separated like I have them.

Well, if it’s not dhcp, then what could it be?

[QUOTE]You could always try DNSMasq to proxy serve your bootfile and server, sometimes this can alleviate issues with finding the correct files.[/QUOTE]

I can give this a try later today.

Um, I don’t really do much with the DHCP, my boss handles most of that. It’s on Windows Server 2008 R2. I just know the IPv4 scope options 66 and 67 are set like they should be. Is that what you were needing?