08-15-2017 11:47 AM
08-15-2017 11:47 AM
'We can't sign you in because the server couldn't be reached or the server version is incompatible with the device.'
This gives me very little information to look into. The logs are just as unhelpful.
The account is setup in Exchange and SfB with an appropriate license.
Get-CSMeetingRoom returns the account.
08-16-2017 03:54 AM
Take a look at this short step by step how to use snooper to read logs:
You will find snooper in the folder you install these tools to.
10-26-2017 06:43 AM
I am having the same problem and I am guessing it is also DNS. What records did you need to add/modify to get this working?
10-26-2017 07:10 AM
In the Office365 Admin Center, go to Setup | Domains and make sure all the DNS records are correct for your domain.
10-27-2017 03:25 AM
Faced with the same issue. Fixed after rebuild image of device.
02-16-2018 05:39 AM
I have the same issues on a SRSv2 running version 126.96.36.199.
The SRS user is enabled in O365 (SfB Online). O365 is federated (ADFS). I am wondering if that could be an issue or not?
The tenant was OAuth2ClientProfileEnabled for a while, but I have tried to revert that (Set-OrganizationConfig - OAuth2ClientProfileEnabled $false)
I notice that none of the users in this tenant are authenticated correctly using testconnectivity.microsoft.com. I receive the following message:
"Couldn't sign in. Error: Error Message: No common authentication method detected..
Error Type: AuthenticationException.
Error Code: 0.
Realm: SIP Communications Service.
Response Code: 401.
Response Text: Unauthorized."
The users in the Tenant are using Skype for Business client on a regular basis. I am not able to sign in to a normal SfB client with my SRS account. Should that be possible?
I guess I have a problem related to authentication - either because of Federation, or because of the ModernAuth changes mentioned, or because I can't run the "Set-Mailbox -RoomMailboxPassword"-command because of the federation situation.
Any responses are highly awaited!
11-01-2019 01:39 PM
The reason I was seeing this is because we force you to enroll in MFA for SSPR so it doesn't allow you to fully login until you have that configured so I had to login to a browser on my computer as the user and setup MFA questions for the acccount.