[Kevin Sevcik]

I'm kinda voting the packet sniffer method as well. As Radical Pi stated, the FMS never talks directly to the cRIO, only the DS. There's firewalling and etc. happening through all the field networking equipment, however. That seems like the only place likely to cause this problem. If Kettering and Waterford used the same field and networking hardware, that'd certainly be suspicious. There might be something on the network with a stray setting that targeted your particular cRIO. I know you can't test things anymore, but I'm curious of you did any/all of the following in all the testing:
Pinged the cRIO from the DS
Pinged the Bridge from the DS
Port scanned the cRIO from the DS
Monitored packets from the DS to the cRIO
Tried your cRIO with a different robot or team number
Tried your cRIO with a different Bridge

Basically, it seems likely to be a networking hardware issue somewhere, as opposed to something physically wrong with the cRIO. What would be extra interesting is if you could get your cRIO to the Michigan Championship, along with someone(s) clever enough to check the network traffic etc. Then there might be a chance of pinning the problem down for good and all.