I have a pxe boot WinPE using iPXE, iPXE config file as follow:

sanhook iscsi:
cpuid --ext 29 && set arch amd64 || set arch x86
initrd      bootmgr
initrd          BCD
initrd     boot.sdi
initrd    boot.wim

After I successfully boot into PE, I found that I can't connect to my iSCSI target, can't even ping the IP. Then I found the strange routing table, below:

IPv4 Route Table
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
     30         On-link    286         On-link    286         On-link    286    286         On-link    306         On-link    306         On-link    306         On-link    306         On-link    286         On-link    306         On-link    286

Please note the line with, how does it go into routing table? I didn't set it in my dhcp server. I tried to delete it using:

route delete
route delete mask

but both failed, saying can't find the item.

Any idea?

  • Your sanhook statement will attach the SAN as a BIOS drive. How are you trying to "connect to your iSCSI target"? It would probably be easiest to drop that statement and attach the iSCSI target with the iscsicpl command in WinPE. Here's a good article about adding MS's iSCSI Software Initiator to WinPE. Also, what are you trying to accomplish? There may be a much easier way. – Chris S Mar 21 '13 at 15:08
  • OK, yes you are right. The sanhook statement is probably not needed if I have iscsi buit-in PE image. What I'm trying to accomplish is to install Windows to iSCSI target. And I've already added iSCSI initiator to my PE. Thanks for the reminder. – Andy Song Mar 23 '13 at 1:58
0 is your is your http server is the IP assigned to the client by the DHCP is the default gateway provided by the DHCP

I think you just have no network because of a driver problem

From WinPE get a console session (SHIFT+F10) and list with Notepad.exe the content of the file:

Notepad.exe x:\Windows\inf\setupapi.app.log

locate the section that identifies the Plug and Play ID (PnPID) of the network adapter and see if that driver is loaded ok.

Please consider even if there are no errors in the file it could still be a driver problem...

  • Before I try your suggestion. I did have network because I can ping the gateway. – Andy Song Mar 22 '13 at 10:53
  • Just checked the log, there is no network error. BTW, how can you tell which is my DHCP server? – Andy Song Mar 22 '13 at 11:04
  • you said you couldn't ping... I haven said the DHCP IP; I've mentioned the client IP assigned by the DHCP server and the default gateway also provided with the DHCP answer. If you can ping then forget about a faulty driver. – Pat Mar 22 '13 at 14:39
  • Sorry for my confusing description. I said I couldn't ping iSCSI target. Forgot to mention that I could ping gateway(also the DHCP server) which is different from the tftp/http/iscsi machine. – Andy Song Mar 23 '13 at 1:54
  • if you can ping the gateway/dhcp server and cannot ping the iSCCI server being on the same net then forget about a routing table problem or a net driver issue. – Pat Mar 23 '13 at 12:15

To answer my own question. Refer to the bottom of this page. Still need to find out how to clear the gateway via the iPXE script.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.