[Elfonzo]

Greg, thank you for the quick response.

We were able to image the cRIO from the 2gopc netbook. So far out of our three computers, that was the only one that would properly image the cRIO. We are completely baffled by this and don't know why none of the other computers can image the cRIO. That being said, after we imaged the cRIO, we haven't been able to load code. Our first thought is to try loading code with the netbook that we were able to image the cRIO with, but the netbook does not have LabVIEW on it and we aren't confident on the netbook's ability to run labVIEW.

So when we plug the computer in directly to the robot, the computer recognizes that there is something plugged in, the driver station sees that there is a robot, but we do not get robot communications (the light is red).

In the diagnostics section of the driver station, this is the error message we are getting:
"Warning<Code> 44002 occured at Ping Results: link-GOOD, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-GOOD, FMS-bad Driver Station
<time>10/1/2013 4:04:51 PM <unique#>32
FRC: Driver Station ping status has changed."

When we open labVIEW, the IP address is set at 10.9.31.2 (and is displayed next to the "RT CompactRIO Target).

When we try to connect to the robot via labview, we receive the error "Unable to resolve from current dialog" and "Failed to connect to Real-Time target.

As background, we changed around our IPv4 IP Address to 10.09.31.5 and disabled wireless connections. We have also completed the Bridge Configuration Utility.