Fog 1.1.1 with ProxyDHCP: /default.ipxe... Connection timed out
I am trying to set up a working fog server with ProxyDHCP. I use this howto:[URL=‘http://www.fogproject.org/wiki/index.php/Setting_up_ProxyDHCP’][COLOR=#555555]http://www.fogproject.org/wiki/index.php/Setting_up_ProxyDHCP[/COLOR][/URL]
If boot a client pc by network I end with this mesage:
[INDENT][I]/default.ipxe… Connection timed out ([url]http://ipxe.org/4c126035[/url])[/I][/INDENT]
Here are some technical details:
Kubuntu 12.04 (updated)
Firewall is turned off
FritzDSL-Router (without any options set that hould cause problems)
Content of /etc/network/interfaces
iface lo inet loopback
iface eth0 inet static
Content of /etc/dnsmasq.d/ltsp.conf
[INDENT][I]# Don’t function as a DNS server:
Log lots of extra information about DHCP transactions.
Dnsmasq can also function as a TFTP server. You may uninstall
tftpd-hpa if you like, and uncomment the next line:
Set the root directory for files available via FTP.
The boot filename, Server name, Server Ip Address
rootpath option, for NFS
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.
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
A boot service type of 0 is special, and will abort the
net boot procedure and continue booting from local media.
#pxe-service=X86PC, “Boot from local hard disk”, 0
If an integer boot service type, rather than a basename is given, then the
PXE client will search for a suitable boot service for that type on the
network. This search may be done by multicast or broadcast, or direct to a
server if its IP address is provided.
pxe-service=x86PC, “Install windows from RIS server”, 1[/I][/INDENT]
Could anybody help please?
thank you for this idea. I already switched to a more reliable solution. I might try Fog in the future again with firewall turned off.
I was having the same problem. The way around it was to turn off the firewall on my router. Let me know if that helps.
[quote=“Meitar Ronen, post: 30549, member: 24536”]I have the same problem…
some clients are succsefully conncting to FOG (and uploading\downloading images) and some get the 4c126035 error…[/quote]
Try different switch gear, there may be a settings on a switch that is preventing information from being passed. If you are using these settings (ltsp.conf), then the settings are correct. If you are successful in booting some but not others, please note the location, the model number, and the nic card. These errors are typically from the ipxe kernel and you should try the most up to date ipxe files that Tom has included for us. I am willing to bet the machines are a different model number of have different hardware.
If moving to a different switch solves the issue, you know where to look/work. If not, I would look into the ipxe files and finally Wireshark to see if the files are getting properly to the destination.
Or you can thread jack, then go start your own thread… I guess that works too -.-
I have the same problem…
some clients are succsefully conncting to FOG (and uploading\downloading images) and some get the 4c126035 error…