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.
0 Like 0 Dislike
Megan Campbell @ on
I have the same problem did you ever figure it out?
Reply Report abuse
Please login to answer the question.
0 Like 0 Dislike
Michael McLennan @ on
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.
Cancel Report abuse
Please login to answer the question.