%1 was unable to resolve the DNS hostname of the login server %2. Resolution: If you are using manual configuration for Communicator, please check that the server name is typed correctly and in full. If you are using automatic configuration, the network administrator will need to double-check the DNS A record configuration for %2 because it could not be resolved.
was unable to authenticate to the server %2 due to following error: 3. Resolution: Please check that the password is correct ...
was unable to join the server %2 due to the client version not being compatible with the server. Resolution: Please switch ...
was unable to locate the login server. No DNS SRV records exist for domain %2, so %1 was unable to login. Resolution: Please ...
was unable to locate the login server. The DNS SRV record that exist for domain %2 point to an invalid server %3 which is ...
was unable to resolve the DNS hostname of the login server %2. Resolution: If you are using manual configuration for Communicator, ...
We can't connect to the server for screen presenting. Please try again in a bit. If this issue continues, contact your support ...
We can't connect to the server. Please check your sign-in info and make sure you're using the (!IDS_PRODUCTNAME_SHORT) account ...
We can't connect you to the meeting because your sign-in info isn't updated. Please sign out and back in to (!IDS_PRODUCTNAME_SHORT). ...
We can't join you to the meeting because your user account isn't recognized by the meeting server. For more info, please ...