@eliaspereira This should be fully fixed in the stable release of 1.5.10.x coming on the 15th of this month and in the dev-branch as of now.
I thought it was already fixed back in September, and it has been working in 1.6 since then but we just got a report of a related issue here https://forums.fogproject.org/topic/18081 which I believe I just fixed.

@george1421 said in Host status is unknow 2:

@eliaspereira So does it work now that you fixed name resolution on the FOG server?

At first, yes.

Thanks again for the great help!!!

@eliaspereira said in wake on lan not working:

fogserver is in a different vlan from the vlans

This is going to be your first problem. The wol magic packet is not a proper IP packet so it typically can’t traverse a router. There is a way to send WOL packet but you need to send as a directed broadcasts. On most routers this “feature” is disabled because it could be used to abuse your networks.

Are you using (or wanting to use) WOL to wake up computers for imaging or just to wake up computers at a specific time?

Understand this subnet issue is a limitation of the WOL protocol and not FOG.

@george1421 said to @eliaspereira in Error on Start from hard disk (HD):

I see you change the exit mode to Grub. That will work too, but I’m surprised that grub works when SANBOOT didn’t

I find this a bit strange too but well you never know. Hardware can be a real pain and is doing weird things across the board. So I guess there is some hardware out that not able to chainload the OS via EXIT or SANBOOT but is happy with the GRUB method…

@eliaspereira Dell uefi firmware and iPXE, not specifically FOG.

The x010 series was the first to support uefi network booting (kind of). They got it right with the x020 series.

@wayne-workman

That’s exactly what I did. I wrote a shell script and put it in rc.local. It checks through the mac if the computer is in the fogserver database and from there it makes the change of hostname and join in our domain.

Thanks to all for your help!!!