Jenni Armstrong's community posts

Same question. I don't see where we're supposed to find this new exe.

'tis a minor issue of little import. :)

You guys have a pretty good product. It's weird, but it works and is innovative in it's handling of things like multiple monitors. I'm very happy with it as an alternative to others!

Thanks for working on this issue. We've been able to work around things, but it'd be nice to not have to use single-password for so many users.

Also, your authentication tabs are all mislabled "authorization", which is the wrong word.

Authorization means you allowed to do something. Authentication is proving you're the/an authorized person.

And end users waste a lot of time telling me "i don't have 'authentication' in properties" and it's pissin' me off :)

Interestingly, the computer that connects with windows security is using a ms online account running windows on MacBootCamp on a Macbook. The one that fails is a regular windows machine & an ms online account.

I have a user with two windows machines, both using the same online account to login. One of them works normally, as expected with windows security, the other exhibits the behavior being discussed in this thread.

Try again, folks, Microsoft account isn't the problem.

We are not using RUServer. These are simple win10 machines. Out of 13 identically configured workstations, 5 end users had to be set to single password auth. With ALL of those cases, my workstations at home get the windows auth window.

With all of these users, the Viewer would attempt to connect, and on the 2nd or 3rd attempt, the user/pass/domain dialog appears and then disappears. After 5 failed attempts the viewer fails and reports access denied, bad credentials.

This occurs when auth is set to "auto" or "windows security".

Initially it appeared these were win10home users, but i've seen at least two using win10pro. Most likely these users have not updated their home machines, because that's how people are, but i don't know that for a fact.

I'm sorry i don't have any further details to assist.

I'm not finding a Usoris folder in HKLM/software on any client machines. And this isn't related to the host at ALL.

The host works fine from my computers, but not from others. This is a CLIENT problem. The CLIENT is passing bad credentials to the host.

Also, 1 that was passing bad (blank?) credentials was win10pro

i will try, but these are users remoting in, i've only helped them via slack, and i don't have access to those workstations. So far about 1/2 of our staff has had this happen. I tried on hosts running both 6.10.9 and 6.10.10, but the result was the same, even after upgrading the older host.

can confirm this happens on all versions of windows 10 home, not on professional