Windows Boot Trouble with Multiple NICs

--===============3556541726808108980==
Content-Type: multipart/alternative; boundary=002354530ec4c0aa1004a547e9a3

--002354530ec4c0aa1004a547e9a3
Content-Type: text/plain; charset=ISO-8859-1

Hello all,

I've been doing some work to separate my LAN and iSCSI network
infrastructure and have run into an issue.

My PC is booting from an Etherboot USB thumb drive and has 2 NICs.  The
onboard Atheros NIC (Net0) is used for LAN traffic and is on the subnet
192.168.10.0/24.  The add-on Intel NIC (Net1) is used for iSCSI traffic and
is on the subnet 192.168.12.0/24.  Both subnets offer DHCP.

My problem is this, if Net0 is plugged in during boot (and thus receives an
IP address via DHCP during gPXE initialization) my Windows boot will hang at
the Windows start-up screen and eventually the PC with restart.  If,
however, Net0 is unplugged during boot everything proceeds as expected.
 Once the computer has finished booting I can reattach the Net0 cable and it
happily grabs and IP and everything works.

Does anyone have an idea as to why having Net0 plugged in during boot would
be breaking my Windows boot?

--002354530ec4c0aa1004a547e9a3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<span style=3D"border-collapse:collapse;font-family:arial, sans-serif;font-=
size:13px">Hello all,<div><br></div><div>I&#39;ve been doing some work to s=
eparate my LAN and iSCSI network infrastructure and have run into an issue.=
</div>


<div><br></div><div>My PC is booting from an Etherboot USB thumb drive and =
has 2 NICs. =A0The onboard Atheros NIC (Net0) is used for LAN traffic and i=
s on the subnet=A0<a href=3D"http://192.168.10.0/24" style=3D"color:rgb(0, =
0, 204)" target=3D"_blank">192.168.10.0/24</a>. =A0The add-on Intel NIC (Ne=
t1) is used for iSCSI traffic and is on the subnet=A0<a href=3D"http://192.=
168.12.0/24" style=3D"color:rgb(0, 0, 204)" target=3D"_blank">192.168.12.0/=
24</a>. =A0Both subnets offer DHCP.</div>


<div><br></div><div>My problem is this, if Net0 is plugged in during boot (=
and thus receives an IP address via DHCP during gPXE initialization) my Win=
dows boot will hang at the Windows start-up screen and eventually the PC wi=
th restart. =A0If, however, Net0 is unplugged during boot everything procee=
ds as expected. =A0Once the computer has finished booting I can reattach th=
e Net0 cable and it happily grabs and IP and everything works.</div>


<div><br></div><div>Does anyone have an idea as to why having Net0 plugged =
in during boot would be breaking my Windows boot?</div></span>

--002354530ec4c0aa1004a547e9a3--


--===============3556541726808108980==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
--===============3556541726808108980==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Etherboot-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss

--===============3556541726808108980==--