Forum Replies Created
-
Posts
-
Could you try:
add “env -u WAYLAND_DISPLAY” to DefaultDesktopCommandDefaultDesktopCommand “env -u WAYLAND_DISPLAY /usr/bin/dbus-launch –sh-syntax –exit-with-session /usr/bin/startplasma-x11” ?
This should work for any installations running NoMachine virtual desktop sessions (e.g you have Workstation installed) and also the free version when NoMachine uses its own embedded X server. To be able to run a physical desktop session, a patch from us is required. We are preparing a package that will fix the issues reported here and will let you know when it’s ready.
Creating M-servername-xxxx directory won’t help in this case, this directory is dynamically by nxnode for each session. You should check if user Adm_XXX (I assume that you are trying create session for him) has correct access (permissions) to /usr1/, /usr1/people/ and /usr1/people/Adm_XXX
If you think that there everything is ok, but it still won’t work you can redirect place where that directory is created by editing node.cfg. Default path should be /usr/NX/etc/node.cfg on remote machine. There is key #UserNXDirectoryPath which points where directory should be created. You must uncomment it and provide path which exist and users have access. There is good example in key description in config file.
Did you check that full path to directory which returns error exists, got correct permissions and correct owner is set for directory and parents directory? Could you paste which directory cannot be created?
A Trouble Report has been created:
https://www.nomachine.com/TR12P09054You wrote “Maybe using ssh rather than nx protocol is the way to go. I’ll have a play …”: so ssh is working correctly?
We are sending you a test library by email, if you want to have a try.
Did you try with protocol SSH? In nxplayer window right click on connection – > edit connection -> protocol -> ssh.
As I understand Linux is radius client. What is radius server? Windows server with configured nps or maybe Azure cloud?
Are you connecting through protocol NX? If yes, then please enable nxserver logs, reproduce issue (try to connect), gather and send logs.
Here are the instructions for how to do this:
https://www.nomachine.com/DT10O00163#1Also try with protocol SSH (in nxplayer -> connection settings). Behaviour should be different.
If protocol SSH fails also, then could you paste here output of ‘ssh username@localhost’?It looks like problem similar to
https://www.nomachine.com/TR11P08977
Did you try with the latest release NoMachine 6.4.6?What is name of user currently logged to desktop on that windows? Does it contain any non-latin characters?
We are unable to reproduce this issue, can you help us in the meantime, by enabling logs and sending them to us?
Here are the instructions on how to do this:
https://www.nomachine.com/DT10O00163Logs from server and client of the affected Windows are requested. Please make nxserver –restart after setting SessionLevelLogs 7 in both server.cfg and node.cfg, reproduce issue and after that gather logs and send them to us.
Possibility of access login window (gdm owner) for all users is currently only enabled on NoMachine Enterprise Desktop. On other products (Terminal Server range, for example) you must for every user the trusted option or create an ‘nx group’ (not system) which will be trusted and then add users to that group.
For example, https://www.nomachine.com/DT07M00090#10.8.
It is hard to say based on the received logs. Can you enable logs in server.cfg and node.cfg by uncommenting and setting SessionLogLevel 7? Then restart nomachine with command nxserver –restart and reproduce problem.
Instructions on how to enable and gather logs are available here:
https://www.nomachine.com/DT10O00163Also client side logs could be really helpful at this point.
Zip them all up and submit to forum. If the logs are big, you can also send them to forum[at]nomachine[dot]com making sure to reference your topic.You should not use workaround from this TR, because it removes physical session from connection options.
27645 27677 11:37:09 255.702 TcpListener/Listener: WARNING! Refusing connection from ‘192.168.132.2’ port 39***.
Warning: Refusing connection from ‘192.168.132.2’ port 39***.Looks like there could be problem with loopback for localhost when you connect. Do you have any changes in network configuration?
Standard name for loopback in Linux is lo:
ip addr show dev loJust to be sure, what version of NoMachine do you have? I don’t recognize NoMachine Enterprise Workstation.
After disabling wayland did you reboot machine?
Is it on login window or some user is currently logged?To be sure can you paste output of command “ps -ef | grep X”?
Since release version 6.0 there are some changes on who can see physical desktop, now it depends on NoMachine product. More info is available here:
https://www.nomachine.com/FR11N03265
Which NoMachine product/version do you have?
On Enterprise Desktop or free, all users should see login window or their own desktop. I expect that root user to see the login window session.
On other versions they must be trusted users or administrators (‘system’ or ‘nomachine’).
You can add them to trusted users with command:
nxserver –useradd USERNAME –trustedAbout those warnings there is such problem described here:
https://www.nomachine.com/TR12O08309but problem should not affect conenction to session, only some mess in logs.
Can you please paste output of “ps -ef | grep X”?Is there any warning during nxserver –restart?
During connection there was question about creating new display because nomachine did not find any?
Or it just white window after connection without anything?If it is second option can you check client logs?
These logs are located on machine where nxplayer is used, in user home directory. For example you say, that tried connect from windows.
To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx
As an alternative, you may navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach this hidden folder.
Path can be similar to: C:/Users/nomachine/.nx