PXE3B: TFTP error - flie not found
-
thats my bad i forgot i manually set my subnet and now its working i set it on the global setting and for got when i first rolled out fog that it was on manually set there its booting now now to test and see if my imaging still works
-
I’m getting this same issue. Can someone describe or give me some more guidance on the 66/67 thing? Thanks!
-
[quote=“Bob Martens, post: 27755, member: 24323”]I’m getting this same issue. Can someone describe or give me some more guidance on the 66/67 thing? Thanks![/quote]
Options 66 and Option 67 are specific for Windows DHCP really, but the intent is more or less the same.
Option 66 is the IP Address of the FOG Server (or wherever you’re trying to boot from)
Option 67 is the filename on the FOG Server (or whatever the file is)
On linux dhcp server the Option 67 is really just the point to the file also known as next-server.
Hopefully this helps.
-
What is the file name without me making any changes?
-
FOG 0.33 and up use undionly.kpxe
FOG 0.32 and below used pxelinux.0 -
That might explain it. I’ll try it tomorrow and report back. Thanks!
-
Well, what you gave me fixed that issue, but now I have machines that will get stuck initializing PXE at boot. When I switch it back to our old server (on the DHCP server that is) then they work just fine.
I’ll keep investigating.
-
[quote=“Bob Martens, post: 27811, member: 24323”]Well, what you gave me fixed that issue, but now I have machines that will get stuck initializing PXE at boot. When I switch it back to our old server (on the DHCP server that is) then they work just fine.
I’ll keep investigating.[/quote]
THere is a known issue with some systems, and we’re trying track down the culprit and/or figure out what will fix it.
If you’re having problems with this, you can try the included undionly.kpxe.INTEL from the svn repo’s.
-
Do you have any instructions on how to include that?
-
Nevermind, went and found it in another thread. I’ll move my responses there.
