Thanks, Polina, for the follow up, but we had already reinstalled the offending host in single-password only mode, and rolled out the same MSI to some 15 other hosts. So too late to harvest the registry keys.
We'll stick with single pwd for now as it seems to be working reliably, can't really afford to sink more time into it at present.
Hi I had tried that. But to be sure, I've tried again: From the Host / "User and Access Control" I've explicitly added my user name with full permissions (as well as the group I'm a member of). Trying to connect still fails in the same manner.
I had already tried both Auto and CSS as the auth method for the connection in the viewer - both give the same result.
Screen shots from the host below (with a little obfuscation). However as I can log into the server and load up the list of users / groups, doesn't this prove conclusively that the server address configured in the host is correct. The server is deliberately running on non-standard port 5654.
I've upgraded the server to 188.8.131.52 and tried with the original viewer and host - same result. I've run the portable viewer beta version - still same result. As the host concerned is remote and belongs to a client, I don't feel able to "risk" running the beta host, even as the standalone host. I might end up losing access to the machine altogether and I cannot access it physically to resolve if that occurs.
It sounds like the fix was in the server and should hopefully have resolved my CSS auth problem even with older host / view although I note the preference to run consistent versions end-to-end.
I think for the time being we'll need to stick with single password auth and use the server mainly for internet ID - it does seem much faster than using the public/default servers. Single pwd seems reliable compared with CSS.
We'll keep testing on this basis - unless you have any further suggestions.
I'm having a problem very similar to that described here.
However I already have the latest server 184.108.40.206. Viewer 220.127.116.11 and host 18.104.22.168.
Host has auth modes single password and CSS enabled. I can connect using single pwd, but when trying to connect using CSS I get "Custom Server Security Authorization Error".
Host logs sometimes show error 35 127.0.0.1 Password is incorrect or error occurs. Whether this actually appears in the host log seems inconsistent.
I can connect to the RU server from the host settings "Users and access control" button - it connects and all the users and groups are visible. I've tried assigning permission to my user directly and via group membership.
I can connect from the same viewer to other hosts on my LAN using CSS. The host that doesn't work is remote and I'm connecting over the internet using the RU server as the internet ID relay server as well as the auth server.
I've tested network connectivity from the host to the RU server using powershell test-networkconnection and verified the IP and port being used are working.