Fresh install TFTP open timeout
-
Hello,
I just made a fresh install FOG Server on an Ubuntu 18.04.
I keeps receiving TFTP open timeout when i try to boot in PXE mode.
I took some screenshot of my setup. We have a Windows DHCP server already on ip 192.168.101.51.
Any idea of what it could be ? I used the Wiki about this problem but i cant find what im doing wrong.
All my machine on my network pings it, i can access to the web interface, and on another linux machine i successfully downloaded the undionly.kpxe
Screenshot from my onedrive: https://1drv.ms/u/s!AoRctQ5Tj-ECg7leUGTj6j-QD9kq2g?e=Vv23KB
Thanks you!
-
@dawildqc Well that really didn’t answer my question, but since your dhcp server is on a different site, then the pxe booting computer and the dhcp are probably also on different subnets??
What does your dhcp scope look like for the subnet where the pxe booting computer is?
For that scope do you have dhcp options 66 and 67 set?
Do you have the capabilities to install wireshark on a 3rd computer at the same site where the pxe booting computer is? We may need to grab a pcap of the dhcp process to understand what the pxe booting computer is being told.
-
Is the fog server and pxe booting target computer, and dhcp server on the same subnet?
-
This post is deleted! -
-
@dawildqc Well that really didn’t answer my question, but since your dhcp server is on a different site, then the pxe booting computer and the dhcp are probably also on different subnets??
What does your dhcp scope look like for the subnet where the pxe booting computer is?
For that scope do you have dhcp options 66 and 67 set?
Do you have the capabilities to install wireshark on a 3rd computer at the same site where the pxe booting computer is? We may need to grab a pcap of the dhcp process to understand what the pxe booting computer is being told.
-
@dawildqc Curious why pxe boot screenshot is showing 2 gateway ip addresses… 192.168.5.5 and 192.168.5.7 ? I’d assume that could be an issue with connectivity
-
Based on @Hanz 's post I look at the pictures a bit closer this time.
The fog server and the pxe booting server are on the same subnet 192.168.5.x the dhcp server is on a different subnet 192.168.101.x.
That is OK and fine. We can use the fog server to find out if the pxe client is not being told the right information. If you follow this tutorial to capture a pcap and upload the pcap to a shared drive and then post the link here. I’ll look at it to tell you what is going sideways.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue -
@george1421 Its working now
I forgot my options 66 and 67 on that 192.168.5.x scope!
Thanks you very much!
