TFTP issues
-
I was able to install FOG .33 on ubuntu 13.10. I got the server all set up, able to log into the gui and pulled a image from a sysprepped windows 7 machine. After doing that PC’s will no lionger connect to the server, they just get a tftp timeout. I am not using a windows dhcp server if that helps. What would have changed or what could I check on ubuntu or fog?
-
Go under the fog configuration page and find the TFTP Server category(almost at the bottom).
Click it to expand the settings, check the password, type in your password and then open a terminal to the server and type
[CODE]sudo /etc/init.d/tftp-hpa restart[/CODE] -
command not found.
-
[quote=“David Schneider, post: 26189, member: 23828”]command not found.[/quote]
Sorry it’s actually
[CODE]sudo /etc/init.d/tftpd-hpa restart[/CODE] -
Did not change anything. It comes up establishes link gets client IP mask shows dhcp ip of my fog server shows the gateway but never gets past tftp
-
And I tried it with multiple machines to make sure it was not isolated to just one.
-
On your ubuntu server type:
[CODE]tftp -v X.X.X.X-c get undionly.kpxe
[/CODE]Where X.X.X.X is your FOG servers IP.
You should get something like this:
[QUOTE]Connected to X.X.X.X(X.X.X.X), port 69
getting from X.X.X.X:undionly.kpxe to undionly.kpxe [netascii]
Received 101962 bytes in 0.1 seconds [11316553 bit/s]
[/QUOTE] -
I just re-installed fog .33 and now is lloading tftp, somehow restarting the process did not fix. Now I am getting a volume not found error message. It looks like the image that I uploaded is still there and the path is correct, don’t know if a reinstall corrupted it somehow. On the client pc it showed this as an error -------volume not found /stdin.001----- that is not the image path shown in the fog gui it is under images/xxxxxxx. I will try and re-upload the image. On a side note this is my first attempt at using fog in any way. Not going so well thus far.
-
Let us know what happens after you re-upload the image.
-
That worked out just fine. Sorry for all of the questions but I have another one. The laptops that I am imaging CANNOT be booted back up after they are imaged. Is there something in fog that I am not seeing that will shut the system down after imaging?
-
Are you using the image type “Single disk resizable?”
If so you HAVE to sysprep the images before uploading.
Otherwise use the image type “Multi partition single disk not resizable” and it will work fine.
Just read that again and realized I may have misread that question.
When deploying a task you should get a checkbox that says “Schedule shutdown after task completion”
Click it and the machine will shutdown after the imaging is complete.
-
[quote=“David Schneider, post: 26213, member: 23828”]That worked out just fine. Sorry for all of the questions but I have another one. The laptops that I am imaging CANNOT be booted back up after they are imaged. Is there something in fog that I am not seeing that will shut the system down after imaging?[/quote]
when you schedule a task from the web gui, you can check the box to “schedule shutdown after task completion” then the server will perform a WOL shutdown. This is the only shutdown FOG is capable of performing.
what do you mean by “cannot be booted back up”?
Does the machine physically not respond to button presses?
Does the OS not boot? Does it get stuck? Does it ever display the BIOS info?What I call not booting and what you call not booting could be two different things. I’m not trying to be difficult I’m just trying to understand your issue. Please be as clear and concise as possible.
If the machine doesn’t boot the OS, I would check the image set up under the image store and choose on if the “multipartition” choices just as a test.
-
A request that I got for the machines is that the machine cannot be booted up after imaging the laptops. I don’t know why he just said that they need to be on the domain for the laptop to be loaded up. What I did was took his sysprepped .gho image sent to me on a thumb drive and loaded one of the laptops. After loading the laptop I pulled the image off of it using fog. He just want to be sure that the laptops get shutdown after imaging not booted up to the my sysprep screen. Something there gets corrupted if the initial settings are done off of the Domain.
-
[quote=“David Schneider, post: 26216, member: 23828”]A request that I got for the machines is that the machine cannot be booted up after imaging the laptops. I don’t know why he just said that they need to be on the domain for the laptop to be loaded up. What I did was took his sysprepped .gho image sent to me on a thumb drive and loaded one of the laptops. After loading the laptop I pulled the image off of it using fog. He just want to be sure that the laptops get shutdown after imaging not booted up to the my sysprep screen. Something there gets corrupted if the initial settings are done off of the Domain.[/quote]
Are the machines you are imaging suppose to be part of a domain? if that is no longer required, I would disable these settings before pushing the image to FOG.
I kind of gathered that you are using a .gho image and loading it to the laptop, did you boot the laptop to windows before you pushed it to FOG?
Windows has a process called Sysprep that generalizes the installation so it can be pushed to mulitple machines, if you allowed the laptop to boot after it was imaged and before it was uploaded to fog… Delete your image store, load the .GHO image to a laptop but DO NOT BOOT IT, instead set up a task on the server for an image upload. After the process completes, try to push your image to the laptops.
