@skyborne98 So the saga on this continues, it seems that pushing an image works just fine, but I am now trying to capture an image. As you will see at the beginning of the thread, there was a password conflict during the installation.

I have followed the instructions for Resynching FOG Service Account Password
Screenshot 2023-09-26 080558.png
Thoughts?

The problem is solved.
I disabled DMA protection on the HP ProBook.
Good day.

@orborneee When I installed the new server on May, I had problems with the LDAP autentication. I don´t know if your problem is the same but you can test if works.
Edit the /var/www/html/fog/lib/plugins/ldap/class/ldap.class.php file and comment the line 235:

//@$this->unbind();

Yes, that worked, thank you very much!

@Almeida

The problem is solved.
tftp was closed

Thanks.

@Sebastian-Roth So I did some extensive work and was able to get it resolved.

I suggest a document change in regards to installing on Ubuntu 22.04. FOG client Wiki

In my situation, I did a minimal install and add just a few packages. For the SmartIstaller instructions regarding to Ubuntu 22 they can be minimized to:

sudo apt-get install nuget sudo apt-get install mono-complete sudo apt-get install apt-transport-https

I also have a proxy in my environment and had to set the current environment, with an export command, Example

export http_proxy="http://proxyserver:port/"

@robert70569 This is interesting. I think it would fail earlier when trying to NFS mount the images share on the FOG server in that case. Strange.

@jouni-jokelainen said in Fog and Pfsense 2.7:

Adjusted Pfsense settings for fog (Thanks for these george) :

I guess this topic is solved then. Please open a new issue if you have more questions (not related to pfSense).

@davidgoncalves Also please run the following commands on your FOG server shell and post output here:

mount df -h ls -al /images/dev

@george1421 The campus has it’s own subnet, im changing the problem with it. When I used a VM to test it, desktops in the lab have a hard time trying to connect to the FOG server via pxe boot. It times out after it tries to bring the gui up. So I’m trying to figure out why it keeps timing out. VMs will boot to it fine, but any physical systems either time out or boot fine with it.

This problem is solved after reinstalling new keys.
Running ‘installfog.sh -K’ solved my problem.
Now all images can be used again and no matter what client is installed they all work fine.

🙂

@george1421 If I give you access to any desk on a PC that reaches the 2 servers, would you be able to understand if there is something wrong?

@george1421 any update on a new kernel to be able to try out? Just checking in.

@Wayne-Workman said in How to configure a DNS server？:

I would recommend dnsmasq. Here’s a good simple tutorial. https://stevessmarthomeguide.com/home-network-dns-dnsmasq/Minesweeper

I have never tried dnsmasq. Can you give detailed instructions on how to use it?

@jjurak Is this something you are actively looking to do?

If yes, do you use the fog client program? If yes that will be the problem. The fog client is hard coded to use port 80. I’ve been asking for a few years to decouple the fog client communication port from the management ui. But there has been other issues that have taken priority.

If you are interested in doing this I can probably give you a few areas to look.