kroy

[kroy]

We weren’t able to reproduce this problem (even on Fedora 28). How did you check the external IP? Using the NoMachine Player “Welcome screen” or by using !M icon in the system tray? Maybe you have many interfaces on the list – external IP is on the bottom – is it possible that you didn’t scroll the list and missed it?

Please check sudo /usr/NX/bin/nxserver --upnpstatus command. It should list external IP and Port (when UPnP is enabled). If it still missing – please send logs with debug from both machines. Instructions about debug and collecting logs you can find here:
https://www.nomachine.com/DT10O00163.

After running debug – please restart nxserver (navigate to bin directory, which in default is /usr/NX/bin/ on Linux and %PROGRAMFILES(X86)%\NoMachine\bin on Windows, and execute ./nxserver --restart). Then execute command ./nxserver --upnpmap. Compressed logs from /usr/NX/var/log and %PROGRAMDATA%\NoMachine\var\log please send to forum[at]nomachine[dot]com.

[kroy]

Hi

Thanks for logs, but unfortunately we need need a new set of client and server logs which match.

Can you check if SessionLogClean is still set on 0 on the server side?

Then, on client machine: please open the NoMachine Player -> navigate to the Settings -> Privacy -> and check “Don’t delete log files on exit” -> Done.

You can also remove any old nxtrace.log.

After that reproduce the problem and send: from the client side: compressed .nx/R-* directories and %PROGRAMDATA%/NoMachine/var/log/nxtrace.log; and from server side: compressed /usr/NX/var/log folder and .xsession-errors which should be in the home directory.

[kroy]

Are you sure that no one was connected at the moment when you see the blank screen? Blanking the screen will not turn off when somebody is connected to the desktop.

