Strange...<div>I think that "Found iBFT NIC 0:" means that was NIC with #0 (first NIC).</div><div>More over, same strings I have in log of working image.</div><div>Please, compare the enclosed logs.</div><div><br>
</div><div>I think, that I need to do something with NIC configuration.</div><div><br></div><div><div>--<br>Yuriy<br>
<br><br><div class="gmail_quote">2010/6/29 Michael Brown <span dir="ltr"><<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Tuesday 29 Jun 2010 11:03:37 Yuriy Khokhlov wrote:<br>
> Found iBFT NIC 0:<br>
> Flags = 0x3, valid, boot selected<br>
> IP = <a href="http://192.168.21.231/24" target="_blank">192.168.21.231/24</a><br>
> Origin = 0<br>
> Gateway = 192.168.21.138<br>
> DNS = 192.168.21.138, 0.0.0.0<br>
> DHCP = 0.0.0.0<br>
> VLAN = 0000<br>
> MAC = 00:0c:29:09:46:b7<br>
> PCI = 02:00.0<br>
> Hostname =<br>
> Found iBFT target 0:<br>
<br>
No NIC is found within Windows matching the MAC address 00:0c:29:09:46:b7. Is<br>
this NIC driver present within Windows, and configured for boot-start? (The<br>
sanbootconf installer will configure the NIC for boot start, but if you have<br>
changed the NIC afterwards then you may need to re-run the installer.)<br>
<font color="#888888"><br>
Michael<br>
</font></blockquote></div><br></div></div>