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"