[ericand]

During the Beta process, we had this problem on occasion and we think the problem is with your network, filtering out packets when the cRIO changes its IP address.

That the cRIO is changing IP addresses is an indication that you are partially connected and then the connection is dropped. I presume that you are team 537 based on the IP address that the cRIO is switching to.

When I saw this problem during the beta program, we determined that the router configuration was blocking the cRIO at the point where the cRIO reformatted and reset its IP address. For us this happened when we had the cRIO hard wired into the Linksys Router. We could work around the issue by having the cRIO use the wireless link. We also could work around the issue by having our laptop at the fixed 10.0.0.6 address and use a cross over cable to talk to the cRIO directly.

I don't think aborting the imaging process is the reason for your problem.

I'll check back later when I have a chance to review procedures with our Beta system vs. the documentation that has been sent out for the early adopters.