Thanks Jaymes,
Yes I restart dnsmasq.
Now, I remove the server name, and make the symlink to undionly.0 (don’t understand why have to do it to this file?) in the ltsp.conf Irefer to undionly.kpxe.
The proxy thing, I don’t know, may be in my newtork this doesn’t work?
thanks again.
[ATTACH=full]1535[/ATTACH]
P.S. I have my dhcp with
[B]next-server 10.1.8.1;[/B] and [B]filename “undionly.kpxe”[/B];
EDIT:
I ask IT dhcp server personal to remove those options but now no offers.
So I give up dsnmasq.
Try without it.
Thanks again Jaymes.

[url=“/_imported_xf_attachments/1/1535_20141203_162141.jpg?:”]20141203_162141.jpg[/url]

[LEFT]I can not put my server running.
Because the pxe does not work , or the menu is displayed but can not register a client.
So I gave a change to the notorious dnsmasq , but now freeze.
here is my config.[/LEFT]
[CODE]administrator@fogserver:~$ sudo nano /etc/dnsmasq.d/ltsp.conf
GNU nano 2.2.6 Ficheiro: /etc/dnsmasq.d/ltsp.conf

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,fogserver,10.1.8.1

rootpath option, for NFS

#dhcp-option=17,/images

kill multicast

#dhcp-option=vendor:PXEClient,6,2b

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

PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.

pxe-prompt=“Press F8 for boot menu”, 3

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 from network”, undionly

This range(s) is for the public interface, where dnsmasq functions

as a proxy DHCP server providing boot information but no IP leases.

Any ip in the subnet will do, so you may just put your server NIC ip here.

Since dnsmasq is not providing true DHCP services, you do not want it

handing out IP addresses. Just put your servers IP address for the interface

that is connected to the network on which the FOG clients exist.

If this setting is incorrect, the dnsmasq may not start, rendering

your proxyDHCP ineffective.

dhcp-range=10.1.8.1,proxy
[/CODE]
my /tftpboot folder
[CODE]drwxrwxrwx 2 fog root 4096 Dez 3 15:15 .
drwxr-xr-x 25 root root 4096 Dez 3 10:19 …
-rwxrwxrwx 1 fog root 840 Dez 3 10:19 boot.txt
-rwxrwxrwx 1 root root 290 Dez 3 10:19 default.ipxe
-rwxrwxrwx 1 fog root 389009 Dez 3 10:19 ipxe.kkpxe
-rwxrwxrwx 1 fog root 389057 Dez 3 10:19 ipxe.kpxe
-rwxrwxrwx 1 fog root 388044 Dez 3 10:19 ipxe.krn
-rwxrwxrwx 1 fog root 389073 Dez 3 10:19 ipxe.pxe
-rwxrwxrwx 1 fog root 25340 Dez 3 10:19 memdisk
-rwxrwxrwx 1 fog root 16794 Dez 3 10:19 pxelinux.0.old
-rwxrwxrwx 1 fog root 165088 Dez 3 10:19 snponly.efi
-rwxrwxrwx 1 fog root 101989 Dez 3 10:19 undionly.kkpxe
lrwxrwxrwx 1 root root 19 Dez 3 15:15 undionly.kpxe -> undionly.kpxe.INTEL
-rwxrwxrwx 1 fog root 0 Dez 3 12:36 undionly.kpxe.INTEL
-rwxrwxrwx 1 fog root 102037 Dez 3 10:19 undionly.kpxe.REAL
-rwxrwxrwx 1 fog root 102053 Dez 3 10:19 undionly.pxe
-rwxrwxrwx 1 fog root 147728 Dez 3 10:19 vesamenu.c32
administrator@fogserver:/tftpboot$[/CODE]
[LEFT]Now ipxe don’t boot.[/LEFT]
[ATTACH=full]1533[/ATTACH]
[LEFT]
Some advice or help please.
Thanks
Pedro Valente[/LEFT]

[url=“/_imported_xf_attachments/1/1533_20141203_154418.jpg?:”]20141203_154418.jpg[/url]

thanks

[quote=“Tom Elliott, post: 39016, member: 7271”]Okay,

I don’t know what setup was around in 0.27 for NFS, but I do know the NFS setup proto changed from UDP to TCP.

That said, I’m just guess here ,that 0.27 was before a required file (.mntcheck) was created.

Check to ensure permissions are set proper with:

[code]sudo touch /images/.mntcheck
sudo touch /images/dev/.mntcheck
sudo chown -R root:root /images
sudo chmod -R 777 /images[/code]

Then try imaging?[/quote]
Done.
But no luck.
May a kernel issue?

In fog configuration -> kernel update.
the 64 or 32 bits is refeing to the server or to the clients.
sorry I’m a noob.
thanks

[quote=“Tom Elliott, post: 39013, member: 7271”]We need quite a bit more information.

First, did you copy images from another system to the fog server?

Second, what version of FOG are you running?

What OS is FOG installed on?[/quote]

Hi Tom, and thanks for the quick reply.
No copy, this is a Fog server comming from 0.27, only had issues after update ipxe.
But on trying to fix may be spoil something.
running fog 1.2.0
ubuntu 12.04.5 lts
thanks

Hi,
This is my problem
When try to upload an image.
I tried every file in tftpboot but with no luck.
My firewall is disable.
NFS service is running.
Need help.
Thanks.

[url=“/_imported_xf_attachments/1/1503_20141112_145935.jpg?:”]20141112_145935.jpg[/url][url=“/_imported_xf_attachments/1/1504_20141112_151434.jpg?:”]20141112_151434.jpg[/url]

hi, my doubt is if the kernel 32 or 64 is for the fog server or for the hosts architecture?
thanks.