kroy

[kroy]

Information how to enable UPnP port mapping on nxserver is available here: https://www.nomachine.com/AR11L00827. Just set EnableUPnP NX in the /usr/NX/etc/server.cfg.

After changes in server.cfg you should restart nxserver (sudo /usr/NX/bin/nxserver --restart).

External IP and port on which you can connect you can find on “Welcome screen” on the NoMachine player. You can also execute command sudo /usr/NX/bin/nxserver --upnpmap. External IP and port should show in the line starting with “NX port 4000 mapped to”.

[kroy]

Have you tried following these instructions https://portforward.com/actiontec/t3200m/ ?

More details about what default ports are used by NoMachine are available here: https://www.nomachine.com/AR01L00770.

[kroy]

Hi.

We couldn’t reproduce problem on different virtual machines with CentOS 5.11. But we would like to look closer to this issue.We couldn’t find CentOS 5 image on openstack sources (https://docs.openstack.org/image-guide/obtain-images.html). Can you tell us how you prepared the image with CentOS 5? Send a link with instructions.

[kroy]

Yes, you are right – installation of NoMachine depends on the OS and it’s efficiency. Useful tips for Raspberry you can find here: https://www.nomachine.com/tips-on-how-to-set-up-your-raspberry-pi-for-remote-access-via-nomachine. We made some tests and it shows that the most efficient OSes on RPi3 with NoMachine on 1080p resolution are Ubuntu Mate 16.04 and Raspbian 9 on armv7 architecture.

Connection to the physical desktop with 1080p resolution:

1) Raspbian 9 armv7

RAM usage for nx* processes: 249 MB
CPU usage for nx* processes: 23.58%

2) Ubuntu Mate 16.04 armv7

RAM usage for nx* processes: 258 MB
CPU usage for nx* processes: 14.93%

3) Fedora 26 armv7

RAM usage for nx* processes: 330 MB
CPU usage for nx* processes: 25.71%

4) Debian 8 arm64

RAM usage for nx* processes: 590 MB
CPU usage for nx* processes: 59.68%

 

About H.264 support. It is available in Enterprise Desktop for Raspberry, that means you get server-side encoding included. It was mentioned in post: https://forums.nomachine.com/topic/hardware-h264-decodeencode-support-in-rpi23.

[kroy]

Hi

We dumped the X.org framebuffer with xwd (https://en.wikipedia.org/wiki/Xwd) and Dashboard screen is also corrupted there. So the problem is on Xorg side, not NoMachine. We suggest you use “Classic Mode” during NoMachine connections.

[kroy]

We couldn’t reproduce the problem. Are you trying to connect via NX protocol? Which NoMachine versions are installed on both sides? If error show again please zip .nx (which is in the home directory) and send it to forum[at]nomachine[dot]com.

[kroy]

You can do it in two different ways.

The GUI method: Show the server status -> Shutdown the server -> you will be asked if services must be started at the next reboot or not.

Second method is to use the nxserver command. Open a terminal and execute /etc/NX/nxserver –startmode manual. More information you can find there: https://www.nomachine.com/DT02O00125#7.2.

[kroy]

Yes – your settings should work.

To check if the connection is under UDP or just TCP – run nxplayer menu during connection and click on “Connection” icon. Search for line “Service type”. There should be information about TCP and eventually UDP port. In your case it should show: “Service type: NX on port 4000 with RT port 6000”.

[kroy]

Can you try disabling Lock screen in server configuration (https://www.nomachine.com/AR07M00851) and let us know if it helps?

[kroy]

I reiterate that booting in Safe Mode will mean that connecting via NoMachine to such session will not be possible.

[kroy]

On the version 6 the ‘NoMachine login’ authentication method is no longer supported. On 6.0.80 packages it also shouldn’t be available.

Are you sure that this is the version installed on that Windows? Can you send player logs? They are in the .nx folder, which is placed in the home directory of the connecting client.

Also, if you are connected to an NX server version 3.5, please zip up the .nx directory and send file to forum[at]nomachine[dot]com.

[kroy]

Thanks for the report. Issue will be fixed as soon as possible. Please follow this trouble report: https://www.nomachine.com/TR03P08451 and use the notify me tool to know when a fix is available. As a workaround you can open cmd on the client side (you don’t need administrator privileges), navigate to NoMachine Client installation directory (in default NoMachine folder is created in the home directory) and execute command:

bin\nxkeygen.exe -u > etc\uuid

[kroy]

If you are using vp8, .nxv file is already playable using common video players without converting or changing the file extension. You can also use ffmpeg or other programs to convert it (transcode) to a different video format. Example ffmpeg command to convert nxv to mp4:

ffmpeg -fflags +genpts -i your_video.nxv -r 24 your_video.mp4

At the moment, if you use h.264 codec you won’t be able to play the .nxv file with common video players or to convert it.

We have plans to provide a transcoding tool in NoMachine in the future.

[kroy]

We aren’t able to reproduce this problem.

Can you enable debug on the server side, restart nxserver and reproduce issue?

Please send server side logs and player logs from the client side (it’s folder started with “R-“, which is in .nx folder in the user’s home directory). Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT10O00163

[kroy]

There are no symbols in the backtrace. Are you sure that you specified all the gdb options mentioned in the article?

Please execute following command:

sudo gdb  -core=<path_to_core_file>  -se=/usr/NX/bin/nxnode.bin

[Author]

Posts