@tallier Nor sure of we understand what you mean by “image de Fog”. Do you mean the captured image - probably a Windows installation?

@Mike-Fahey Just tried on a 1.5.9 install and it works perfectly fine for me (Firefox on Debian).

Possibly a browser or caching issue? Trycleaning the cache and using other browsers.

@sebastian-roth We don’t have a proxy server. Our iBoss web filter might be something I need to look at.

From what I’m finding this may be a router issue. I created a VM FOG server on VLAN 192, connected the client to the same VLAN and successfully PXE booted. When I plugged in the client to VLAN 194, PXE times out on http again. Are there any suggestions to resolve this?

I saw in this post https://forums.fogproject.org/topic/12368/fog-dhcp-server-on-multiple-vlan-network/4 mention of properly configuring Windows 2012 DHCP by Goerge1421. He also mentioned PXE roms may be an issue.

"Lets take a step back here. With such a complex network why are you using the FOG DHCP server instead of your network infrastructure dhcp servers?

FOG does work across subnets, what you need is the dhcp server responsible for those other subnets to set dhcp option 66 to the fog server IP and dhcp option 67 to the boot kernel. The issue you will run into now is that if you have both bios and uefi systems on your network, your dhcp server will need to be smart enough to send the right boot kernel name based on the target hardware. Windows dhcp on 2012 and newer will do this correctly if configured right. Linux dhcp server does that automatically like FOG uses.

If you have inter vlan routing working correctly, you can/should be able to image with FOG. There are some pxe roms that are not very smart and may not like pxe booting across subnets.

Instead of messing with all of these dhcp helpers, you should take a step back and answer what device provides your dhcp services for these other subnets?"

@omegaxis said in Failed to get IP VIA DHCP:

I am able to pxe boot vm’s within the server just fine

when I try to boot a thin client that is attached to the same cisco catalyst 2960g switch, i am getting the dreaded failed to get ip error.

Meraki mx64 functioning as DHCP
Cisco Catalyst 3750-E as backbone
catalyst 2960g as endpoint switch where both the server and the computer I am trying to pxe are.

So lets think about what I’ve outlined. You can pxe boot a VM on the hypervisor just fine. But a physical machine attached to your 2960g can’t get ip error.

Is your meraki dhcp server issuing ip addresses to the VM, or is that coming from some other dhcp server? If you plug a windows computer into the 2060 does it get an IP address? Is the virtual switch where your FOG server is connected bridged to the physical network or is it Nat’d? (I don’t know unraid as a hypervisor to give directions to check) We may want to get a pcap (packet capture) of the pxe booting process to know what is really going on. We can/should use the fog server to capture its side and then a witness computer with wireshark to capture the virtual side. I have a tutorial on using the fog server to grab a pcap. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue for wireshark you can use the capture filter of port 67 or port 68 if you don’t use a capture filter you can use a display filter of bootp. Capture both the what fog server sees and what the witness computer sees. My guess is the FOG server will not see the dhcp request.

Looking at the pcap you should see a typical DORA response.
Discovery (client sends)
Offer (server sends)
Request (client sends)
Ack (server sends)

If you look into the Offer packet, the dhcp server should set the {next-server} and {boot-file} fields in the ethernet header as well as dhcp options 66 and 67 in the options section. Both groups need to be there.

In my experience using a router or switch as a dhcp server does not give good luck because many do not handle the dhcp pxe boot settings well. Many for some reason will list the router/switch as the {next-server} even if they have a setting for a boot server. In this case you need the fog server IP configured in {next-server} and dhcp option 66.

@goll420 Ok here is a quick explanation of why the suggestion. iPXE has 2 basic sets of boot loaders. One boot loader has all of the known network drivers installed and only uses a single standard driver that interfaces with the firmware on the network card. This is the same idea for both bios and uefi.

For bios the standard driver is undionly.kpxe (fog recommended)
For bios with the all included network driver its ipxe.kpxe

For uefi the standard network driver is snponly.efi
For uefi the all included network driver is ipxe.efi (fog recommended)

For the FOG recommended boot loaders. The undi driver for bios is very old (~20 years) and very stable. The snp driver for uefi is new (~6 years) and in the early days not very dependable. That is why FOG recommened the ipxe.efi (all native drivers). With new hardware coming out the iPXE boot loader community can’t keep up with really new hardware and the snp network drivers are getting more mature. So the FOG developers at some time may switch their recommendation to the snponly.efi, but not today.

