Sanhook appears to block internet.

[Icky]

Hello,

I've followed the instructions for booting from WinPE as per the instructions at http://ipxe.org/howto/winpe using the ADK, and am able to boot into WinPE without any hassle.

Just to be clear, I'm running iPXE from within VirtualBox, which is configured as follows:

Quote:- 64-bit Processor
- Boot Order: Network.
- Sata Controller: 4 ports, 1 DVD port taken by my MSDN Windows 7 Installer.iso
-Network: Bridged Adapter

What I'm wanting to ultimately achieve is connect to my iSCSI target (created by WS2012), then boot into WinPE, connect to the windows share where my Windows installation is, and run setup.exe and then obviously install windows onto the iSCSI target.

As I say I'm able to boot into WinPE without any problems, and while booted into WinPE I can ping google.com and get replies, connect to the windows share and run setup.exe and start the Windows 7 setup, but obviously there is no iSCSI target that has been connected to, so no drives appear to install to.

I've used the iPXE builder at https://rom-o-matic.eu using the standard setting and the 'UNDI only' output format, along with the following embedded script:

Quote:#!ipxe
dhcp
chain http://192.168.0.2:8080/boot.iPXE

The 192.168.0.2 is my server, where I run the DHCP server and the web server. The 192.168.0.1 is the router (that is NOT running a DHCP server).

The boot.iPXE is the same as provided at the tutorial page:

Quote:#!ipxe
cpuid --ext 29 && set arch amd64 || set arch x86
kernel wimboot
initrd ${arch}/media/bootmgr bootmgr
initrd ${arch}/media/Boot/BCD BCD
initrd ${arch}/media/Boot/Fonts/segmono_boot.ttf segmono_boot.ttf
initrd ${arch}/media/Boot/Fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd ${arch}/media/Boot/Fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd ${arch}/media/Boot/Fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd ${arch}/media/Boot/boot.sdi boot.sdi
initrd ${arch}/media/sources/boot.wim boot.wim
boot

This gets me into WinPE no problem as I've already described. This is also where my problems start...

According to this page (http://ipxe.org/appnote/winpe_with_iscsi), WinPE already has the iSCSI initiator driver, just not the controller, and will connect to the iSCSI target if I specify one with sanhook. So, I change my boot.iPXE to the following:

Quote:#!ipxe
set initiator-iqn VirtualBoxiPXE
sanhook iscsi:192.168.0.2::::iqn.1991-05.com.microsoft:homeserver-windows7base-target
cpuid --ext 29 && set arch amd64 || set arch x86
kernel wimboot
initrd ${arch}/media/bootmgr bootmgr
initrd ${arch}/media/Boot/BCD BCD
initrd ${arch}/media/Boot/Fonts/segmono_boot.ttf segmono_boot.ttf
initrd ${arch}/media/Boot/Fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd ${arch}/media/Boot/Fonts/segoen_slboot.ttf segoen_slboot.ttf
initrd ${arch}/media/Boot/Fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd ${arch}/media/Boot/boot.sdi boot.sdi
initrd ${arch}/media/sources/boot.wim boot.wim
boot

And iPXE continues to boot into WinPE, however once in WinPE, things seem to change. I'm not able to ping google.com and instead the output below and consequently, I'm not able to connect to the share on the server, yet the output for ipconfig indicates that I do have a connection:



However, commenting out the line in boot.ipxe:

Quote:sanhook iscsi:192.168.0.2::::iqn.1991-05.com.microsoft:homeserver-windows7base-target

And power cycling the VM, and allow it to go through the same procedure, I have no problems, but as previously stated, no iSCSI drive to install to.

So, why would sanhook be causing this network issue, and how can I resolve it?