TFTP Timeout Issue/First FOG Install
-
When i ran the command and then checked the Status
When i tried to PXE boot after
-
@george1421 Don’t see this file in file veiwer. Is it hidden? what is the best way to copy this stuff over to it?
-
@weltern This last picture “When I tried to PXE boot after”. Is the exact error I want. That sounds a bit strange, but this is what I would expect to happen with only the dhcp server running on your comcast router.
The comcast router says I’m the next server, but it doesn’t provide the boot file.
Now you need to install dnsmasq on your fog server.
It will probably be a command like this:
sudo apt-get update sudo apt-get install dnsmasq
Then paste the config file I posted below into /etc/dnsmasq.d/ltsp.conf
And finally start dnsmasq with this command
sudo service dnsmasq start
. All of these commands I posted here are from memory. They may not be exactly right but they are very close. Note: You may need to do a little research to find the exact command. -
@george1421 Tried what you said but still got the same PXE error as last time now.
The file wasn’t there after it installed so i had to make it. Made it on the desktop and pasted your code into it and them sudo moved it to the location.
The file name is ITSP or LTSP? i have ITSP with the I capital. -
@weltern With linux (unix) case is important.
I just sent you a IM. Look at the bubble on the fog forum tool bar.
-
@george1421 we moved the conversation to IM since turn around time was much quicker.
We got dnsmasq setup with all of the configuration required to pxe boot in a home router environment. DNSMasq probably won’t be needed in a business envionment since a business will typically have a dedicated dhcp server where you can set dhcp options 66 {next-server] and 67 {boot-file}. In the case of the home routers, dnsmasq will provide these missing values.
At this time the OP is able to pxe boot the VM target computer and was in the process of registering the VM with FOG.
Marking topic solved.