PXE-E32 error, unable to boot to fog from pxe

[Wayne Workman]

@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.

[K.Hays]

@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.

[Wayne Workman]

@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.

[george1421]

@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.ipxe and confirm that the chain at the end has the correct fog server IP address listed.

[Wayne Workman]

@george1421 It could even be requesting it from the wrong IP…

[george1421]

@Wayne-Workman Yes I agree a screen shot of the error would help. That way we can read between the pixels as it were.

[K.Hays]

@george1421

[Tom Elliott]

@K.Hays Have you tried updating to trunk?

[Tom Elliott]

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).

[Wayne Workman]

@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.

[george1421]

@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.

[Tom Elliott]

@george1421 No, because it’s 1.2.0

[george1421]

@Tom-Elliott said in [PXE-E32 error:

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).

Wow, how’d I miss asking that question. Well same on me.

https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

[K.Hays]

@Tom-Elliott i have not tried updating to trunk, is that necessary?

[Tom Elliott]

@K.Hays said in [PXE-E32 error:

@Tom-Elliott i have not tried updating to trunk, is that necessary?

It’s not necessary, but I think you’d benefit a great deal from it.

[K.Hays]

@george1421 the owner is fog.root but how do i check the access level?

[Wayne Workman]

@george1421 said in [PXE-E32 error:

@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.

Good catch, George. It is supposed to have an address before it.

[george1421]

@K.Hays said in [PXE-E32 error:

@george1421 the owner is fog.root but how do i check the access level?

ls -la will do that for you. it should be -rw-r--r-- 1 fog root

But as Tom said you would be better off upgrading to the trunk. Don’t let the not stable term scare you off.

[Tom Elliott]

@Wayne-Workman No it’s not, not if the user is using FOG 1.2.0.

[K.Hays]

@george1421 ill do whatever to fix the issue at hand. If you think updating it to trunk will do that, then so be it