Problem after upgrading from 0.32 to 1.1.1

[NickConrad]

[quote=“NickConrad, post: 30457, member: 24656”]the full error was “pxelinux.0: no such file or directory” which is why I figured it was that.

As for undionly, it’s in tftboot as a .kkpxe, .kpxe, .kpxe.INTEL, and .pxe.[/quote]

Tom, the following is my dhcpd.conf located in /etc/dhcp3, did I goof somewhere along the way here?

[INDENT=1]use-host-decl-names on;[/INDENT]
[INDENT=1]ddns-update style interim;[/INDENT]
[INDENT=1]ignore client-updates ;[/INDENT]
[INDENT=1]next-server xxx.xxx.xxx.xxx.[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]subnet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx {[/INDENT]
[INDENT=2]option subnet-mask xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=2]range dynamic-bootp xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=2]default-lease-time 216000;[/INDENT]
[INDENT=2]max-lease-time 43200;[/INDENT]
[INDENT=2]option domain-name-servers xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=3]option routers xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=3] [/INDENT]
[INDENT=2]filename “undionly.kpxe”;[/INDENT]
[INDENT=1]}[/INDENT]
[INDENT=2] [/INDENT]

[Junkhacker]

[quote=“NickConrad, post: 30463, member: 24656”]Tom, the following is my dhcpd.conf located in /etc/dhcp3, did I goof somewhere along the way here?

[INDENT=1]use-host-decl-names on;[/INDENT]
[INDENT=1]ddns-update style interim;[/INDENT]
[INDENT=1]ignore client-updates ;[/INDENT]
[INDENT=1]next-server xxx.xxx.xxx.xxx.[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]subnet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx {[/INDENT]
[INDENT=2]option subnet-mask xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=2]range dynamic-bootp xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=2]default-lease-time 216000;[/INDENT]
[INDENT=2]max-lease-time 43200;[/INDENT]
[INDENT=2]option domain-name-servers xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=3]option routers xxx.xxx.xxx.xxx;[/INDENT]
[INDENT=3] [/INDENT]
[INDENT=2]filename “undionly.kxpe”;[/INDENT]
[INDENT=1]}[/INDENT]
[INDENT=2] [/INDENT]
[/quote]

if that is a direct copy, i see the issue

undionly.kxpe should be undionly.kpxe

[NickConrad]

[quote=“Junkhacker, post: 30464, member: 21583”]if that is a direct copy, i see the issue

undionly.kxpe should be undionly.kpxe[/quote]

not a direct copy, so just a dumb typo. Good catch, though, you made me double-take for a second between screens :eek:

[Wolfbane8653]

Any chance we can get a direct copy? PM it to Tom or something.

[NickConrad]

DHCP Server Configuration file.

see /usr/share/doc/dhcp*/dhcpd.conf.sample

This file was created by FOG

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.6.116.243;
filename “undionly.kpxe”;

subnet 10.6.116.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.6.116.10 10.6.116.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 10.6.116.246;
option routers 10.6.116.246;
filename “undionly.kpxe”;
}

[NickConrad]

Just to see what would happen, I made a symlink like Tom had suggested, but I made it to pxelinux.0.old. No change when booting a client over PXE

[Tom Elliott]

Do you have another DHCP server on your network, or is FOG the only one?

[NickConrad]

[quote=“Tom Elliott, post: 30474, member: 7271”]Do you have another DHCP server on your network, or is FOG the only one?[/quote]

I have my DHCP service running on Active Directory as well, though it doesn’t have a scope for the IP that my fog server is on

[NickConrad]

so with TFTP off, the message I get at PXE boot is the expected TFTP . . . . . until it finally times out. This is making me think the issue is specific to TFTP. I went and checked my username / password, and for some reason the web interface was dropping part of the password for the user I provided. I changed the user to something that has the same access but a plain text password. The web interface likes that just fine, but I get the same

TFTP.
Exiting

Screen when booting over PXE. Are there other usual suspects in the TFTP settings I should be cluing in on?

[Oscar Hilliker]

I have problems with fog 1.1.1 working correctly if the GUID of the computer is not displayed. Fog 1.1.1 is ok if the GUID is displayed, however if it sees FFFFFF …etc it says not for us.