If it’s not the case we need to check logs. On the server machine open Command Line as the administrator. Navigate to etc directory and edit node.cfg file (cd %PROGRAMFILES(X86)%\NoMachine\etc\ and notepad.exe node.cfg). Find SessionLogClean key uncomment and set value to 0 (change#SessionLogClean 1 line to SessionLogClean 0).

Reproduce the problem and zip %PROGRAMDATA%\NoMachine\var\log directory from server side. Send the compressed file to forum[at]nomachine[dot]com.

Please write here also what is the machine model of the server host.

[kroy]

After unplugging the display, the system may use only one resolution. Can you make sure if in the system settings there are any other resolutions available?

Can you also send NoMachine logs from /usr/NX/var/log/node directory from server side? Please edit /usr/NXetc/node.cfg and uncomment and change key: SessionLogClean 0, then restart nxserver (sudo /usr/NX/bin/nxserver --restart) and reproduce problem. Send also .xsession-errors file from home directory. All files please send to forum[at]nomachine[dot]com.

As a workaround you can run a virtual desktop session if you have a Terminal Server version installed. If you have the free NoMachine version you can try to run in headless mode. When the local X server cannot be found, NoMachine is able to use its own display service (that is an embedded X server) to let users connect seamlessly to a physical desktop running in the background on the remote machine.

[kroy]

Very strange. Are you connecting from a connection visible in your recent connections panel? Do you get the same behaviour if you click New and start a new connection?

You could check in the logs of your Windows PC to see if there are any error messages. A sudden termination of the NoMachine programs would generate nxtrace.log, which are placed in the %PROGRAMDATA%/NoMachine/var/log/ folder. NoMachine Player logs you can find in home directory – inside .nx/R-* folder. Look for the errors in session text file.

If you send us the compressed both directories with logs, we can check for you. Send it to forum[at]nomachine[dot]com

[kroy]

Are they excerpts from the logs shown during connection via NoMachine Player to localhost? Can you try to connect to 127.0.0.1? Is connection via SSH to localhost possible there?

[kroy]

Hi.

Our tests show that NoMachine installs fine, and we checked again just to make sure.

Did you happen to see any Warnings or Errors during installation? Any errors during installation would appear in the /usr/NX/var/log/nxinstall.log (nxupdate.log if that was update).

If you send us the logs, we can check for you. Send it to forum[at]nomachine[dot]com, attach there also output following commands:

cat /etc/xdg/menus/applications-merged/NoMachine-dir.menu
cat /usr/share/applications/NoMachine-base-unity.desktop
cat /usr/share/applications/NoMachine-status-unity.desktop
ls -l /usr/share/applications/NoMachine*

[kroy]

Login as root is disabled in the system by the default. For security reasons we do not recommend to enable it. But if you are aware of the dangers and you are sure that you want to enable root login, you should edit /etc/gdm3/custom.conf by adding the line AllowRoot=true below [security] section. Save the file and exit.

Then edit /etc/pam.d/gdm-password and comment the line (add # sign at the beginning of the line) auth required pam_succeed_if.so user != root quiet_success.

Reboot your system after making the changes.

[kroy]

To connect you need to use your remote system account’s username and password (the topic has already been discussed on this forum here: https://forums.nomachine.com/topic/how-to-configue-usernamepassword-authentication).

I tried to tell NoMachine to reset the recorded password. But that still won’t have it ask.

To achieve this – open NoMachine Player, edit the connection file for the Windows computer and check the box “Reset saved preferences and password”. Does that help?

However, “connection refused” shouldn’t be shown as a result of entering the wrong password. Are you sure that the nxserver is running on the server side (the computer you want to access)? Did you do a restart after installation?

After installing you can check the status of the server by clicking on the NoMachine icon in the tray and choosing “Show the service status” (in your case, on the Windows 8 host).

[kroy]

We haven’t problems with sessions on upgraded Fedora 28. Is there any core dump, produced by any program (even by a NX program, although this would be rather bad 😉 ) in Fedora’s home directory, when session fails? That would be useful.

Please enable debug on server side, restart nxserver (sudo /usr/NX/bin/nxserver --restart) and reproduce problem. Compressed nxserver logs (/usr/NX/var/log/ directory) and .xsession-errors file from home directory send to forum[at]nomachine[dot]com.

Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT10O00163

[kroy]

By the default NoMachine use port 4000 (more about NoMachine’s default ports you can find there: https://www.nomachine.com/AR01L00770) and it should be used as “LAN Port” in your case.

But to avoid possible problems with port forwarding manual configuration we suggest to restore all your previous changes and enable UPnP on the router and on nxserver. To do that last – edit server configuration file (/usr/NX/etc/server.cfg) and change EnableUPnP none to EnableUPnP NX (uncomment if it’s commented out). Save the file and restart nxserver (sudo /usr/NX/bin/nxserver --restart). More details about enabling UPnP you can find there: https://www.nomachine.com/AR11L00827.

Then start again ‘Server Status’ window again to check External IP and Port (that information should show also in the output of the command: sudo /usr/NX/bin/nxserver --upnpstatus).

[kroy]

Thanks for the tip.

Budgie, though currently unsupported. Is similar desktop environment to GNOME and even use their technologies, so removing GNOME after Budgie installation is not recommended.

And as a rule changing AvailableSessionTypes is not necessary. Adding a Budgie path to DefaultDesktopCommand should be enough. We checked it just to make sure and we can definitely confirm this.

There’s another article which goes into more detail about non-default virtual desktop environments, it’s linked in the article you based your research on: https://www.nomachine.com/AR04K00667.

It gives you a load of tips on how to find out what GUIs are installed and what commands to use.

[kroy]

It looks like you have double NAT in place. Is your router connected to the modem or router from your provider? If yes, NoMachine has to go through two devices. That is, a router facing the internet for which you have a private LAN with IP address of 222.222.222.222) and then another router for access to the private network/LAN for which you have an IP address of 111.111.111.111).

UPnP doesn’t easily support this type of scenario. If you have access to both routers, port forwarding should be set up on both (https://portforward.com/help/doublerouterportforwarding.htm).

With the release of NoMachine Network this won’t be necessary. You can read more about this upcoming functionality here: https://www.nomachine.com/FR07J02731.

[kroy]

Are you sure that the nxserver was restarted?

After executing the restart command sudo /etc/NX/nxserver --restart if you connect to the host it should show the message: “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”. When you click on “Yes” it should create a new display.

Have you made all the steps and then it shows the black screen? If yes, it could be because of a wrong DefaultDesktopCommand value. What is your output of the command grep DefaultDesktopCommand /usr/NX/etc/node.cfg? If you installed KDE Plasma you should have: DefaultDesktopCommand “/usr/bin/startkde”. You can change it by editing the key value in the /usr/NX/etc/node.cfg file.

You can find here more info about connecting to headless systems: https://www.nomachine.com/AR06N00891.

[kroy]

We were able to reproduce the problem. The issue will be fixed as soon as possible.

Please follow this trouble report: https://www.nomachine.com/TR08P08785 and use the notify me tool to know when a fix is available.

• This reply was modified 6 years, 4 months ago by Bilbotine.
• This reply was modified 6 years, 4 months ago by Bilbotine.

[Author]

Posts