I see no setting for boot file name, but I’m not used to linksys’ new interface. I’ll give it a bit longer but I think I’m going to go with my backup plan

again thanks for the help

The new Linksys EA6400 is doing the dhcp

FOG_TFTP_HOST = 192.168.1.200
FOG_PXE_IMAGE_DNSADDRESS = 127.0.0.1
FOG_WEB_HOST = 192.168.1.200
fog was installed without dhcp
(didn’t change any of these its what they have been since the reinstall after router died)
error still persists

again thanks for the help

ubuntu is 12.04
fog is 0.32
router was changed from a dlink so the static ip is now 192.168.1.200 (was previously 0.200 but changed when reinstalling ubuntu and fog after dlink died)
first switch is an unmanaged dllink dgs-1016D
second switch is a 3com superstack 3 4200 (cant find a definitive answer on if its managed or not)
also I was able to pull and deploy an image fine before the router switch and reinstall of ubuntu and fog (forgot that in original post)

Again many thanks for the help

Hi
I volunteer at a place called computers for schools, had fog running and was going to do a muticast test. when our router decided to give up the ghost (literally minutes before doing the test) so it was replaced with a linksys EA6400. Instead of trying to reconfigure it to work with the new router I just reinstalled ubuntu and fog, but when i try to pxe boot anything I am greeted with a :
pxe-e53 no boot file name
directly followed by
pxe-M0F exiting intel boot agent.

The fog server is directly connected to the linksys router any computers to be imaged are behind an additional 2 switches.

Thanks in advance for any help, speeding up the process of refurbishing these old computers will let us focus on our sizeable pile of E-waste