Forum Replies Created
Of course would be interresting to fix this.
How do i create this .nxs-file? I did not find one in my old and the new user (which works with NX) …
Ok – thats the point – Yes, of course there is a reason why i use another user: my standard-account was used for tests with many different NX-versions, especially with some 4betas. Since this time there something wrong with my account – connecting to it i can enter the (right) password, but a connect did not work (error with ssh-authentication and sometimes with the host 127.0.0.1). I have removed ~/.nx, /usr/bin/NX and so on – but no success.
After a long search i found creating an additional account, it works without problems – just connection to this account and then using the screen of my standard user … so i decided not go deeper in the problem with my account…
So – then the “problem” is solved – its only a problem of my local account but not of NX … so thank you for the help!
Yes, NX does (normally) ask. However, to work from remote i have configured the NX-Server that it dont ask for permission. Because if it asks, and i sit remote, a cannot click on the button “ok” 😉
It would be very helpfull to have a list, e.g. in the NX-Database, where permitted users to connect can be stored. The idea is, in this case there are many system users (UsersX), which can connect to a machine (e.g. via active directory). However, there is only one “owner” of the machine (User1), which normally sits in front of the screen (session :0) and in this case he is the only one who should be able to connect via NX to that session. For that i need a kind of a white-list to allow only User1 to connect.