PXE Problems (random)
-
Hello,
I use Fog for quite a long time now.
Never experienced any problems.
But since the new Fog 1.2.0 I have some strange things.- My PXE won’t work good:
This is the error
[QUOTE]
[FONT=Tahoma]TFTP.
PXE-T00: File name too long
PXE-E36: Error received from TFTP server
PXE-M0F: Exiting PXE ROM.[/FONT][/QUOTE]The most strange thing is that it is only with HP 4520s Laptops and normal desktops.
What can i do about it.
Second thing is, when i wanna upgrade the FOG kernel; the following error shows up:
[QUOTE]FOGFTP: Failed to put file. Remote Path: /var/www/fog/service/ipxe/bzImage, Local Path: /tmp/bzImage, Error: ftp_put() expects parameter 1 to be resource, null given[/QUOTE]Hopefully someone can help me further!
Regards,
John
- My PXE won’t work good:
-
Use DNSMASQ to serve your bootfile and server information.
This should alleviate the TFTP errors you are experiencing.
Is there a specific reason you want to update the kernel? After you set up DNSMASQ if you have issues booting a device to the PXE menu, I would look into updating the kernel.
As for the kernel, have you thought about backing up your current kernel and manually downloading he new one?
-
Hello Jaymes,
Maybe there is a connection between the problems… So that was the idea to update the kernel.
But first i wanna check your solution out.Thanks in advance…
-
Definitely give the DNSMASQ a shot, I have to use this because my Novell network is sorely outdated and won’t support the length of the bootfile name either
Then if you still have issues come back and I would be happy to help you update your kernel.
-
Oh… Just for the information, the DHCP server is on another machine… is that a problem?
-
Does the DHCP server have the proper scope options specified (either Option 66 – IP of tftp server or next-server (and/or) Option 67/filename – undionly.kpxe)
-
i will check that out Tom… thanks
-
With DNSMASQ you don’t need the DHCP on the server and you don’t need to adjust scopes. You supply all the information in the ltsp.conf file.
-
Jaymes… The PXE is also coming from another server… so… uhm… I feel myself a n00b right now…
-
So your FOG server is not supplying your PXE or your boot menu?
-
Could you give us a better understanding of your network and servers?
-
sure:
I have a DHCP Server: 192.168.50.1
And a PXE Server: 192.168.50.95
I’m now asking the network manager if i can get the pxe-settings, once i have that i will post it here!! -
Hey John,
I am having the exact same issue when trying to upgrade my kernel to one of the latest versions. I also use our networks DHCP server that points to the FOG Server and Bootfile name undionly.kpxe. Though, I have no issues getting my machines to pxe boot into the FOG menus. Is there a known solution to this outside of using the FOG server for DHCP?
-
@Ahagel Can you type out (or post a photo of) the exact error?
Also, take a look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP
-
@Wayne-Workman Here you go. I will look at the TFTP troubleshooting steps as well. Thanks.
-
@Ahagel I’d recommend ensuring your FTP stuff is correct as well… https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
and perhaps reinstall FOG using the installer you have and see if your issues are resolved.
-
@Ahagel said:
Is there a known solution to this outside of using the FOG server for DHCP?
You can use Windows DHCP. You could even use ProxyDHCP (dnsmasq).
The TFTP article I posted links to those topics.
