will overrule filename or opt67 if client arch matches one of the below
Sanboot -no-describe -drive 0x80 || goto failedĮcho You cancelled the menu, dropping you to a shell # UTILITY ITEMS #Įcho Type exit to get the back to the menu
Menu.ipxe is a menu that allows selection of multiple operating systems / boot files once loaded in - I'll quote part of it but it is pretty long:Ĭonsole -picture $ I'm using undionly.kpxe simply because it is what the AIO Boot tutorial said to use (I am a noob at this stuff) TPS Version: 1.0.0.21 - I didn't realize I had an older version and am updating now (this is why I am confused - as it seems its trying to pull the menu from 192.168.1.1 instead of 192.168.1.35) Hi thanks for the reply! Here is the info you requested: It seems like it is trying to connect to the IP address of my router which leased the IP instead of the Tiny PXE Server. I have attached the server Log and a picture of a client computer trying to connect. However when I run with ProxyDHCP enabled - it stops working all together.
When I run Tiny PXE Server with ProxyDhcp OFF - I get about a 50% success rate - I assume this is my router's DHCP server and Tiny PXE's DHCP server racing and whoever leases the IP first is what the PXE client tried to connect to to download the Menu etc. I have had some success so far but have run into issues. I've recently been trying to set up Tiny PXE Server to boot Active Kill Disk over the network to many machines for easy drive formatting.
0 kommentar(er)
