Just curious as we were able to image fine on 1.2.0 for quite some time up until recently. I know there was a minor network infrastructure change, but nothing that should have affected the Fog server’s functionality. Given I can access it via HTTP, TFTP, etc… and that it worked before, Im slightly confused why we need to upgrade.

Could you explain why this is necessary? What bearing does it have on the PXE issues I am having?

[media=youtube]he6x8hHzA78[/media]

To answer your questions in order…

1. No fog menu. It appears that PXE is failing before it can load the FOG menu.
2. DHCP options are set as they should be:
   [QUOTE]Option 66 - Boot Server Host Name: 172.20.4.252
   Option 67 - Bootfile Name: undionly.kpxe[/QUOTE]
3. We do not run STP on our network.
4. I will try to set up a private network for the Fog server and a client but it will take some time due to the DHCP settings that won’t be passed when configuring the private network.
5. I am not entirely certain what you are speaking of in regards to the trunk, more specifically the version

Will post a video in a bit.

Bump…

Still need some help resolving this. To this point, nothing has changed, though I have no clue what I could change to possibly fix the issue.

Thanks.

Apologies. I did both, worked as indicated. File transferred and whatnot, so it does not appear to be an issue with either the file being missing or the TFTP server not being active.

Restarted service as indicated in the link, attempted another download - no dice. Same error as before.

[quote=“Wolfbane8653, post: 40205, member: 3362”]Could you attempt some troubleshooting? [url]http://fogproject.org/wiki/index.php/Tftp_timeout…#Other_Troubleshooting[/url][/quote]

Coincidentally, an issue we had to work through to get the fog server to run correctly when we upgraded to 1.2.0 (way before this issue) was to add a delayed TFTP restart to the chron jobs (iirc - sorry been a while) so that the TFTP server would initialize after the NIC had initialized with its static IP.

Option 67 in our DHCP server is set as specified. Ill give the tftp service a restart, but I’m honestly skeptical as of right now.

Morning,

In a bit of a pickle here. Our Fog server (v1.2.0 - running Ubuntu 12.04 LTS) has been chugging along nicely since I got it up and running a month or two ago. However, went to go re-image a laptop I had already imaged via this version of Fog by downloading the image to the laptop and was greeted by this:

[QUOTE]iPXE initialising devices…done

iPXE 1.0.0+ (3a02) – Open Source Network Boot Firmware – [url]http://ipxe.org[/url]
Features: NFS FTP HTTP HTTPS iSCSI DNS TFTP VLAN AoE bzImage ELF MBOOT PXE PXEXT MENU

Configuring (net0 xx:xx:xx:xx:xx:xx)… ok
Could Not Start Download: Operation Not Supported ([url]http://ipxe.org/3c092003[/url])[/QUOTE]

It then instantly exits the PXE boot and boots back to windows.

Im absolutely lost as to what the problem could be since the server had no issues previous to this. Ive asked around and nobody has touched the server, so what changed is completely unknown.

Hoping to get a solution soon so I can get the laptop in question done.

Thanks.

I made the configuration change (took me a bit to find where to make that change) and started another upload task.

Results: Seems to be working! I’ll hold off on being certain its fixed until it’s completely uploaded, but I have no reason to believe it won’t right now.

Thanks for the quick replies. Would have taken me a lot longer to have spotted that configuration error. If anything pops up, I’ll reply here, but this upload won’t be for a while as the hard drive is quite large and I’m only able to upload over a 100MB LAN connection.