Found some cRIO-9068s that are acting like the primary NIC and secondary NIC are mutually exclusive. I cannot get them to simultaneously respond to pings.
New rack - power on.
Use NI MAX to find it via Link local address.
Set Primary:
192.168.3.13
255.255.128.0
Set Secondary
192.168.4.100
255.255.128.0
Save.
Change Laptop to primary sub net (.3.). Reconnect. See that the secondary is still only set to link local. Re-set per above, save.
Laptop #1 on primary (via one dumb switch) it's set for static on .3.
Laptop #2 on secondary directly connected it's set for static on .4.
Both have WiFi disabled, proxy off, Windows foirewall off, symantic disabled etc.. to cut down on the cinfusion.
Laptop #1: Refresh Chrome and cRIO web page says secondary nic is indeed 4.100.
Laptop #2: Cannot ping it (secondary NIC).
Laptop #1: I change the primary NIC from 3.13 to 3.53 (any change will do) Save.
BAM! Laptop #2 can now ping 4.100. But wait, now Laptop #1 can't Ping 3.53. So.....
On Laptop #2: I change the secondary NIC from 4.100 to 4.99
BAM! Laptop #1 can now ping 3.53. and...as you may have guessed Laptop #2 can't ping 4.99.
I created a ticket with NI: But thought I would ask here just in case, possibly, someone else has seen this.
I have seen this on two racks. The first had a full application on it, and in the course of troubleshootin I wiped the disk and re-deployed software via MAX. The second rack I didn't even go so far as deploying SW via MAX - it was left in safe mode, and it also did it. I did however flash the firmware of both to 1.1.0f0.