Tue Nov 11, 2014 4:13 am
sorry for so many updates, but I'm just posting info as I troubleshoot.
I can recreate this every time, and now have a sure fire way to get the wan back. I have to go into the adapter tcp/ip v4 settings, and change the subnet mask from 255.255.255.0 to 255.255.0.0, then back again...which seems like the only non-disruptive change I can make, while being enough of a change to force the nic to start acting right again.
downloaded latest intel driver for my i350 nics, software installed, driver kicked in, checked intel proset driver settings, everything looked good.
ran test again, clicking refresh in the ms iscsi initiator, bam, loss of wan, but nic still up.
change nic ipv4 mask, and goes right back up....so strange.
I would love to show this to bohdan, or someone, logged into my workstation, watching me recreate this, I'm scratching my head!