Forum Replies Created
-
Posts
-
The output seems ok. The monitors are extended so all should work. You can use Ctrl+Alt+A shortcut to see all monitors, or Ctrl+Alt+1 (or 2) to switch between them. Check this guide out for more details: https://www.nomachine.com/support/documents/switching-the-view-between-multi-monitors-during-a-remote-desktop-session. Are you not able to switch between them?
Please submit the output of ‘ps -ef’ and new server logs. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298 using the UI. Set the level to Debug, restart the server, reproduce the problem, then “Take logs”.
You can attach everything here or send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
It seems you have enabled a v3 compatibility option in the server.
# dialog=1 display the disconnect/terminate dialogwhich is in the #ConnectPolicy key of the server.cfg.Try setting dialog=0
#ConnectPolicy autocreate=1,autoconnect=1,automigrate=1,desktop=0,dialog=0,xsessions=0,udp=1Now, the terminate button is in Connection info panel. When you close the client window, it just disconnects.
Hi, we have this planned. It was put aside in previous versions to allow us to focus on other priorities, namely NoMachine Network. Development will start soon. About using the x64 package, you can use it, our tests were ok except for functionality that requires device drivers. Installing through chocolatey also worked.
Yes, you are right and we have already started work on implementing support for VA-API.
@Kermu, possible solutions right now to have a working AMD h264 hardware encoder are to downgrade the driver and downgrade the Linux distribution version whilst you wait for support for VA-API to be released in NoMachine. We’re not able to provide an ETA yet, but its high on our priority list.Hmm. We can only reproduce it when logged in as a non-admin user on the client side. We cannot reproduce it when the user is an admin account. Here is when we reproduce it:
1. Non-admin is logged in as the local user on the client side
2. Non-admin or admin user is connecting through NoMachine
3. Sharing is set to Public
4. Remote disk (server side) is shared
Is this the same for you?
In point 1, we also tried with the built-in administrator account and can access the correct drive.Hi, it is not possible to disable them when installing, but there are two keys to do it on server and client:
Please take a look at the following article for details: https://kb.nomachine.com/AR06W01278.
Essentially, after installation on the server machine you can prevent that host being added to Network. Instead, by editing the player.cfg on the device you are connecting from you can prevent logins to the NoMachine Network service and connections with the Machine Id.
Hi, the other topic that you linked points to the Trouble Report, currently open, https://kb.nomachine.com/TR05T10545. We are actively working on a solution. Please use that link to monitor its status. Do you specifically have duplicated monitors on the Windows machine you are trying to blank? As a workaround, set the monitors to ‘extend these displays’: blanking will be set correctly.
“I’ve put the server log into debug mode but sometimes it can go for a week or more without glitching.”
Send in the logs if it happens again 🙂
@Frank, we looked at the logs and noticed a similar problem to this bug report, https://www.nomachine.com/TR06W11409, which was fixed in 9.1, so if you have not updated to the latest version yet, please do so. If you are still seeing the same issue, yes, new logs with debug enabled would be useful. Please see the following instructions for how to set the debug level and gather logs, https://kb.nomachine.com/DT08U00298.
@CheltenhamSteve, it is not clear what steps you are taking to connect to the NoMachine server. What NoMachine product and version are you using on the device you are connecting from and what NoMachine product and version is installed on the target machine?Hi J, please check your email inbox. We have sent you a link to a debug package. Instructions are in the email 🙂
We are unable to reproduce this issue. Did you restart the NoMachine server on the Linux host after applying the changes?
Just one other thing, can you tell us the exact steps you follow to reproduce this issue? We would like to compare your steps with our findings.
Hi, we have reproduced this behaviour and have opened a Trouble Report here: https://kb.nomachine.com/TR03V11109
Please use the link to monitor its status.
If the printer is not shared as a network printer, but plugged in with USB cable, you could try sharing the printer as a USB device. After plugging in the printer with USB cable to the Mac server, start the NoMachine connection, open the menu (Ctrl+Alt+0) and select Connect a USB device, and select the device. You would need to have the printer drivers already installed on the Mac.