Forum Replies Created
-
AuthorPosts
-
snejokParticipant
Is the owner of the virtual desktop the same user who then connect to such virtual desktop?
Yes, exactly!
Thank you!
December 26, 2013 at 21:02 in reply to: RSA key-based login to NX server (original thread closed…) #1444snejokParticipantHello, heywood!
I found open FR that describe your question:
https://www.nomachine.com/FR10K02791
Your original post: https://www.nomachine.com/forums/forums/topic/rsa-key-based-login-to-nx-server
snejokParticipantHello, all!
Dear sil04, could you tell us some advice to debug this “problem with authenticating” in 4.0?
I heard on this forum about “debug version of nx”, that distributed by request. Could you tell us why you are not distribute it “by default”?
snejokParticipantOk, thank you for your answer!
Dear NoMachine, what you think about the same behavior as ssh do:
ssh -o “StrictHostKeyChecking no” <ip>
Because I see for example this situation:
I use Nomachine Enterprise as Load Balancer, 15 Terminal Nodes, and 500-1000-10000 terminal clients. In one day I decide to increase Nodes count, so all 500-1000-10000 terminal clients will see the Warning about the keys. This terminal clients is a “readonly thin clients (kiosk mode)” with firmware made by me, so I could switch some option nxplayer.cfg to disable this warning, for example. In another way I will FLASH ALL this thin clients again to add Keys in the firmware.
I know that I can “replace keys on the server side”, but it is “not secure” too 😉 😉
snejokParticipantAs I understood the behavior of nxplayer this happens when “NX Monitor” can’t find system tray.
But, as I see, there is no system tray in your configuration 🙂
snejokParticipantThank you!
Oh, very usable feature!
snejokParticipantThank you for you reply!
Yes, Ctrl-Alt-Shift-F synchronize window state with the button.In NX Client 3.5 everything works fine.
snejokParticipantubuntu.package.list.txt.zip
Attachments:
snejokParticipantHello!
I updated to newest version 4.0.368 and tried to reproduce the problem by setting DisplayLimit to “1” in server.cfg and expect that nxplayer show me the error about “not reached for the user” or something else, when I try to connect two users simultaneously.
But two users successfully connected to the server simultaneously.
Logs and configs attached.
When I set only ConnectionsLimit to “1” and tried to connect simultaneously, all works as expected:
nxplayer show me:
The session negotiation failed.
Error: Reached the maximum number of concurrent sessions on this server
So, I think that my first problem is fixed and maybe I found second problem. (or maybe I don’t understand DisplayLimit behavior)
Attachments:
snejokParticipantThanks for the reply!
Please, don’t close this topic until I test 4.0.367 😉
-
AuthorPosts