SOLVED PXE-E32 error, unable to boot to fog from pxe
-
@george1421 No, because it’s 1.2.0
-
@Wayne-Workman Isn’t there suppose to be text to the left of /default.ipxe? I just tried on my system and its too fast for me to catch.
-
@K.Hays Internal addressing is not available to the outside world and doesn’t harm anything to share. However I’d recommend not sharing external addressing.
-
First, all, this is 1.2.0 (Sorry it wasn’t asked before. And glancing over the posts, it wasn’t mentioned at all either).
-
@K.Hays Have you tried updating to trunk?
-
-
@Wayne-Workman Yes I agree a screen shot of the error would help. That way we can read between the pixels as it were.
-
@george1421 It could even be requesting it from the wrong IP…
-
@K.Hays Can you confirm that you have a default.ipxe in the /tftpboot directory on the server. I do have to admit this is the first time I’ve seen a permision denied message here.
The owner of this file should be fog.root with the access level of 644
And then finally
cat default.ipxeand confirm that the chain at the end has the correct fog server IP address listed. -
@K.Hays Well that’s a different error and maybe a different problem - but it could be due to many things.
Firstly, I’d verify that the file exists inside of /tftpboot. If it’s there, I’d then check it’s permissions. If permissions are good, I’d then open the file and make sure the IP address at the bottom is good.
However, a photo of the error would help a lot, it would contain a lot of information that would help us help you.
-
@Wayne-Workman Is this going to help with the new problem? the permission denied problem? I’m doing that now but I got past the PXE-E32 error now.
-
@K.Hays Can you just boot a destkop on that subnet to windows please, disable the network connection, start a Wireshark capture for that network connection, and then enable the network connection. Let Wireshark run for 15 or so seconds and then stop it, and upload that file? It will contain the DHCP information we are looking for - and this is the fastest way to get it in your situation.
-
@george1421 “/default.ipxe… Permission denied (http://ipxe.org/0212603c)”
That is the error I’m getting now when i try to pxe boot. It does in fact connect though to the fog server. -
@george1421 All of these settings and configs are correct.
-
@K.Hays said in [PXE-E32 error:
So what we figured was we had to change all of our current ip pools to all point to the fog ip. Some were pulling the old fog server ip. I am now able to boot with pxe, but i get permission denied shortly after. Im still happy though, this is one step closer than i was a bit ago!
OK, we need to verify since you had a fog setup at one time. Lets make sure that you have undionly.kpxe listed for option 67 and not pelinux.0 or something else from the older deployment. I would also ensure (at least intially) that you the target computer and the fog server are in the same subnet. That will eliminate any cross subnet confusion.
-
This post is deleted! -
So what we figured was we had to change all of our current ip pools to all point to the fog ip. Some were pulling the old fog server ip. I am now able to boot with pxe, but i get permission denied shortly after. Im still happy though, this is one step closer than i was a bit ago!
-
@Sebastian-Roth I’m not so sure, Discovery, Offer, Request, and Acknowledge. The server does the offer, then the client takes that info and requests it from the DHCP server officially, then the DHCP server acknowledges it… This is how it works from all the captures I’ve seen…
EDIT - my bad, you are correct. I just double checked on a system here. But I still think it’d be more beneficial to just do a full capture with no filters.
-
@Wayne-Workman Sure because this is the request sent by the client! It does not show the answers as those are requests from other PCs and the DHCP server seams to answer unicast instead of broadcast.
-
@K.Hays I took a peek at the pcap file.
There are no next-server or filename or 066 or 067 options being given.
