Forum Replies Created
-
Posts
-
I renamed the topic since it was unrelated to the actual problem. The new name describes the problem better.
Please people also provide the requested info so that we can chek if further investigation is required. This topic is hanging around since weeks. If this is not a NoMachine problem I think it’s time to close it.
Changed the icon’s color to black 😉 Thanks also for the many good suggestions. We are evaluating all of them.
Hello, thanks for working with us to understand the issue. There is a Trouble Report open which is public here:
https://www.nomachine.com/TR11K04067. Use this link to track its status. Thank you also for your availability to test 😉As Dan25 suggested we will check if there are problems with custom session. If we find anything wrong the client side (player), it’ll be fixed.
If there are problems with NX 3.5.0 server, they need to be dealt with by the support team for those customers still using 3.5.0. Any bugs will be investigated according to the terms and conditions of the support contract.
This forum is, as a rule, for problems related to NoMachine 4, but since this could well be a problem related to client 4, it would be useful to take a look at the session file (.nxs) and also the server logs 🙂 You can send logs to issues[at]nomachine.com. Put the topic name in the subject of your email.
Hi Isabel,
Can you tell us the exact message that you see?
Also, are you connecting from NoMachine 4 on Windows to Machine 4 on Windows?
Take a look at this article here: https://www.nomachine.com/AR11K00740
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.
Thank you. We have analyzed them and have identified where the problems lie. Developers have already started work on implementing a fix.
Hi Beduine,
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.
“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
https://www.nomachine.com/FR11K02793