Forum Replies Created
-
Posts
-
The new free NoMachine can be used as a client to get access to your NoMachine NX server. You can just disable server access if you wish to use it as a client software only (see the tutorial here to do that: https://www.nomachine.com/how-to-disable-access-to-the-local-desktop).
Version 3 is a 10+ year-old product and old products are replaced everyday. For every old product replaced there are those that had learned to live with it and want to “hang on to it”. So I am interested in knowing if there is anything special that makes you prefer client 3. I think most of the problems are due to communication problems. These communication problems are somehow normal when you have to deal with a large user base and with a completely new market space at the same time (Windows and Mac users). For example, people that used client 3 are confused by the fact the new free version is also a server. These people may have overlooked the fact they can install the free Enterprise client. This is a standalone client as it was the old client 3.
Hello, did you see the link “What to include” when submitting? It’s just below the box you use to submit a comment.
You’ve missed out some very important information:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).
– If on Linux, desktop version (GNOME. KDE, whatever) on client and on server.Once we have this information, someone might be able to help 🙂
No available sessions on this server
You should take a look at the forum topic here: https://www.nomachine.com/forums/forums/topic/how-to-enable-local-display#post-251
It deals with the same message that Simeonof is getting.Paai, you should try the latest version (366) making sure you’ve followed the advice in the other topic I just linked. If you are having problems with the installation still, feel free to open a new topic.
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.