I hope that this helps:

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. Με επιφύλαξη κάθε νόμιμου δικαιώματος.

C:\Users\hk>tftp -i 192.168.1.5 get ipxe.efi
Transfer successful: 934816 bytes in 1 second(s), 934816 bytes/s

C:\Users\hk>tftp -i 192.168.1.5 get i386-efi/ipxe.efi
Transfer successful: 852160 bytes in 1 second(s), 852160 bytes/s

hk@debian-server:~$ ls -al /tftpboot/ipxe.efi /tftpboot/i386-efi/ipxe.efi

-rw-r--r-- 1 fog root 852160 Mar 27 17:05 /tftpboot/i386-efi/ipxe.efi

-rw-r--r-- 1 fog root 934816 Mar 27 17:05 /tftpboot/ipxe.efi

0_1459164590543_tftp_issue.pcap

@Sebastian-Roth said:

@hariskar Ahhh, now I see. Your client seams to be a 32 bit machine. But your 32 bit ipxe.efi binary is missing!

cd /tftpboot
sudo mkdir i386-efi
sudo wget -O i386-efi/ipxe.efi "https://github.com/FOGProject/fogproject/blob/dev-branch/packages/tftp/i386-efi/ipxe.efi?raw=true"
sudo chown fog i386-efi

Then try booting the win10 UEFI client again and see if it works. The missing 32 bit UEFI binary is something Tom and I fixed in the installer just a few days ago. So if you update to the latest version this would be fixed as well. But with the above mentioned commands you can do this yourself very easily.

I made a clean installation of latest trunk.
Again the same:
With:

dhcp-match=set:bios,60,PXEClient:Arch:00000
dhcp-option-force=tag:bios,66,192.168.1.5
dhcp-option-force=tag:bios,67,"undionly.kpxe"

dhcp-match=set:efi32,60,PXEClient:Arch:00006
dhcp-option-force=tag:efi32,66,192.168.1.5
dhcp-option-force=tag:efi32,67,"i386-efi/ipxe.efi"

dhcp-match=set:efibc,60,PXEClient:Arch:00007
dhcp-option-force=tag:efibc,66,192.168.1.5
dhcp-option-force=tag:efibc,67,"ipxe.efi"

dhcp-match=set:efi64,60,PXEClient:Arch:00009
dhcp-option-force=tag:efi64,66,192.168.1.5
dhcp-option-force=tag:efi64,67,"ipxe.efi"

Checking Media Presence
Media present
Starting PXE over IPv4
Station IP address is 192.168.1.2
Server IP address is 192.168.1.1
NBP filename is ipxe.efi
NBP filesize is 0 Bytes
PXE-E99: Unexpected network error.

I will try it.

Also my Windows 10 are 64bit.

What about

PXE-E32 TFTP open timeout

in the BIOS windows xp PC? It started when I put the 12 lines in DNSMasq.
With

dhcp-boot=undionly.kpxe,x.x.x.x

it was OK.
Maybe there is a connection between the 2 issues of the 2 PCs?

Thank you!

In my previous post I made the attempt to get undionly.kpxe from fog server. Here is the correct attempt:

C:\Users\hk>tftp -i 192.168.1.5 get undionly.kpxe
Transfer successful: 92104 bytes in 1 second(s), 92104 bytes/s

C:\Users\hk>

tftp -v 192.168.1.5 -m binary -c get ipxe.efi

How can I do it from windows console?

