@ch3i No because now I cant log in… not sure what happened but when I enter the correct credentials into the webUI it just clears the 2 fields and does not log in, nor does it give me an invalid login notice like it would if I used the incorrect credentials.
Latest posts made by alorsung
-
RE: Captured images not moving from */images/dev to */images/<hostname>
-
RE: Captured images not moving from */images/dev to */images/<hostname>
@Quazz understood, thank you for clarifying.
-
RE: Captured images not moving from */images/dev to */images/<hostname>
Even though, it completely captures the image but just isnt moving it? That can be caused by FTP credential problems?
-
Captured images not moving from */images/dev to */images/<hostname>
I have my FOG server up and running but after it completes the process of capturing the image, the image sits in /dev with the MAC as the folder name. I understand that FOG is supposed to execute a script upon completion to rename the folder and move it.
I have ensured that all of the directories are correct in the configs and the UI. The */images/dev has been chmoded to 777 recursive, and the FTP password are all synonymous.
Not a clue at this point how to get that portion of the server working. Ive checked all the forums and posts and done everything suggested by others, but none of them are taylor-made to my issue.
Thank you!
-
RE: TFTP/PXE timeout Linux server to Windows PXE boot
@Wayne-Workman I just pulled the current version, wanted to see what new features, if any, were added.
-
RE: TFTP/PXE timeout Linux server to Windows PXE boot
Wasnt selinux… that is disabled by default on our centos 7 templates. Also firewalld has tftp service allowed as well as corresponding ports.
I found the issue and its kind of silly, but FOG02 has version 7180, which is slightly newer than the version on FOG01 and so, in the tftp config i added:
-r
blksizeto the end of “server_args” setting, restarted the xinetd service and it worked. End result:
server_args = -v -s /tftpboot -r blksize
I chalked it up to being an issue with versions of FOG or possibly the TFTP server running on the two VM’s because the configs were identical before I made that adjustment.
Hope this helps anyone else facing this problem.
-
TFTP/PXE timeout Linux server to Windows PXE boot
I am not sure if there specific forum exists with my specific problem but I have read through tons of posts on multiple websites regarding this same issue, but what’s worked for other doesn’t work for me.
I have a working FOG server with 4690 installed on a VM that is stored locally in our office on CENTOS7. I just built a new CENTOS7 FOG server but it’s on our Rackspace hypervisors in Dallas.
I have compared the config files, firewall settings, services DHCP settings on our windows domain controller (Yes I have option 066 and 067 enable and pointing to the server that is running FOG/TFTP as well as the correct bootfile undionly.kpxe). But still the client machine which we have imaged ton of with our working server FOG01, will not get past “TFPT…” portion with out timing out with the error PXE-E32 TFTP open timeout.
I was able to successfully TFTP the bootfile to my mac via terminal I also tried switching subnet’s from FOG01 to the new FOG02 server and the FOG01 server was able to grab the bootfile and load the image. Which leads me to believe SOMETHING on my new FOG02 server isnt working, but again ive compared all the applicable configs, etc… between FOG01 and FOG02 and it’s all identicle.
Racking my brain here! Anything helps.
Thanks!