"PXE-T00: File name too long" on some machines

[Junkhacker]

@yochaigal u.kpxe still has 4 characters after the period, that may be causing issues if it’s trying to adhere strictly to 8.3 format (disclaimer: i haven’t looked at the pcap file)

[yochaigal]

@Junkhacker Oh right, that makes sense!

Well, I changed the name to undionly.pxe (8.3) - same issue. Uploaded new pcap file.
0_1463151170763_too_long.pxe.pcap

[Wayne Workman]

@yochaigal Can you check for a firmware update for this troublesome target host?

[Junkhacker]

could you try renaming the file to undionly.0 ?

[yochaigal]

@Junkhacker Done. Same problem:
0_1463154351281_undionly.0.pcap

[yochaigal]

@Wayne-Workman I already did - it is using the “latest” release (late 2011).

http://support.lenovo.com/us/en/products/Laptops-and-netbooks/Lenovo-V-Series-laptops/Lenovo-V570-Notebook/1066/A9U/downloads/DS027341

[yochaigal]

Here’s a more general question:

I’ve setup FOG for my computer repair business; we install Win/Mac/Linux on a daily basis on all sorts of different hardware scenarios; we were originally looking into MDT until I found this amazing FOSS solution, that so far works great!

However, In instances where I’m dealing with different hardware on a regular basis, what is the best “fallback” scenario? Is there an alternative PXE booting utility I could use in these cases? I’ve already tried PLOP but had the same issue.

Thanks

[Junkhacker]

you could try this http://ipxe.org/download
burn to cd or make a usb boot drive. this will load an ipxe network boot rom into memory and boot to it, instead of the network card’s onboard boot rom

[yochaigal]

@Junkhacker Yeah, this totally worked! That’s really all I need; I doubt I’ll see another of these machines for some time.
Thanks so much you guys! Consider this thread solved. I really appreciate how quickly people here responded; I’ll try to help others in turn (at least, as much as I can!).

[Sebastian Roth]

Great to hear that you guys found a workaround to this. Thanks a lot for the pcap file anyway. It actually shows exactly what the error message is saying. I wouldn’t believe it if it wasn’t in the pcap! That machine is requesting not just undionly.kpxe but undionly.kpxe\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377....
Looks like it’s padding the string with EOL (end of line) symbols. I have no idea why that is. If PXE booting is working fine for you with all the other machines you are perfectly fine with booting this one via the iPXE cd image! Don’t bother about it.

[piercerob]

Simple solution to file name too long is Long Path Tool.

[Sebastian Roth]

@piercerob Can you explain what you mean? From my point of view there is no simple tool that can help you fix this.

[yochaigal]

@sebastian-roth I worked around the issue using an iPXE boot ISO.