hk@debian-server:~$ ls -al /tftpboot
total 4868
drwxr-xr-x  3 fog  root   4096 Mar 21 12:04 .
drwxr-xr-x 25 root root   4096 Mar 21 12:04 ..
-rw-r--r--  1 fog  root    840 Mar 21 12:04 boot.txt
-rw-r--r--  1 root root    426 Mar 21 12:04 default.ipxe
-rw-r--r--  1 fog  root 199104 Mar 21 12:04 intel.efi
-rw-r--r--  1 fog  root  92505 Mar 21 12:04 intel.kkpxe
-rw-r--r--  1 fog  root  92553 Mar 21 12:04 intel.kpxe
-rw-r--r--  1 fog  root  92510 Mar 21 12:04 intel.pxe
-rw-r--r--  1 fog  root 913472 Mar 21 12:04 ipxe.efi
-rw-r--r--  1 fog  root 849920 Mar 21 12:04 ipxe.iso
-rw-r--r--  1 fog  root 328877 Mar 21 12:04 ipxe.kkpxe
-rw-r--r--  1 fog  root 328925 Mar 21 12:04 ipxe.kpxe
-rw-r--r--  1 fog  root 328396 Mar 21 12:04 ipxe.krn
-rw-r--r--  1 fog  root 328727 Mar 21 12:04 ipxe.pxe
-rw-r--r--  1 fog  root 123448 Mar 21 12:04 ldlinux.c32
-rw-r--r--  1 fog  root 187820 Mar 21 12:04 libcom32.c32
-rw-r--r--  1 fog  root  26468 Mar 21 12:04 libutil.c32
-rw-r--r--  1 fog  root  26140 Mar 21 12:04 memdisk
-rw-r--r--  1 fog  root  29208 Mar 21 12:04 menu.c32
drwxr-xr-x  2 fog  root   4096 Mar 21 12:04 pxelinux
-rw-r--r--  1 fog  root  43186 Mar 21 12:04 pxelinux.0
-rw-r--r--  1 fog  root  43210 Mar 21 12:04 pxelinux.0.old
-rw-r--r--  1 fog  root 198656 Mar 21 12:04 realtek.efi
-rw-r--r--  1 fog  root  93324 Mar 21 12:04 realtek.kkpxe
-rw-r--r--  1 fog  root  93372 Mar 21 12:04 realtek.kpxe
-rw-r--r--  1 fog  root  93380 Mar 21 12:04 realtek.pxe
-rw-r--r--  1 fog  root 197920 Mar 21 12:04 snp.efi
-rw-r--r--  1 fog  root 198112 Mar 21 12:04 snponly.efi
-rw-r--r--  1 fog  root  92056 Mar 21 12:04 undionly.kkpxe
-rw-r--r--  1 fog  root  92104 Mar 21 12:04 undionly.kpxe
-rw-r--r--  1 fog  root  92174 Mar 21 12:04 undionly.pxe
-rw-r--r--  1 fog  root  29728 Mar 21 12:04 vesamenu.c32

Thank you!!

tftp -v 192.168.1.5 -c get undionly.kpxe
Connected to 192.168.1.5 (192.168.1.5), port 69
getting from 192.168.1.5:undionly.kpxe to undionly.kpxe [netascii]
Received 92825 bytes in 0.1 seconds [13246522 bit/s]

Also in /tftpboot ipxe.efi Size 892.1KB (913,472Bytes)

With:

dhcp-match=set:bios,60,PXEClient:Arch:00000
dhcp-option-force=tag:bios,66,192.168.1.5
dhcp-option-force=tag:bios,67,"undionly.kpxe"

dhcp-match=set:efi32,60,PXEClient:Arch:00006
dhcp-option-force=tag:efi32,66,192.168.1.5
dhcp-option-force=tag:efi32,67,"i386-efi/ipxe.efi"

dhcp-match=set:efibc,60,PXEClient:Arch:00007
dhcp-option-force=tag:efibc,66,192.168.1.5
dhcp-option-force=tag:efibc,67,"ipxe.efi"

dhcp-match=set:efi64,60,PXEClient:Arch:00009
dhcp-option-force=tag:efi64,66,192.168.1.5
dhcp-option-force=tag:efi64,67,"ipxe.efi"

I get in the windows 10 uefi pc:

Checking Media Presence
Media present
Starting PXE over IPv4
Station IP address is 192.168.1.2
Server IP address is 192.168.1.1
NBP filename is ipxe.efi
NBP filesize is 0 Bytes
PXE-E99: Unexpected network error.

and it boots into windows

In the windows xp BIOS PC:

PXE-E32 TFTP open timeout

