problems pxe boot using existing network
-
I have previously tried to disable the IPv6 and still same thing… what is odd is that no problem when booting from confined network.
However these pesky HP 215 G1 are pain in the butt heheh
-
This system is trying to boot via NIC over UEFI/EFI boot. Can you change your bios settings to use “Legacy” or CSM (Compatibility Service Mode)? Rather than PXE Boot IPv4 NIC?
-
@Tom-Elliott said:
This system is trying to boot via NIC over UEFI/EFI boot. Can you change your bios settings to use “Legacy” or CSM (Compatibility Service Mode)? Rather than PXE Boot IPv4 NIC?
Thank you very much didnt think of that…
Flipped on legacy and at first didn’t work but found that HP set so that F12 is network boot shortcut however doesn’t work with legacy had to hit F9 and select IPV4 legacy in the boot list …
-
So you’re good to go now?
-
I believe so… Thank you for your assistance.
-
@Tom-Elliott said:
So you’re good to go now?
Off topic. has there been any updates on using fog with device that do not have Ethernet Ports ?
-
No.
While technically capable to do imaging over wireless, it’s not a method I want to directly support. If you feel you want to take on that challenge, please do.
Understand, it’s not a very simple thing to do, and nearly impossible to get correct across the board. I suppose in the “future” of fog it is something that we may need to look at, but for now I think it is just too much to try and take on.
-
@Tom-Elliott said:
No.
While technically capable to do imaging over wireless, it’s not a method I want to directly support. If you feel you want to take on that challenge, please do.
Understand, it’s not a very simple thing to do, and nearly impossible to get correct across the board. I suppose in the “future” of fog it is something that we may need to look at, but for now I think it is just too much to try and take on.
Understood, I know i looked into it before and complex it is.
Damn device developers, they just had to stop adding Ethernet ports lol.
-
See, I don’ t know why they decided to do that.
It was working fine with then, then blam, no more.
-
Of course, I’m one to talk.
-
Yea hehe. I know they waited to make deviced thinner but damn it they definitely didn’t think about he IT world in terms of deployment.
what they should have done is developed a new Ethernet port that is thinner and than all we would have needed is either an adapter or new connectors. -
Etherboot supports wifi network booting…
I’m looking into using that instead of the current FOG methods for booting.