Forum Replies Created
-
AuthorPosts
-
March 18, 2021 at 20:13 in reply to: NoMachine app doesn’t rotate when on high dp settings, low res screen #32464
Tor
ParticipantHi Gato. 🙂
I’ve set the UI on my Android to dpi 600 dp, this forces NoMachine into horizontal mode only, the app thinks I’m on a tablet.
Physical screen size detection is based on screen pixel’s density, so changing the DPI value affects the result. This is normal and the application behaviour is expected. When running in tablet mode the user interface needs a wide horizontal space, that’s why it doesn’t allow the portrait orientation. We’ve experimented multiple solutions but none of them was good enough to unlock the orientation, so unless we change the interface to be the same on all devices (something we’re actually evaluating, anyway) I’m afraid I can’t offer a quick solution for your configuration.
My feature request would be that the NX player resizes when you open the OSK.
Yes, this change is definitely on our road map. We didn’t want to reduce the viewport size because we’re unaware of the current remote cursor position and movements to reach it could be pretty narrow, but your experience is clear and we want to improve it, no doubts.
Thank you for your feedback!Tor
ParticipantI have the same problem. My server always has “Desktop not shared” in the server status page and the toggle in the lower right is greyed and not clickable.
Hi mymachines, and welcome!
The control is greyed out when your desktop can’t be shared or when there is no way to change the status, but I guess you already knew this! 🙂 Let’s see why this can happen.1. Your server is not running. You can easily verify this by opening the Settings > Server > Status.
2. Your server is configured to not allow the desktop sharing. You can confirm it by checking the status of the box “Share the desktop at server startup” in the Server Status panel.
3. Your NoMachine client is running in a Windows Terminal Server. In such a case NoMachine can’t access to the RDP desktop, thus the client can’t change the sharing configuration. I suppose this is not your case, I’m listing it only to give complete information.If you confirm you’re not in any of the above cases then you could have an unexpected issue, so let’s debug it!
Please open the command prompt and run the command"%ProgramFiles(x86)%\NoMachine\bin\nxserver" --status
(binary path between double quotes), what’s the output?
Open a file browser and enter the folder%ALLUSERSPROFILE%\NoMachine\var
(you can paste the path in the address bar), then compress the folder “log” and send it to forum[at]nomachine[dot]com by using the topic title as subject.Tor
ParticipantIf you are sure that the server configuration is correct, I’d say something in your network or firewall configuration is dropping your packets by causing a timeout. Try to run the command
nc -v <hostname> 4000
and confirm that you receive the message “Connection to … succeeded!”. If you do not, then you should try to debug your firewall or VPN.Tor
ParticipantIf the client can create the connection file it should also be able to modify it, but just to be sure everything is correct, could you check permissions and ownership of folder Documents/NoMachine and connection files stored inside it?
Please try also to right click the connection in the Machines list, select the item “Create a copy file”, save the new file on the desktop and connect by using this entry instead of the original. Are credentials saved in that case?
Tor
ParticipantHi klnbrk. Your logs point out networking problems, it looks like you loose the connection to the VPN and to the remote desktop, and from that time on the client could not reconnect because it could not find the server host. Could you verify the network stability with ‘ping’ or similar tools?
Tor
ParticipantHi flight750, please try our latest update and let us know if the window resize now better fits your needs.
Tor
ParticipantPlease open a Command Prompt window and let me the output of the following command:
find "EnableAcceptingConnection" "%ProgramFiles(x86)%\NoMachine\etc\node.cfg"
Tor
ParticipantHi. Did you try to enable desktop sharing by using the link in the bottom-right corner of the client window?
You can find a description here:February 17, 2021 at 16:03 in reply to: Cannot grab special keys after upgrading to Ubuntu 20.04 #32015Tor
ParticipantHi. Please try to start the player with the
--activegrab
option, by running the command/usr/NX/bin/nxplayer --activegrab
If it helps you can either create a link to the player to always add that option, or you can edit the file
$HOME/.nx/config/player.cfg
and set the configuration key “Enable active keyboard grabbing” to “true”.Tor
ParticipantHi. What is the Windows version running on the computer where you try to change shortcuts?
Did you try to register multiple different shortcuts, and none of them work? There is a chance that some key combinations are already used by the Operating System, so NoMachine can’t take over it.About changing the host resolution, if you want to avoid that behaviour you should be sure to disable the Display option “Resize remote display” and never select the radios “Resize the remote display…” in the Display resolution welcome panel.
Tor
ParticipantHi. About the credentials saving issue, do you connect to the server through an automatically discovered server item, or did you manually configure the connection by setting the server IP? If you’re not sure open the context menu by right clicking the connection item, and check if the “remove connection” menu entry exists or not.
PS: I’m discussing the connection dropping in the other thread you’ve opened, to better split the topics.
Tor
ParticipantHi. Does the disconnection occur as soon as you minimize the window, or after some time? Is the window disappearing when you minimize it, or it stays open with an error explaining the disconnection reason? In the latter case, what is the error?
PS: I’m going to ask for details about the username/password problem in your other thread, to better split the topics.
Tor
ParticipantWe’ve found a problem with the Magic/Smart Keyboard, the device still reports it as available also when it gets disconnected, so the app behaviour is unexpected. Can you confirm if this could be your case? If it is so, restarting the device when this happens causes the keyboard status to be reset and fixes the NoMachine app issue.
However we didn’t reproduce the pinch gesture problem, could you share additional details? It doesn’t work at all, so pinching in/out is just ignored?January 20, 2021 at 15:42 in reply to: ClientSession: Failing reason is ‘The session negotiation failed.’. #31390Tor
ParticipantHi. Do you mind sending whole logs directory where you’ve found that file to forum[at]nomachine[dot]com? We might need also server side logs, but let’s try to grab as much info as possible from the client first. Thanks.
Tor
ParticipantPlease, what is the iPadOS version you’re using?
-
AuthorPosts