[Greg McKaskle]

What we occasionally see is that the laptop will tell the cRIO to reboot, and when the cRIO goes away, the laptop no longer has an enet link. No link leads to it self-assigning to 0.0.0.0. Then when the cRIO comes back, the laptop and cRIO won't communicate due to the IP conflict.

I don't really know why some laptops do this and most don't, but the solution/workaround is to connect both cRIO and laptop to a device that keeps its IP and keeps the laptop from self-assigning. The right tool for the job is the dlink or another router. Simply plug the laptop and cRIO into the dlink and go through the formatting. You may need to do the safe mode.

Greg McKaskle