Forum Replies Created
November 19, 2013 at 18:56 in reply to: nxclient unable to find session on headless X server #811
You need to add the ‘screen’ parameter to the execution of X server, for example:
‘-screen 0 1024x768x24’.
The screen size ‘1024×768’ can be set as you like but it’s important to set 24 bit depth as ‘x24’.
Additionally X server and GNOME should be started from one console.November 19, 2013 at 13:19 in reply to: Can't connect to my PC, multiple errors in logs on server #809
Thank you. We have analyzed them and have identified where the problems lie. Developers have already started work on implementing a fix.
It’s a bug, so thanks for reporting it to us. You can track its status using this link:
I’m having the same problem on Fedora 19, local accounts only, no NIS. Sometimes I can log in, sometimes I can’t. Really intermittent.
Also, when I do manage to connect, it keeps asking me every time what I want to do about the audio device, pass through or not.
VirtualNobody, this seems to be a different problem. I’ve opened a new topic: https://www.nomachine.com/forums/forums/topic/intermittent-login-on-fedora-19
I used NX 3.5 with linux machines a few years ago. It was wonderful. Remote sessions were opened only with user credentials and without being presented at local display, I also authenticated with my own ssh key.
It’s still like that and even better, given that from the 3.5 to the 4 there have been 6 years of development. But let me summarize: you make a lot of noise for basically nothing and in the end your problem is that now you have to pay a moderate amount for the privilege of running such a (in your words) wonderful terminal server. And of course you want it exactly the same on Mac. And presumably for free. OK, we’ve got the point. Now we’ll get back to work. Thanks for your insightful comments.November 15, 2013 at 18:33 in reply to: Can't connect to my PC, multiple errors in logs on server #760
We have not received the logs. Can you send them to the email address we provided making sure you put ‘Can’t connect to my PC, multiple errors in logs on server’ in the subject of your email?
- This reply was modified 6 years, 11 months ago by Britgirl.
“Make a grab pointer option” has just been added to the roadmap 🙂
Adding the ‘Grab the mouse input’ option to the NoMachine menu panel inside the session
we’ve inserted a new Feature Request into the development roadmap which you can track using the following link:
Starting the session by passing options to the client from command line
A very basic rule of security is that people contact the software vendors before posting in a public forum, so that others can’t exploit the security fault until the fault is fixed by the vendor.
Regardless this problem is a security fault or not, we hope in the future all posters play nice and follow the rules.
Hi mt, can you post a new topic if you are having problems with resuming sessions on your 3.5.0 server? This way we don’t embed too many issues into one topic.
Hello Michal, please check this article: https://www.nomachine.com/AR11K00740
You can try putting the following in the .profile of the user, to force the setting, or find a way to let Yast automatically apply your setting when you login.
setxkbmap -rules evdev -layout fr
Note that this appears to be a Yast bug. I don’t see any reason why it should “forget” about your setting once you have set the keyboard in Yast,
I should note that NIS (aka yp) is in play
Yes, indeed the auth method used can be a useful detail when having to investigate a login failure.
Our test team is re-checking NIS auth and will let you know.