Forum Replies Created
-
Posts
-
First check your firewall settings and allow connections via NX to port 4000. We would also need the server-side logs. Please check the instructions here: https://www.nomachine.com/DT07M00098. The logs you sent in earlier were of the client side.
The logs were perhaps too big and so didn’t attach. Can you submit them directly to forum[at]nomachine[dot]com? Thanks!
It seems that Kroy replied to you as you yourself were following up and he forgot to mention that the logs you sent were only player logs from a session which wasn’t started (maybe you attached the wrong set, I dont’ know), so weren’t very helpful. So yes, we did see your topic, the day it came in, and it was placed in the queue, but unfortunately the lack of information slowed down any potential investigation.
Please understand that the forums are handled by the developers as quickly as possible – in the time they have between handling support tickets coming from subscribed customers and their own development work.
You can send your logs to forum[at]nomachine[dot]com and we’ll take a look.
– What OS and version is the remote system?
– What product do you have installed?
– Are you connecting to the physical display of the server or are you running virtual sessions?
– And if you are running virtual sessions, is ‘Use X11 vector graphics mode’ checked? (it is by default)
– What desktop environment is in use in the remote session (either in the physical display or in the virtual session)?
– What graphics card and driver is installed on the remote system?
@Ve0 what do you mean? Fra already provided some suggestions in his reply, see above 😉
Ashok Barik, you should have received an email from us with further details about the best way to get support for your environment, please check your email inbox for emails from forum[at]nomachine[dot]com. Thank you.
Something obviously went wrong when you first installed – possibly old lic files interfering from an earlier version.
SSH is meant to work out of the box, so when the user selects in SSH in the connection set-up, the rest is done for them.
The free product does not support SSH protocol. Features available in the free version are highlighted here: https://www.nomachine.com/nomachine-features.
But you should be seeing a message like this when you try to connect to the Pi “Running NoMachine sessions over a SSH is not supported” or similar, not an Error 138.
To understand better why you’re not seeing the message logs would be useful. You can follow the instructions here (https://www.nomachine.com/DT07M00098) and send them to forum[at]nomachine[dot]com.
forum[at]nomachine[dot]com
This is the email address. Replace the [at] with the usual email address symbol and a ‘.’ before the ‘com’. Anyway, we’ll take a look at what you sent. Thanks.
Accessing multiple user accounts running on the same host is available on Linux, and not on Mac or Windows. This functionality is called Terminal Services, you provide a virtual desktop for each user and they work separately, even at the same time.
When you access the physical desktop of NoMachine (which is what you do with the free NoMachine for Linux/Win/Mac), the users will see the same physical desktop. NoMachine can’t currently make any Windows or Mac computer become a Terminal Server.
Glad to know you sorted the problem out. I added your follow-up to your original post.
On systems which NoMachine supports, with default system settings, commands in keys should work fine without editing. But If you have installed a desktop environment manually it might be necessary to change values in those keys.
This article deals with that 🙂
How to run a virtual desktop environment on Linux different from the default one with NoMachine
https://www.nomachine.com/AR04K00667