|
Re: crio II imaging issue
Good news: I've managed to successfully image our cRIO. I'm posting this in case others have the same issue in the future.
I installed Wireshark and started monitoring the traffic going between the two devices and noticed some odd behavior going on. There was lots and lots and lots of ARPing and browser election stuff going on when it normally wouldn't be. I then isolated the machine that was talking to the cRIO by connecting it directly to the cRIO instead of leaving it attached to the LAN. I wanted to make sure and isolate it from traffic on the domain. Once this was done, I saw FTP sessions that hadn't ever previously initiated and the process was rolling along.
Anyway, here is the bottom line of what worked. Other configurations might work too, but this is something you might try if you're having trouble:
- Use a physical machine. Using a VM is not sufficient.
- Leave your LAN. Connect the cRIO directly to the machine you're imaging from via a patch cable. Do not connect to a switched network with other devices.
- Do not use wireless.
- You do not necessarily need to leave your domain, but you do need to be isolated from it.
- Remove all other IP addresses from your computer's NIC except for the 10.x.x.5 address you plan to use. Do not just bind to this address in addition to your normal addresses.
- Remove all DNS, WINS, etc server references from your NIC.
- Power cycle the cRIO controller and wait about 30 seconds.
- Try imaging now.
Last edited by Particle : 15-01-2013 at 22:00.
|