Forum Replies Created
-
Posts
-
Can you send us the install.log or update.log? Neither of these were in the log file you submitted. You can find them in ProgramData with the other log files, or if something went wrong with the installation you can find them here: C:\Users\%USERNAME%\AppData\Local\Temp\Setup Log…2019-06….txt.
Thanks.What’s the Linux distribution and version? I take it you are connecting to a computer with the free version installed? Please try submitting the file, which failed to attach, to forum[at]nomachine[dot]com.
Please see here: https://forums.nomachine.com/topic/download-old-versions
Hi, you could try this.
1) connect to the remote desktop
2) to close the session, use this shortcut: Ctrl-Alt-T
3) make sure the box at the bottom is flagged “Remember current window size and position” (screenshot attached)
This needs to be done only once.
If that doesn’t help, then we need the specific steps to reproduce.
Attachments:
If NoMachine doesn’t find a local x server, NoMachine starts its own virtual display. If you restart the NoMachine service, the virtual display it just created is obviously terminated, hence you are disconnected.
To avoid this problem, you can either:
– make sure a graphical interface is installed
– or avoid restarting service
Hello, can you do the following:
1) try disabling hardware encoding on the server (see https://www.nomachine.com/DT10O00155#2.5)
2) try disabling hardware decoding on the client (see https://www.nomachine.com/DT10O00157#5.7)
If neither of those helps, please send us the logs which you can extract once you’ve enabled debugging and reproduced the problem. Please consult this document for instructions: https://www.nomachine.com/DT10O00163 and send them to forum[at]nomachine[dot]com.
Hi, we’d like to send you a debug version to help us further with investigation. Is this ok with you?
You need a desktop environment installed in order to be able to use NoMachine. If you remove the Graphical Interface, NoMachine can’t run a graphical remote session.
As stated here: https://www.nomachine.com/DT02O00124
Software requirements
A desktop environment must already be installed. This applies also to headless Linux machines.If you don’t want to use Gnome, you can use KDE, LXDE, XFCE or another if you prefer.
Hi cosuan, what you need is this Feature Request which is currently being implemented.
https://www.nomachine.com/FR10N03220
Please sign up to receive notification of when it has been released.
Hi, the correct behaviour is:
Click Yes if you want to close the NoMachine app, and upon the next Windows session, everything will be started up again.
Click No if you want to close the NX services and at next reboot, you prefer to restart NoMachine manually.
So you have understood correctly it would seem 🙂 However, selecting either requires Administrator rights and the system will ask you to enter your Windows account credentials. Do you not see the box asking you to enter admin credentials?
Please tell us the Windows version you are using. This will be useful to be able to investigate whether services are being restarted within the same session rather than at start-up.
@dlp_1 did you get the email containing the link to the debug package?
@kosak @graphixillusion, please check your inbox. We have sent you a link to the patched package for testing.
That seems very odd. The NoMachine Installer auto-detects the system language. Can you show us a screenshot of what you see once NoMachine has been installed? What OS are you installing on?
Let’s check some other details first (you may have already checked this, I’m not sure):
1) https://www.nomachine.com/getting-started-with-nomachine#internet
Figs 9 and 10 can show you which IP you should be using to connect from the external network.
Quoting from the guide: “NoMachine will display it like this: nx://151.1.192.128:29382. Write this information down. If a port number is not displayed next to the external IP, NoMachine has detected that you don’t need it in the next phase.”There is the possibility that you have a double NAT in place, but this would mean intervening on both routers. There is a similar topic here: https://forums.nomachine.com/topic/error-138-cant-connect-to-office-computer-from-home
NoMachine Network, the upcoming feature, would resolve this problem. It would avoid having to know your computer’s public-facing IP address and eliminate the need to configure port-forwarding on the router.
