walttheboss

[walttheboss]

I suggest you get a ZeroTier account.  That will give you a WAN accessible psuedo IP address that NoMachine can use to get directly to your PC.  Be careful with this though as it can expose any connected computer once someone gains access because all of your computers anywhere in the world can work as one LAN.

Walt

 

[walttheboss]

Can you clarify which version of NoMachine you are running?

What operating system are you running from, Linux, Windows, Mac?

What is the operating system of the remote host you are connecting to?

Is the timeout on the remote host or the local NoMachine application?

[walttheboss]

OK after invoking the gods of admitting to losing your keys and then they immediately appear, I have the solution.

1. Dial and then put the ssh into the background. That allows you to enter commands on the current machine
2. Sleep for a bit to let the ssh connection work.
3. Open the NoMachine session.

ssh -fN -L 4102:localhost:4000 user@remotehost  && /bin/sleep 5s &&  /usr/bin/xdg-open /home/acer/Documents/NoMachine/Exodus_ZT.nxs

I would mark this as solved but do not know how.

Walt

 

[walttheboss]

Thank you so much.  That is brilliant.  I linked that script to a keyboard shortcut so I can tap it anytime I am running NoMachine.

Works Perfectly.

Thanks again.

Walt

 

[walttheboss]

Definitely don’t update till the point release of 20.04 comes out.  That is usually August.  When you see 20.04.1 then upgrade. Till then you have to force the upgrade and it may break.

During the upgrade my experience says that NoMachine will be fine.

[walttheboss]

I have been using NM for a long time.  Free Connection using SSH tunnel.  The speed of the connection and responsiveness vary a great deal.

I recommend using the ssh tunnel to establish a connection.  Then connect NoMachine. If you want help with that see the instructions or PM me or just reply here.

[walttheboss]

One more change.  Make sure that you also check your node.cfg .  It could be that the Physical Display variable is now set to a virtual and not actual display.  When you start the machine and the NoMachine icon does not appear in the System Tray then node.cfg has been messed up.

/usr/NX/etc/node.cfg

Look around line 825.

Make sure that the line either refers to your actual physical display or is commented out(Default).

To know what display is the real one that normal users use you need to be on that computer.  Open a terminal and type $DISPLAY

It will return something like :0 or :1

If you then want to specify this then do so in node.cfg.

[walttheboss]

Thanks @graywolf for the comment.  Good to know that command. Restarting the nx server however did not solve the problem.

I went into the two config files /usr/NX/etc/node.cfg and server.cfg.

server.cfg had added two lines because of the one time that I connected with the monitor off.

Lines 920 to 950.  Maybe slightly off depending on your version.  Only a few lines shown. I commented out the bold lines below and all is working well.  When I connect to that computer it gives me the actual display. For some reason once this is set there is no GUI way to reverse it.  You need to go in and change the config files back.

# 1: Enabled. NoMachine will create automatically the new display at
#    server startup. This setting has to be used in conjunction with
#    ‘DisplayOwner’ and ‘DisplayGeometry’.
#
# 0: Disabled. NoMachine will prompt the user for creating the new
#    display. This is the default.
#
#CreateDisplay 0
#
#
#DisplayOwner “”
DisplayOwner claw
#
# When ‘CreateDisplay’ is enabled, specify the resolution of the new
CreateDisplay 1
# desktop in the WxH format. Default is 800×600.
#
#DisplayGeometry 800×600
DisplayGeometry 800×600

Attachments:

1. 

   Selection_003.png
   

1. badlineinserver.cfg_.txt

[walttheboss]

Will check this AM.  I have restarted, rebooted, reinstalled many times.  Do you know of anywhere in KDE where the virtual display config is saved?

[Author]

Posts