abigroot

If I were to purchase a Neeo remote is it a simple changeover from the SR260 or is there extensive programming needed. Better yet, can someone remotely configure this is I purchase a Neeo remote? It is not to extensive of a setup, basically one tv and a cable box hooked to the remote blasters.

Well, windows did have some updates and then I re-installed Composer. For a try, I installed Composer HE and Composer ME as well and they all seem to have the same issue. To me it seems like a network issue which is why I was looking for the ssl as a possibility

Virtual System opens up, but as soon as I try to connect to director, I get the same error. I included a pic of the screenshot. This is in the virtual system loaded up but no director.

Totally aware that the old composers will not work, I was just going with what was working previously. Even upgraded to 2.10, the 2.5.3 would log-in. Couldn't do anything with it, but that was one of the few I could remember that would allow any sort of access. Tried the Broker as well, no dice. Thanks, keep the ideas coming please.

I tried to disable and re-enable the director and that didn't seem to help, still having the error. I can see the director when "picking" which to connect to and everything on the system as a whole works, that means that the touchscreens are seeing the director. In that vein, I'm fairly certain the director is working as required. Looking further into things, none of the previous versions of composer PRO work where they did before (with errors, of course) and the media and home editions of composer do not connect either. I can connect via systems manager, direct IP login, remotely (for control) via android phones and using when/then. just not through composer. The date is correct, which I see has been an issue from time to time for some. The only thing I cannot see is the SSL and whether or not it is on or off. This was all working before we did the update to 3.0. That means that the composer pro 3.0 was working. Thats the only way to do the update. It was after the reboot of the director that I couldn't connect which is driving me towards something of a network problem. The error that pops up is so non descript; "Unable to connect" - "Could Not Connect To Director at 192.168.1.XXX" (XXX for my privacy). The only thing that gives me someinformation is when I try to logon via composer pro 2.5.3 and it says "ERROR" - "Could Not Connect To Director on the Non-Secure Port"

Yes, it is the same. Just upgraded and after the upgrade it will not connect.

Upgraded to 3.0. I was able to use composer pro prior to the upgrade. After the upgrade I cannot connect. The director shows up as a possible selection, I click it and it shows up right away saying it cannot connect. Not sure if this is a network problem or a Control4 problem. Previously there was an issue with the SSL not being selected. I cannot see that as an option when I connect through the system manager (oh yeah, connects just fine through the system manager) Anyone experience this before? Shed some light?