Forum Replies Created
-
AuthorPosts
-
December 31, 2020 at 09:02 in reply to: NoMachine 7.0.209 on Windows10 – cannot connect to due to “Error is 108” #31041ercmapaParticipant
To clarify a bit – in all cases I used Latin-only for account names on system set up and then after first login linked those up to MS account. Maybe this information will help a bit. No non-Latin characters are used in account names. So it came as a surprise to see weird (=non-Latin) characters in log files.
December 30, 2020 at 08:52 in reply to: NoMachine 7.0.209 on Windows10 – cannot connect to due to “Error is 108” #31025ercmapaParticipantSorry, I probably don’t understand the question
NX runs as a service regardless of logged in user, i.e. I can [used to be able to] connect to machine that just started up and waits for username/password. Moreover, same behavior is witnessed on two machines – one is [let’s call it] shared desktop with multiple users, another one is configured with single user, but is also password protected.
December 24, 2020 at 13:18 in reply to: NoMachine 7.0.209 on Windows10 – cannot connect to due to “Error is 108” #30929ercmapaParticipantIt persists with 7.0.211
December 24, 2020 at 10:41 in reply to: NoMachine 7.0.209 on Windows10 – cannot connect to due to “Error is 108” #30915ercmapaParticipantThere are a lot (2295) of directories there majority of which (I assume) relate to particular sesssion, thus I copied most recent five of them and all dirs/files which seem to belong to NX itself.
I can see some strange account name in “session” files – such account definitely does not exist.
Attachments:
-
AuthorPosts