kroy

[kroy]

We couldn’t reproduce such problem in our lab. It’s possible that is system configuration issue. Can you run debug, reproduce problem and send to forum[at]nomachine[dot]com? You can find instructions about collecting logs here: https://www.nomachine.com/DT04M00076.

[kroy]

The easiest way to create the desktop in your case is to create a new one with NoMachine option. After reboot just connect to the host with NoMachine. There should show: “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”, choose yes and it will create xfce session (make sure that DefaultDesktopCommand in /usr/NX/etc/node.cfg has value /usr/bin/startxfce4). Thats all.

Of course you can use mentioned by you commands (points 2, 3 and 4) to the system startup script, but remember that using an old cookie it is not recommended for host security.

[kroy]

Hi.

6. Something seems to show up…it’s some xfce default background and nothing else.

This is the default xfce session. You can change desktop command in NoMachine configuration. Find DefaultDesktopCommand in /usr/NX/etc/node.cfg and change value to /usr/bin/startxfce4. Line should look like this:

DefaultDesktopCommand “/usr/bin/startxfce4”

7. found https://www.nomachine.com/AR10K00710

Article was tested on CentOS 6 and it should work fine (maybe permissions nohup.out were denied for your user, thats why there was black screen). In Step 6 you should just change command to this:

DISPLAY=:0 nohup /usr/bin/startxfce4 &

[kroy]

I don’t know how to connect to my desktop without a password.

Connections to Windows account without password are not possible (https://www.nomachine.com/AR05L00802&an=).

Eventually I would like to use a password, but a password that is not related in any way to a login password for Windows.  How do I do that?

You can use NoMachine users database.

1. Edit as administrator the server configuration file (%PROGRAMFILES%/NoMachine/etc/server.cfg) and enable (uncomment and change value to 1) two keys:

Change:
#EnableUsetDB 0
…
EnablePasswordDB 0
to:
EnableUsetDB 1
…
EnablePasswordDB 1

And restart nxserver:
%PROGRAMFILES%/NoMachine/bin/nxserver.exe –restart

2. Add your user to NX database and set password for NoMachine log-in:

%PROGRAMFILES%/NoMachine/bin/nxserver.exe –useradd <username>

Now you can connect via NoMachine using your login and new password.

Also, if I wanted to use an authentication key, how would I set that up?  Is that an option for the free personal version?

Yes. Here you have instruction how to do it (https://www.nomachine.com/AR02L00785).

[kroy]

Can you look through this topic https://www.nomachine.com/forums/topic/error-138-cant-connect-to-office-computer-from-home and verify that you haven’t this same problem?

[kroy]

We need more information about your configuration. Have you tried to connect over local network? Please verify first it is not this same problem https://www.nomachine.com/forums/topic/error-138-cant-connect-to-office-computer-from-home

[kroy]

I wonder if this has anything to do with my home drive being encrypted?

It’s connected with your first problem – “Can you also tell me why I always have to ssh to the box and login first before I can even get NoMachine to authenticate?” It’s our bug. You can follow up that Trouble Report https://www.nomachine.com/TR02N06450 to know when it will be fixed. You could connect using SSH protocol, but that feature is disabled on the free version.

About problem with unplugged monitor:

Your Ubuntu is with Unity? Can you try other environment, for example xfce4? Can you tell us what graphic card you have? Logs would be really helpful to find problem.

[kroy]

Let us know whether you are getting the same issue on Arch. I must add that this behavior of having to ssh in beforehand is not normal with NoMachine, and since we can’t reproduce it (not so far anyway), we would ideally need the debug logs.

[kroy]

Sure. It’s in /usr/NX/etc/node.cfg file. Key EnableFileTransfer. You can also disable transfers in the GUI. Click on nxclient monitor in tray on server -> “Show the server status” -> “Server preferences” -> “Transfer” (fourth panel).

After making those changes you need to restart nxserver.

[kroy]

Can you also tell me why I always have to ssh to the box and login first before I can even get NoMachine to authenticate?

Our developers are investigating this problem.

Message “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?” shows when there is no started X server on the host. Are you sure that you can see the desktop if you plug-in the monitor after changing the GFX driver? If you can see the correct display on the screen, please run debug in NoMachine, reproduce problem and send logs from server and client side to forum[at]nomachine[dot]com? You can find instructions about collecting logs here: https://www.nomachine.com/DT04M00076.
Please also send .xsession-errors file, which you can find in the home directory.

[kroy]

NoMachine without connected sessions shouldn’t have any influence on the screensaver and power options. We couldn’t reproduce that problem in our lab. Are you sure there is no application that triggers any screensaver to start and the problem doesn’t exist when nxserver is disabled? Are you using xscreensaver as default screensaver on that machine? Can you write exactly what session configuration you have changed?

[kroy]

NoMachine free version supports only one remote connection to that server. To be able to connect multiple simultaneous remote connections to the same desktop, you need NoMachine Enterprise version – https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop

For more information about the free version, check here:
https://www.nomachine.com/AR10K00702
https://www.nomachine.com/AR10K00716

[kroy]

Your description indicates that you have double NAT networking. So NoMachine has to go through two routers. The first one which is facing the internet, and the second, which is on your local network (in your case RV042 with IP 192.168.2.*).

In that case you need to set up separate port forwarding rules on each device. If you’re not in charge of these routers, you would need tocontact who is in order to open the necessary ports to get access to your network from outside. The easiest option is to wait for NoMachine Network which will eliminate this problem altogether. This is in its final stages.

[kroy]

Nxnode is disabled for some reason. Could be a simple license or configuration problem.
Also, you should connect using NX, not SSH since connecting on port 22 is reserved for SSH which is not supported in the free version.

The best solution is to remove and reinstall NoMachine.

Execute sudo dpkg –purge nomachine && sudo rm -rf /usr/NX /etc/NX

and install again. Let us know if that helps.

[kroy]

Are you using non-native firewall? Please try turn off for test or just add port 4000 as an exception by hand.

Are you able to connect in reverse, from your Ubuntu host to your Windows PC? Maybe port on server is changed? You can check it in “Server status” on your Linux box.

See section 2 and fig. 1 in https://www.nomachine.com/DT11M00107#2 for more details.

[Author]

Posts