One last bit of info, its up to the network card manufacturer to write the proper snp driver into the network card’s firmware. Some do this better than others.

@Mike-Fahey Which mysql command do you use to connect to the database?

The installer uses the following command to login and check if it was successful:

mysql --host=localhost --user=root --password="yoursecurepassword" --execute="quit" [[ $? -ne 0 ]] && echo "Connection failed" || echo "Connection succeeded"

@sebastian-roth Thanks to your suggestions I took a deeper look at the host server I was provided for this project, and there was a lot of driver packages missing. Once I installed those drivers, everything loads at a good speed now.

In the end it was my mistake not looking over the host server my colleague prepared for me, but I learned a lot more about FOG in the process so it wasn’t all time wasted.

I appreciate the help though, sorry if I confused you there

@sebastian-roth No problem i can create separate images for same sized disk but first milestone is to make sure it is possible. I will give it a try and share here.

@george1421 said in Dell Optiplex 3080 - UEFI - PXE Boot E-21: Remote boot cancelled.:

Side note: If your network doesn’t have a dhcp server I would personally use isc-dhcp server on your fog server over dnsmasq. I would use dnsmasq if you have a dhcp server run by someone else and can’t update settings. In this case dnsmasq would supplement your unchangeable dhcp server.

THANK YOU!

I set up isc-dhcp and it’s working like a charm.

For any future people reading:
I modified /etc/dhcp/dhcp.conf with the below config.
I disabled dnsmasq. systemctl stop dnsmasq.service
I started isc-dhcp service dhcpd start
I tsuccessfully PXE booted with my Dell 3080 a few times.
I permanently disabled dnsmasq. systemctl disable dnsmasq
I set isc-dhcp to start automatically. systemctl enable dhcpd

option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option arch code 93 = unsigned integer 16; # RFC4578 use-host-decl-names on; ddns-update-style interim; ignore client-updates; next-server 192.x.x.7; authoritative; subnet 192.x.x.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; range dynamic-bootp 192.x.x.200 192.x.x.254; default-lease-time 21600; max-lease-time 43200; option domain-name-servers 192.x.x.7; option routers 192.x.x.7; class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } }

@mmethe Not sure what’s wrong but you might try setting the ownership: chown fog:root /images/dev/postinitscripts/fog.postinit (note: the user fog exists in older versions only. After the update to 1.5.9 it will be called fogproject)

@mapaga said in Windows 7 Deployment Error:

Just for curiosity, why is it important to caputre all partitions?.

Because only with all partitions it will also capture and deploy the partition table. If you set this to a single partition, it will only capture/deploy this partition and won’t touch the partition layout. This is ok if you have the correct layout on the destination system already but will fail otherwise.

@cammykool said in Unable to restore GPT partition tables on one image:

this is the stuff that broke after that init move.

That has nothing to do with the init change. The version information in the FOG web UI is pulled from the fogproject.org server and I would guess either there was a connection issue or your network admin restricted access to this URL.

@tom-elliott I tested on another computer and its working.

on this particular pc its not working. I will try and uninstall fog client from the pc and reinstall it again and will see if it works.

IF it still doesnt work will try to remove from fog server and re add

@sebastian-roth Thank you ! That does it perfectly. I didn’t know that command. Have a good day !

@george1421 I ended up looking for FOG 1.4.4 kernel update issues and found the permissions missing issue and followed what the guy did there. I’m not getting an error anymore.

@fargat There is far too little information to accurately assist you.

Here’s the details we have, so far:
You have FOG Server running on Ubuntu 20.04.
You have Sophos Firewall as DHCP server.
You have tried DNSmasq but it did not work.
You have tried FOG using a Lenovo laptop.
Based on the picture, the laptop is attempting to boot using UEFI stack.

That’s all we have.

We would need:
What version of FOG are you running?
What configuration did you use for DNSmasq?
What DHCP options 66/67 are defined on your Sophos Firewall DHCP Server?
What model of Lenovo laptop are you using? (There are many different models.)
Have you disabled Secure Boot?

There’s most likely going to be many more questions, but a picture and “Firewall is …” doesn’t really help us. Neither are any of the follow up responses you’ve given.

Here’s some resources:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq

As @EduardoTSeoane has told you, based on the picture your machine is using UEFI stack for booting, but it’s calling the legacy boot file (undionly.kpxe should be ipxe.efi).