Moderators

@Atton So now you can ping the workstation by their short windows names?

@Atton So just to confirm that your fog server’s IP address is hard coded and not set by dhcp?

If its not set by dhcp, I might assume you have a ubuntu or debian based FOG server? If that is the case you will need to go into the network manager application and define the name servers and search domain in that app because each time you reboot the fog server the network manager rewrites that resolve.conf file.

@Atton Ok then something isn’t right.

Do you have an AD domain?
Is the resolv.conf pointing towards your DNS server for AD?

It did run as expected when I included the bash reference at the top of the copy script and changed the mode of the new fog.download script to 755.

You should see the script run right after FOS Linux picks up an IP address. The line will start out with * Running post init scripts.......

You should have a chance to see that message if you run the fog compatibility checker from the iPXE menu.

@pnwbsi I’m currently confirming the patch file method on a development machine.

The first thing I see wrong is in the script I forgot #!/bin/bash to be inserted at the top of the bash script. Also to set the file mode of 755 on the patched fog.download script.

I’ve already updated to tutorial with the missing bits.

I’m going to pxe boot a machine in the next few minutes to make sure it does what I should.

@pnwbsi Hmmm that’s not helpful if the script is not running.

The /bin/fog.download file is on the FOG Linux engine.

@Atton Well we’ll need the names resolution working. So can you ping the hosts using their FQDN?

@Atton Can you ping a windows computer from your fog server using its short name?

If so then it should be setup correctly if you have port 445 enabled on the target computer’s firewall. FOG doesn’t use the simple ping check to confirm the computers online, it uses a connect to port 445 which is a bit more reliable to show the system is actually up than a ping.

There is a FOG service that runs at some interval to refresh the up/down status. That may have not run yet, if you just fixed the name resolver. Rebooting your FOG server should kick everything off again.

@pnwbsi I think we have a new fog.download file with some additional debugging output. This file will not fix the issue, but hopefully it will give us an idea what’s happening. We’ve identified the point in the code where it could be failing.

I have this debug mode fog.download file here:
https://drive.google.com/open?id=1yppCONpwr6zCOXA541rhOfiQNb-LoTYS

What I want you to do is download this new fog.download file. Then I want you to follow these instructions to setup a postinit patch. What we are going to do is dynamically replace the current fog.download in FOS Linux with the debug patched version.

https://forums.fogproject.org/topic/13500/dynamically-patching-fos-using-a-postinit-script

You will follow the instructions but replace the top lines to this

# Current File in FOS Linux to be replaced
currfile="/bin/fog.download"

#Patch file to send to FOS Linux virtual hard drive
newfile="${postinitpath}fog.download"

So the testing protocol I want you to use is this:

1. Confirm you are still getting the error in the picture about unable to mount images folder. Then power off the target computer. Don’t touch the web ui, just power off the target computer.
2. Setup the patching environment per the tutorial
3. Download the fog.download file from my google drive and move it into the postinit directory on the fog server.
4. reboot the target computer
5. When the target computer throws the error again, snap a clear picture of the debugging information. This output will help us understand why…

@Atton If resolve.conf is managed by the NetworkManager (typ ubuntu or debian variant) application then you need to make those settings inside the networkmanager program. The other thing that would overwrite that file is if your fog server has its address defined by dhcp.

I would go ahead and set the file manually and see if something along the way changes it. No guts no glory, I say…