If your tftp command comes back as successful, then the server is operating normally, and the problem lies in the environment.
Try setting up the dnsmasq service to dole out proxydhcp information, it can sometimes help in getting your pxelinux file where it needds to be by supplying the tftpboot information that the clients need. I use this in my environment set ups and it solves the issues you are experiencing.
the 32 bit version of the kernel that Tom keeps up to date can be found [url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url]
[quote=“jbrabhamMSD, post: 24822, member: 22901”]Tom, should the link to the bzImage file have the fixes you made? And where do I go to change pxelinux.0 to undionly.kpxe? Thanks for your help on this.[/quote]
You will want to update your DHCP server information, specifically Option 67. You will want to update your DHCP server to point to the undionly.kpxe file instead of the pxelinux.0 file you used with FOG 0.32.
If you use a dnsmasq proxy service, you need to edit the ltsp.conf information and update the pxelinux.0 listing in there to point to the new undionly.kpxe as well.
Also the link provided is the most up to date version of the kernel and includes all fixes up to this point.
[quote=“DanielJay, post: 24808, member: 23088”]BigMan99211,
Multicast should not have issues if you have the network setup correctly. It is best if you use managed network switches and can run IGMP on your network. This would prevent the flood of traffic to all network ports.[/quote]
This can also cause issues with trying to find the tftpboot server and your undionly.kpxe, be careful and take notes, I actually use the dnsmasq service because of this.
It depends on what you mean by back up. You can “store” the image stores there and you can add them back to the FOG server as you need them, so the data is there and what not, but while they are being stored on another server they will not be able to be accessed, if you want to be able to store and access the images, you need to set up a node.
[quote=“DanielJay, post: 24780, member: 23088”]Jaymes,
When you were multicasting were you doing identical hardware or different hardware? What was your link speed?
I have 25 identical machines to image all connected via gigabit and a 10G uplink to network. I may end up doing unicast on these machines for now but would like to know if it is a FOG server problem or a network switch related problem.[/quote]
I have 29 identical machines at Gig link speed and 1 that is a newer model ( I usually image it manually since it is one machine and keep it out of the group so it doesn’t cause issues with hardware when pushing the image… JUST IN CASE. Plus the drivers for the machine aren’t included in the image yet due to laziness, but I have a driver disc I use for the one machine.
Honestly I don’t like using the multicast, so I hadn’t tested it. I do however set up groups and manage the image through the membership page. I will deploy to all 30 machines at once but only 10 of them will image at a time and from my experiences will image faster than multicast. My ~45gb image takes about 15-20 min per machine. In the past if I multicast each machine takes upwards of 2 hours and even then sometimes fails because a machine drops out or looses connection and bombs my entire lab.
Try pushing your image out as a unicast to multiple machine and see if you can get by until someone fixes the multicast, you may find it is faster like I did 
.
I hate to agree with him but I have made a number of walkthroughs that are easy enough to follow that even a person that has never used linux feels comfortable. Please look in the Tutorials section of the forum!
[url]http://fogproject.org/forum/threads/ubuntu-installation-for-fog-12-04.9338/[/url]
for example.
This may be due to how Microsoft looks for the computer name. If you find the registry values you need to edit, you can make a script the queries the other instances of the computer name and synchronizes them.
I think the problem is the fog client, it may not support the naming conventions of Windows 8.
Glad I could help, and thank you for using the search button!
That’s my oldest Daughter in the picture, my girl snapped a picture of us once while we were napping 
[quote=“Vlad.R, post: 24685, member: 23134”]Hello .
I am trying to install FOG 0.33 with dnsmasq .
Following this guide :
didn’t have any success in booting at all .
Then , I have renamed “pxelinux.0.old” in “pxelinux.0” , and now I can boot from PXE .
Now ,a client computer find “pxelinux.0” , load it, and then loads iPXE file.(i think)
How can I make use of [B]undionly.kpxe file ? [/B]In this workaround , I don’t think i am using it.[/quote]
In the past, I was not aware that undionly.kpxe is a drop in replacement for pxelinux.0
You do not need to use the pxelinux.0 file. instead replace it with undionly.kpxe
look on your fog server in the folder /tftpboot/ look for files that match the mac address of your machine and delete the file, you should then be able to boot into the pxe menu normally.
Windows Task Scheduler. Add a task that runs the force shutdown command at 11 pm.
I should probably warn you… Green Fog is getting removed in 0.33
The command you want to put in your task is :
[code]
c:\windows\system32\shutdown -s -f -t 00
[/code]
Its loading drivers, you can try building a custom kernel and include ONLY the drivers your machines need.
There is a guide on this forum about creating custom kernels. That is the only way I know of to speed up a kernel load.
[quote=“Gary Kulovics, post: 24525, member: 2982”]Hello Tom and Jaymes
When I try to install the file it is downloaded as a DOS/Windows executable (application/x-ms-dos-executable) Why is that
What am I doing wrong Any haelp would be great
Thanks
Gary[/quote]
Try downloading the file on your server, not on a windows box. There is no extension it’s not bzImage32.zip or anything it is only bzImage32
Windows may have difficulty acquiring the file. I know my windows box wants to download the file as a .txt however the file isn’t encoded any differently, you should be able to download it in whatever flavor windows wants, just remember to drop the extension when you copy it to your linux box. OR you can do as I suggested and completely circumvent the Windows and download it straight to the server.
Sorry, but I am out of ideas… the compatibility test didn’t fail. I originally thought that the drive could be of the 4k advanced format… but now I am beginning to think that is not the case.
You are using the latest Kernel, and you installed windows as a resizable option, you chose the right option when setting up the image store… so all your options are set correctly from what I can gather.
I will bow out now and hope someone else can offer some expertise.’
If I come up with anything else I will be sure to let you know.
What happens if you run the compatibility check from the pxe boot menu?
[S]Not that I doubted you, but I gave this a go with the undionly.kpxe in place of pxelinux.0 and it went off without a hitch![/S]
[S]Thanks for your insight Tom![/S]
See next post