Repeating "waiting for cRIO to reboot"

[usacat6]

NetBeans console message “waiting for cRIO to reboot” repeats every few milliseconds even when the robot is functioning.
Java NetbeansIDE 7.1
Java program “SampleProject” from the “Getting started with java for FRC Control System_2 “ document.
cRIO firmware update with the latest code, checked and updated again
Execute the Java run to down load program, ftp completes, “waiting for cRIO to reboot” appears on console
Drive station communication and robot code status indicators go off
Drive station and communication indicators come back on
“waiting for cRIO to reboot” message continues to repeat on the NetBeans console
Robot drives when enabled, code seems to perform as designed.
“waiting for cRIO to reboot” message continues to repeat on the NetBeans console.
Does anyone know why the console keeps getting the “waiting for cRIO to reboot” message? Java code or some other problem?

[Patrickwhite]

When we had this problem in the past, the problem was that the subnet mask on the development computer was not the same as the robot - 255.0.0.0.

[usacat6]

Checked the subnet mask this morning. Set to 255.0.0.0.
Updated Java this morning, prolem with repeating waiting for cRIO still exists.

[Robby Unruh]

Checked the subnet mask this morning. Set to 255.0.0.0.
Updated Java this morning, prolem with repeating waiting for cRIO still exists.

We found that just resetting the robot per normal did the trick. Have you tried this?

Otherwise, my team had this problem a few days ago and for the life of me, I can't remember how we fixed it. If you still don't have this solved when (or if) I remember, I'll definitely let you know.

[usacat6]

Checked all the subnet masks on all the network components. According to the "Getting started with the 2012 Control System_2" the subnet mask on the cRIO is 255.255.255.0. We changed all our network devices to have this subnet mask. Rebooted all devices. The repeating "waiting for cRIO to reboot" still persists.

[Lalaland1125]

Make sure to use static ip's and set your computer to either 10.xx.xx.5 if you are the classmate or 10.xx.xx.6 if you are other.

We have this problem every time we switch to the DCHP on our router( so we can access the internet).

[usacat6]

Last night we implemented the smartdashboard. We are able to send data from the cRIO to the smartdashboard with no issues. We are using the Java command-based robot project with NetBeans 7.1 The “waiting for cRIO to reboot” message persists on the programming computer console.
By the way the programming team is very excited about the command-based robot project. They recognized the benefits of this platform very quickly.

[Bryscus]

You can always try re-imaging the cRIO if the problem persists.

- Bryce

[usacat6]

We found the problem. The computers we are using for programming are loaners from a company sponsor. They still have the companies virus protection software loaded. We installed the wireshark network packet analyzer and discovered the cRio trying to communicate using port 6666. The McAfee virus software blocks port 6666. We disabled the On-access scan function and the communication issue was resolved.