@george1421 I got some tricky ways to find if dnsmasq is using the configuration that we created. In the directory /etc/dnsmasq.d/, we created the configuration file, but if there is no other file called README, I think dnsmasq did not use the configuration file. But after I updated dnsmasq, there is a new file called README. And it works!!! I am not sure if my thoughts was right. But it got working in my case.

@Sebastian-Roth Thank you Sebastian. I got it worked. Thank you so much for your patient help. I really appreciate.

@george1421 Hi George, it worked!!! After I made update for dnsmasq. I was thinking about that dnsmasq did not use the configuration that I created to run. So I was updating it and it worked. Thank you.

@george1421 Hi, George. Unfortunately, I still got the same problem here with that issue fixed. My configuration is like this

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,192.168.88.40

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,192.168.88.40
dhcp-boot=net:UEFI,ipxe.efi,,192.168.88.40
dhcp-boot=net:UEFI64,ipxe.efi,,192.168.88.40

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

dhcp-range=192.168.88.40,proxy

@Sebastian-Roth I was having trouble with starting dnsmasq service, saying bad dhcp-range which pointed to the end of the configuration was something wrong. I tried to reinstall dnsmasq service and now it is working now. I am not sure if there is some connection between these two problem.

@Sebastian-Roth Status of dnsmasq:

● dnsmasq.service - LSB: DHCP and DNS server
   Loaded: loaded (/etc/init.d/dnsmasq; generated)
   Active: active (exited) since Tue 2019-07-30 16:02:47 EDT; 9min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4654 ExecStop=/etc/init.d/dnsmasq stop (code=exited, status=0/SUCCESS
  Process: 4655 ExecStart=/etc/init.d/dnsmasq start (code=exited, status=0/SUCCE

Jul 30 16:02:47 genesicadmin-PowerEdge-840 systemd[1]: Starting LSB: DHCP and DN
Jul 30 16:02:47 genesicadmin-PowerEdge-840 systemd[1]: Started LSB: DHCP and DNS

The content of the configuration:

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,<192.168.88.40>

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

# Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,<192.168.88.40>
dhcp-boot=net:UEFI,ipxe.efi,,<192.168.88.40>
dhcp-boot=net:UEFI64,ipxe.efi,,<192.168.88.40>

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Booting FOG Client", 1

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot to FOG", undionly.kpxe
pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi
pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi

dhcp-range=<192.168.88.40>,proxy

Because I cannot control the DHCP, so I did what it says in the article.

Hi team, I am trying to image my windows 7 home and I have some problem using PXE boot. I got the error when the computer was booting. I think the target computer did not detect the fog server computer. Even IP address did not appear.

And I have started the dnsmasq service in the Ubuntu computer which installed fogs server. And have configured it with correct content.

@Sebastian-Roth It works!!! Thank you.

@Sebastian-Roth Hi Sebastian, when I entered “mysql -u root -p”, I entered the password and I got the error.
ERROR 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: YES)

And I set up mysql password while installing fog server

This is image that I took.
https://drive.google.com/file/d/1Ov4O9qw32CmGKSzV7DP7SSt_XdwolAaf/view?usp=drivesdk

Hi team, I just installed Ubuntu 18 and trying to install fog server. And the installation was getting well until these command appeared:
You still need to install/update your database schema.
This can be done by opening a web browser and going to: MyIP/fog/management
Press [Enter] key when database is updated/installed.

But when I opened my browser and entered the address, it said database connection unavailable. And I tried the method in the article.

But when I entered the mysql with root, I came to MariaDB instead of mysql. And I could not run that command because of SQL syntax( I think maybe there are some differences between MariaDB and MySQL)

So what should I do to finish installing fog server?

@Sebastian-Roth Hi Sebastian, I reboot the system and now when I enter the command, it prompted ‘Enter password’, I just click enter and now the error came
'ERRO 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: NO). Because last time I entered some command I found in the internet, I did not want that to influence our process so I reboot. Last time, I restarted MySQL and entered ’ sudo mysqld_safe -skip-grant-tables’

@Sebastian-Roth Hi Sebastian, when I enter the command, I directly went to the MariaDB instead of MySQL

After fixing the network PXE booting problem, I came into another issue here. While installing the fog server to my ubuntu 18, I did not enter any password when asking me about the password for mysql. So right now I cannot access mysql and it gave me the error that ‘Access denied for user ‘root@localhost’ (using password:NO)’ So after finishing the image, an error came in saying something wrong because of the denied database. Is there any solution for this? Right now when I enter mysql command, I came to a MariaDB instead of mysql.

@george1421 it is working now !!! I think I did this before like what it says in the fog server wiki. But this time after editing with your same configuration, my windows 7 began to image. Thank you so much for helping me solving this problem. Thank you!!!

@george1421 I used method 2 to set the DHCP. The link is the picture taken when booting.
https://drive.google.com/file/d/14OLcAnl0gqqjGk6AWl8fstnL7fiSpiH3/view?usp=drivesdk

@george1421 I am using my company’s network, and two computers are using the lans near by. So I think they should be in the same IP subnet.

@Quazz Hi Quazz, I think you are right. Because I have set up the ProxyDHCP and when booting the client computer could find the fog server IP. So right now I think it is the THTP that has some issues. Look like the client computer could not find the booting file in fog server IP. How could I solve this problem.