ISCSI boot with Intel NICs added to windows 2008 r2 routing table causes non iscsi traffic to attempt default routes on iscsi networks

Question

I have a server with Intel 82576 Gigabit Dual Port Nics.  I have configured them to use iSCSI boot the primary looks to 10.0.0.1/24 and the secondary looks to 10.0.1.1/24.  The target is configured correctly.  Everything boots as expected.
 I have added the MPIO feature and configured MPIO for the iscsi initiator as per: http://blogs.technet.com/b/migreene/archive/2009/08/29/3277914.aspx.
 My issue is that the iSCSI networks show up in the routing table like so:
I did not configure a default route in the Intel setup utility:
I tried to explicitly remove the 0.0.0.0 entry and leave blank, with no change.  As you can see with the above routing table traffic attempts to travel over these routes:
C:\Users\Administrator>ping google.com
Pinging google.com [209.85.145.99] with 32 bytes of data:
Reply from 10.0.0.201: Destination host unreachable.
Reply from 10.0.1.201: Destination host unreachable.
Reply from 209.85.145.99: bytes=32 time=23ms TTL=51
Reply from 209.85.145.99: bytes=32 time=22ms TTL=51
Ping statistics for 209.85.145.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
A ping to the outside world first attempts on 10.0.0.x/24 network, then on 10.0.1.x/24 network and then finally on the network the traffic should go over.  I don't want my iSCSI traffic to ever show up with a default route.  How do I get rid of it?
route delete 0.0.0.0 mask 0.0.0.0 "on-link" results in: The route deletion failed: The parameter is incorrect.
route delete 0.0.0.0 mask 0.0.0.0 on-link results in: The route deletion failed: The parameter is incorrect.
route delete 0.0.0.0 deletes all default routes, then I have to add back in the "valid default route" of 192.168.100.6.
I would like to not have to do a route delete though.

Answer 1

So I've sort of given up on fixing the gateway assignment in the route for iSCSI boot.  I configured a DHCP server to give out the information required by iSCSI boot and configured the network cards to use DHCP for their configuration.  I insured
that my DHCP server gave out no default gateway entry.  However, I still got the undesired routes in the routing table.  This makes me assume that there isn't a "fix" for it, only the workaround.
Here is the script I run on each iSCSI Boot initiator (you would obviously change the ip number to suit your environment):
@Echo off
Rem fixes iscsi route problem as shown below:
Rem IPv4 Route Table
REM ===========================================================================
REM Active Routes:
REM Network Destination Netmask Gateway Interface Metric
REM 0.0.0.0 0.0.0.0 On-link 10.0.0.200 10255
REM 0.0.0.0 0.0.0.0 On-link 10.0.1.200 266
REM 0.0.0.0 0.0.0.0 192.168.100.6 192.168.100.98 266
REM The top 2 lines are on the iscsi interface and traffic tries to go out it
REM We need to delete the routes, so we'll just delete all gateway routes and
REM add back in the one we care about.
route delete 0.0.0.0 >c:\iscsibootroutefix.log
route -p add 0.0.0.0 mask 0.0.0.0 192.168.100.6 >>c:\iscsibootroutefix.log
After running it I get:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.100.6 192.168.100.98 11
10.0.0.0 255.255.255.0 On-link 10.0.0.200 10255
10.0.0.1 255.255.255.255 On-link 10.0.0.200 10255
10.0.0.200 255.255.255.255 On-link 10.0.0.200 10255
Then I added a task in “task scheduler” of "administrative tools"  that ran as the user “system” “when the computer starts” that runs this script.