I upgraded to 2.49, and have been running it for several days. The 6600m has the remote connected to an ip switch. The 6600m had been turned on and off with the ip switch successfully numerous times during the last 24 hours of use. I had used the desktop client, as well as the iPhone app with total success. I was, at some point after at least 24 hours intermittent use, unable to connect or switch off the rig with the remote ip switch. The remote ip switch was working perfectly, and the rig power light responded, but the screen remained on with the rig turned off by the ip switch. I was at home, so I walked to the 6600m and found the main screen displayed with the 'operate' button on the bottom of the screen. The 6600m was completely unresponsive. The desktop client could not connect (locally), the iPhone app could not connect, and pressing the operate button the the 6600m screen had no effect. I toggled the ip switch off. The lighted power button on the 6600m indicated that the remote switch had worked, but the screen on the 6600m remained. I tried the power button on the rig, but the screen still displayed on the 6600m, but was unresponsive. I tried the ip switch, it worked, but although the power button on the rig flashed and went through the sequence, the screen on the 6600m remained the same, and unresponsive. I was still unable to connect with either the desktop or the iphone app. I removed the power cord from the 6600m, and then reconnected it. The rig booted up and functioned normally. My concern is that the power had to be removed and replaced at the rig. This means that remote operation is not reliable with the remote connection if that won't get the 6600m out of this state. I would have to also, or alternatively, remove main power from the rig. Since I am fairly new to Flex, I would like to know if I could have made some error to get the rig in this state. As far as I know I operated the rig on the lan with both the desktop client, and the iPhone app, and had no issues. Has anyone else observed this? Could I have made an error to cause it? This would end remote operation if I was 1500 miles away. Any ideas?