TFTP issues with brand new build

[george1421]

@mmoore5553 said in TFTP issues with brand new build:

I changed it from fogproject to the user on the ubuntu box

This is concerned depending on what you changed. That won’t be an issue just yet with pxe booting.

What device is your dhcp server?

[mmoore5553]

i am using our network dhcp server.

I have another fog server on the network that works fine. I am able to isolate to this subnet and it is not working there . I did change back to fog project with the correct password. I even looked at the other settings on fog server and looks correct.

[mmoore5553]

@george1421 i did send you a chat message

[george1421]

@mmoore5553 What error are you seeing on the target computer?

Are/is the fog server and the pxe booting client computer on the same IP subnet?

[mmoore5553]

@george1421 yes we are on the same subnet .

[george1421]

@george1421 said in TFTP issues with brand new build:

What error are you seeing on the target computer?

[mmoore5553]

@george1421 TFTP time out . I get an ip address and subnet mask and dns on the remote computer. Just nothing else after that. I know this computer has no issue. I can put it on another subnet mask and it pulls up on our second fog server. I am creating one for another site.

[george1421]

@mmoore5553 Ok lets see if we can get a pcap of the pxe booting process. We’ll use the fog server to capture what is going down the wire and what the target computer is being told during the dhcp exchange. Please follow this guide and then upload the pcap file to a file share site like google drive, dropbox etc, then post the link here.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

[mmoore5553]

@george1421 I will delete this link once you confirm you received the file

https://drive.google.com/open?id=1SQz6DYi5d_2lZ0KCfHOihjLn5g3GII28

[george1421]

@mmoore5553 Ok you can delete it, lets switch over to IM because the turnaround is faster.

[george1421]

The issue ended up being a configuration problem with the dhcp server. Once that was straightened out the target system pxe booted like expected.