Multiconsole with EOS/ION 2.0

I have an RVI and Ion purchased in 2008. Since software version....1.9-ish (I think) we have been able to remote power on our Ion console from the RVI.  This is wonderful because the console is in a location that is hard to access while the RVI is easily accessible.  We recently upgraded to 2.0 and I am having trouble with the Ion launching from the "multiconsole power on" command from the RVI. The Ion will power on but then a "multiconsole error" box pops upon the Ion stating networking services are not available. This prevents the console from opening into Ion (primary) and requires an individual to go to the console and click on the box to "start anyway." Once that step is complete it launches and synchronizes with the RVI just fine.  Is there a network setting that I may be able to check/uncheck to bypass the "multiconsole error" and have the console start anyway automatically? Any insight is appreciated. Thanks.



[edited by: Chiaroscuro at 7:07 PM (GMT -6) on Tue, Apr 9 2013]
Parents
  • The error message on the Ion means that the application is attempting to launch before necessary background network services are running that would allow it to work as a multiconsole device.  Once the services started, I would have expected that error message to go away.  There is nothing that you are doing wrong or different, it is the simply a behavior of the console.  I will take a look at it.

  • I've had similar issues with an RVI that is powered on via the network, however it just logs in without being able to connect (and doesn't give any indication that it actually connected as an offline client). In order to fix it I have to exit the application, and then log in again & it is able to connect. This has been persistent thru the last several builds of the beta prior to 2.0 being released.


    [edited by: jrgoss at 12:22 PM (GMT -6) on Wed, Apr 10 2013]
Reply
  • I've had similar issues with an RVI that is powered on via the network, however it just logs in without being able to connect (and doesn't give any indication that it actually connected as an offline client). In order to fix it I have to exit the application, and then log in again & it is able to connect. This has been persistent thru the last several builds of the beta prior to 2.0 being released.


    [edited by: jrgoss at 12:22 PM (GMT -6) on Wed, Apr 10 2013]
Children
No Data
Related