This problem used to occur for users behind strict firewalls that were blocking the traffic needed to access the remote tool sessions. We’ve redesigned our software to use standard web ports for all traffic, and we deployed the solution in Sept 2011, so nobody should see this error ever again.