Register the Client with the FOG Server Errors

[naysweb]

Version 1.2.0 download today.

[Tom Elliott]

Well, based on the kernel your screen is showing, you haven’t updated your: next-server/filename information to point at the undionly.kpxe file have you?

[naysweb]

@Tom-Elliott Based on the fact, that confuses me slightly I’m going to say no

Sorry.

[Tom Elliott]

Your DHCP server should be setup, right now, to be looking at pxelinux.0, if this was an upgrade from 0.32.

On linux, the file to edit would normally be:

/etc/dhcpcd.conf

However, I’m going to guess you’re in a Windows environment so you’re likely using a Windows Server to provide DHCP for your systems.

On Windows DHCP you need to edit the DHCP Scope options 66 and 67. 66 will the be IP address of your fog server, 67 will be the filename you’re trying to load. In your case you want to load undionly.kpxe.

[naysweb]

@Tom-Elliott ahhh I understand now, Yeah all of that is correct on our Windows DHCP.

[Tom Elliott]

@naysweb What do you mean?

[naysweb]

@Tom-Elliott It was complete new install today, and our DHCP was setup to point to the FOG server and undionly.kpxe. But getting the screen shot error when add the client to fog.

[Tom Elliott]

Then that is not a “fresh” install, or somebody did not update your particular scope to look at your new FOG Server.

[naysweb]

@Tom-Elliott Ok, back to confused… So should it not be undionly.kpxe???

We had Fog before but never got round to using it. So i wiped the server and the settings in DHCP and setup backup from latest installer from the website today.

[Tom Elliott]

Undionly.kpxe is correct, but 1.2.0 did NOT install a 3.8.8 core kernel, only 0.32 installed it.

This tells me the old fog server you had likely has a tftpboot directory structure of:

/tftpboot/fog/kernel/bzImage
/tftpboot/pxelinux.0
/tftpboot/pxelinux.cfg/default

And so forth.

Which server is this coming from? I haven’t a clue. Either somebody else still has a running copy of 0.32, or it’s tftpboot contents, and the PXE Boot options on your particular subnet are being directed to look at it.

[naysweb]

@Tom-Elliott Thanks you, I have just installed the latest Kernel and it now works. Not quite sure what was happening but thank you for your support.