Forum Replies Created
-
Posts
-
Did you restart nxserver after changes? Please try also enable “Use a specific display encoding” and set it to VP8 before restart.
If you changed network interface you need to restart upnp mapping. To do that you can run CMD as administrator – navigate to bin folder in NoMachine directory (in default it should be in
%ProgramFiles(x86)\NoMachine\bin) and execute commands:nxserver --upnpunmap nxserver --upnpmapYou can also just restart nxserver from GUI (click on NoMachine icon on the Windows tray -> choose “Show the server status” -> and press “Restart the server” button).
Please try to disable acceleration for display processing in the server preferences GUI (https://www.nomachine.com/AR02L00782) and let us know if that helps.
Hi.
We coudn’t reproduce this problem. Can you enable debug, restart nxserver and send server logs from server side and please collect also player logs from client side (it’s ~/.nx folder on your Mint). You can send them to forum[at]nomachine[dot]com? Instructions about debug and collecting logs you can find there: https://www.nomachine.com/<wbr />DT07M00098.
We weren’t able to reproduce this problem. Can you try installing again and when the issue appears zip server log folder (
%ProgramData%\NoMachine\var\log) and send to forum[at]nomachine[dot]com?You should be able to authenticate with added ssh-agent key by providing any key which isn’t configured to allow authentication to the server.
But unfortunately at the moment forward authentication won’t work in this scenario. The issue is under investigation. It should be fixed as soon as possible.
It looks like the issue documented in the trouble report. We can confirm it is if you send us the logs.
Is this a connection to the physical desktop? Does the session works fine before becoming a white screen? Can you verify that the problem shows when the machine on client side loses the connection with network?
We have found a similar problem in such a scenario. The issue should be fixed soon. As a temporary workaround you can terminate suspended session (
sudo /usr/NX/bin/nxserver --terminate <session_id>).Please see the Trouble Report we have open for it: https://www.nomachine.com/TR12M06283
If, on the other hand, the problem is different. please enable debug on server host, restart nxserver (
sudo /usr/NX/bin/nxserver --restart) and send/usr/NX/var/logfolder from server side and~/.nxfrom client side to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.Is there a problem with big UID’s and NoMachine?
No. It should work fine.
A deeper investigation would be required to understand what happens. If you prefer you can just uninstall and install NoMachine again on both machines – this should fix it.
From the logs you attached the problem could be a wrong certificate on player side. To investigate problem we would need also all logs from
/Library/Application\ Support/NoMachine/var/log/from both sides and information about updates. Was systems updated after installing NoMachine 6.0.62?We received player logs from the connecting client side, and nxclient logs from the server side. We would also need also nxserver logs (it’s in
/Library/Application\ Support/NoMachine/var/log/) on the server in order to see what could be wrong.Command
--historycan give quite completely information. Take a look on example:sudo /usr/NX/bin/nxserver --history Display Username Remote IP Session ID Date Status Node Type ------- --------- --------- -------------------------------- ------------------- ------------ -------------- ---------------------- 1005 user1 192.168.0.11 21274CD5BAC280EBA3CA1ED07BC051A8 2017-11-22 16:23:55 Connected localhost:4000 physical-desktop 1003 user2 192.168.0.12 034252F491CB5E6B2EFD0289EA9697C1 2017-11-20 18:26:31 Finished localhost:4000 shadow 1002 user1 192.168.0.13 A706C54F46C2D5C64C0F02E6BEE10767 2017-11-05 23:45:10 Failed localhost:4000 unix-console 1004 user3 - C38F8C100B40A99BE41FDB06CCF38DAB 2017-11-16 08:40:05 Disconnected localhost:4000 unix-applicationIn the “Status” column you have four possibilities:
Connected – when it’s connected to the remote display.
Disconnected – this status is available only for virtual desktop sessions. A session is marked as disconnected when it’s disconnected from the remote display. A disconnected session can be reconnected at any time even from a different machine (migration). While a session is disconnected, applications on remote stay running.
Finnished – the session has been closed in a clean way and all NoMachine processes have been shut-down smoothly.
Failed – Any of the NoMachine processes has failed to start or it has been “un-cleanly” terminated.
More info you can find in link from previous post.
Enabling the VPN client on the server host should not affect access to this machine. So you still should be able to connect to the server via NoMachine.
We weren’t be able to reproduce the problem. NoMachine icon should be visible on system tray on Windows Server 2016. Did you restart machine after installing NoMachine? Does your username or hostname contain ASCII characters?
If the problem still appears please enable debug, restart nxserver and send server (which are located: %PROGRAMDATA%/NoMachine/var/log) and client (%USERPROFILE%\.nx) logs to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.
Is the nxserver running? Problems shows after upgrade – right? Which product and version did you install there? Can you send logs also from server side? Please enable debug and restart nxserver (
sudo /etc/NX/nxserver --restart) earlier. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.