You are not logged in.
This may be because it's still beta (or preview as MS call it).
In these strange times, remote access to work is a necessity. After days of trying and fiddling, I finally managed to connect to the work VPN (this was the hardest part), and then to the RDP desktop trying to translate Windows/Mac instructions to xfreerdp.
Final step (since there's a chance of us being thrown into lockdown again) is MS Teams. I have the client installed, but the login fails every time. No errors other than "We can't log you in". This happens whether I'm on my own connection, or the VPN.
I already know precious little about Teams, but it works fine on my phone (via my data connection, not connected to work). Is there an issue with the Linux client, or something I should be doing differently (other than my login and password)?
Last edited by Roken (2020-09-19 10:34:06)
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline
I try to avoid the TEAMS application as much as possible, in both Linux and windows, therefore I cannot really comment on the app.
However, I can tell you that the web version works quite OK in Linux, if running in the Chromium browser. When I tried in Firefox, I could not have any voice call within the platform - not sure why there should be such a browser-specific dependency in 2020?
Regarding the access, I think there was some big hiccup couple of days back and the whole thing only worked partially. I would suggest to give the web version a shot. Chats, meetings, calendar, voice work, and it is easier to close down
Offline
Nope. I get the same error using the web client.
Unfortunately, I have no option but to use teams (work standard), and worst case is I use it on my phone, which works just fine, but it'd be nice to get it working.
Googling some more, this doesn't appear to be just a Linux issue, so I guess I'll have to wait for MS to write good, working software. It may take a while.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline
I am also forced to use that platform, sadly. But if the problem happens with the web version as well, I am out of ideas - except for the usual cleanup on browser side, try it out starting without profile/safe mode, etc.
One thing that could alleviate the situation would be to bring the mobile's screen to your Linux - e.g., with scrcpy.
Offline
As a quick update, on a completely different matter, I noticed that my system clock was 1 hour fast. After some fiddling, it is now the correct time on each boot, and Teams is working just fine. To fix I
Enabled ntpd service
ran
sudo ntpd -qg
And all is good.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline
Glad that it worked. I recall now seeing something similar when dualbooting with w10. The VPN client for windows (Cisco) would not connect until the clock was updated via NTP. With this in mind, I am surprised that your VPN worked at all (if the clock problem was already present). On the Linux side, I am satisfied with the minimalistic Systemd-timesyncd and only resort to the "-qg" when starting up a virtual machine from an old saved state.
Offline
Edit: Whoops, wrong thread
Last edited by paragordius (2020-09-23 17:41:03)
Offline
and only resort to the "-qg" when starting up a virtual machine from an old saved state.
Well, it has persisted now across multiple reboots, so it looks like a one-shot fix here.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline