Oh, I think I got it now. Since I noticed the problem the worst during installation, I will see if I can manage to roll it into my WinPE images so that when the WinPE image boots, it should fire up the sanbootconf. I'll give this a shot and see if I can do away with that routers option line in my dhcpd.conf. Thanks for pointing this out to me!
OK, glad to know I'm in the right place. -Steve On Thu, Jan 3, 2013 at 10:23 AM, Michael Brown <[email protected]> wrote: > On Thursday 03 Jan 2013 15:15:53 Steve Cross wrote: >> I didn't realize that this routing issue had already been worked >> around in iPXE. Is this something that I have to specifically enable >> somewhere or is it supposed to happen automagically? > > It's not iPXE that does it; there's no way for iPXE to construct an iBFT that > won't trigger the erroneous behaviour in Windows. > > sanbootconf is the iSCSI boot configuration driver for Windows 2000/XP/2003. > It should also work on later versions of Windows, though it isn't necessary > since the equivalent functionality is included in Windows by default. > However, if you do install sanbootconf then it should work around the routing > issue. > >> On a side note, I just realized that this is the devel mailing list >> and I am only a user. Please let me know if I need to unsubscribe and >> leave everyone alone since I am not actively developing iPXE - I would >> hate to be intruding where I should not be. > > No, this is the right place! > > Michael _______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