So, since I use a router with dd-wrt firmware as a proxy with DNSMasq I understand that In the page you mention https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_ProxyDHCP_.28dnsmasq.29 this is what I should read. So

dhcp-boot=undionly.kpxe,x.x.x.x
which I till now had for my 2 windows xp bios pcs
becomes:

dhcp-match=set:efi64,60,PXEClient:grafeio2
dhcp-option-force=tag:efi64,66,x.x.x.x # TFTP/FOG server ip
dhcp-option-force=tag:efi64,67,“realtek.efi”
dhcp-boot=realtek.efi,x.x.x.x
dhcp-match=set:bios,60,PXEClient:ergastirio
dhcp-option-force=tag:bios,66,x.x.x.x # TFTP/FOG server ip
dhcp-option-force=tag:bios,67,“undionly.kpxe”
dhcp-boot=undionly.kpxe,x.x.x.x

for 1 windows xp (bios) and 1 windows 10 64 (uefi)??

Thank you!

After those messages windows logo shows and windows boot.
I use my DD-WRT rooter as DHCP server and put dhcp-boot=undionly.kpxe,192.168.1.5 with
DNSMasq Enabled
Local DNS Enabled

Some days ago I had another configuration:
Boot option 1: PXE network boot (non uefi)
Boot option 2 (Windows Boot manager (uefi))

it boots normally in PXE but then there is another problem: if it does not boot from option 1 it does not fall to boot option 2 and asks for a bootable medium.

So I thought to make both boot options uefi, but now I have the problem mentioned in pos #1.

Thank you for reply!

My Windows XP PC works fine with fog 1.3.0. Edit: works fine with fog trunk.
I have problems with my Windows 10 PC:
I open the Windows 10 PC to register it to fog and it says:
Checking Media Presence
Media present
Starting PXE over IPv4
Succeeded to download NBP file
…and then it goes to Boot option 2 and boots in Windows.

When add manually the host on the fog server and make a task, it opens the Windows 10 PC but it boots into windows after the same message as I wrote above.
In BIOS only UEFI boot options are enabled.
Any help please?
Thank you

Thanks a lot ch3i!

For Windows 10 client is it better to use 1.2.0 or the trunk unstalled on Debian 7.4?
I read that 1.2.0 is compatible although released before Windows 10 and trunk has built in Windows 10 support but is trunk so maybe not very stable. Which should I choose?

Thank you!

Boot mode selection: UEFI and Legacy
Storage Boot option control: Legacy first
Secure boot mode: Standard

Thank you for very fast and great support! (I made a small donation )
I hope that my BIOS problem will be resolved too.

Windows do not start even if they are boot option 2 after the DVD player with PXE deactivated. So, it is not relevant to fog. So my fog problem seems to be resolved. Should I use the trunk from now on, or should I return to stable sometime?

Any idea if some BIOS setting could interfere with Windows in 2 Boot option not booting?

Could it be some BIOS setting? I did not change the defaults. Any idea which BIOS settings could affect Boot 2 option to start after cancelled Boot 1 option?
Thank you

I run them. Nr 4 says that this PC seems compatible with fog. Do you want to post something of this test? If yes please tell me where can I find it.

Yes, this is it…

It is a desktop PC made from different parts.
The motherboard is: Gigabyte Z97P-D3 with firmware F7. What else would be useful?
Do you think it is incompatible?

Thank you.
I changed Exit to Hard Drive Type to 'Exit style" and after Exc it goes again to PXE boot.
Then I changed it to “Grub style” and with Esc it stacks to reboot and choose a correct boot medium. I didn’t put anything in Advanced Configuration Options because I don’t know what.

I did not have this problem with the other PCs, after Esc it continued to boot with Option 2 (Windows)

I made a clean installation of 3480 and with dhcp-boot=undionly.kpxe I registered the new PC and I can network-boot it. Now I have a new BIOS related problem I guess.
With boot option:

1. Windows
   2…

it boots normaly to WIndows

But with:

1.Network Boot
2. Windows

it boots to PXE, but when I cancel it with Esc it does not goes to option 2 and boot Windows but it stacks and tells me to reboot and choose a correct boot disk etc…