Britgirl

[Britgirl]

The next update for the NoMachine Mobile app, to be released after we have released version 8 for desktop, will be based on the new APIs provided by the most recent iPad versions which will mean full support for mouse devices connected to the iPad. As a temporary workaround,  you could use touch gesture to perform the right mouse click and the mouse scroll.

[Britgirl]

Hi, is it possible you installed the NoMachine app on your Macbook?. Try the .dmg package from our website instead.

[Britgirl]

Hi, can you provide more details? A screenshot showing the “no desktop found” error and the steps you take which result in that error dialog would be useful. What macOS version is it?

Additionally, logs from the Mac on the server side would also be helpful. Please follow the instructions here and submit them to forum[at]nomachine.com making sure to reference the title of your topic as the subject of your email. Thanks!

[Britgirl]

We haven’t been able to reproduce this issue using the same set-up. Make sure that before changing any parameter in the player.cfg on the computer you are connecting from, you exit the player (click on the !M icon in the system tray and select Exit the player). Once all nxplayer processes are closed, then edit the cfg file and try again..

[Britgirl]

Having a local user account on the remote computer you want to connect to is pre-requisite, like you have on the other PC that you have tried and successfully connect to (like when you connected from your tablet to the Windows PC you used account credentials to log in to the desktop, for example) You must always use a username and password to log in to the desktop that is running there.

Further references:

https://www.nomachine.com/getting-started-with-nomachine
Section 3 of the installation guide: https://kb.nomachine.com/DT10R00166#3

Glad to know it’s now working.

[Britgirl]

Are you using password authentication to log in?

Username formats which can be used are detailed here:
https://kb.nomachine.com/AR03S01118

Logs would also help us understand why authentication is failing. Instructions on how to extract them are available here:

https://www.nomachine.com/DT11R00182

Please submit them to forum[at]nomachine[dot]com.

[Britgirl]

and a little bug – in kubuntu left mouse click on tray NoMachine icon not raises NoMachine main window
only need to right click and select “show main windows”

Thanks for reporting, we’ll get that checked out.

I tried to connect to another Ubuntu 20.04 machine, and can select option not to resize (as on screenshot)

You probably selected to not show this dialog anymore. Welcome panels appearing when the connection to the desktop has been established can be restored by checking the “Reset saved preferences and password”  box while editing the corresponding connection settings.

These options in the welcome panel are always available on the bottom on the menu. In your case, it is the most left icon (https://kb.nomachine.com/DT10R00168?#5). When multiple monitors are present, it’s the penultimate on the left.

[Britgirl]

Can you check your External IP and compare with what’s showing, for example, on whatismyip.com? If IP addresses are different, then that would indicate indeed a double NAT.

If it’s the same, I advice you to start again (remove old changes, basically to what you had before changing anything) and set Port Forwarding with for example 24222 (or other – but not 24224 which is used for UPnP which is what I’ve understood you’ve done).

[Britgirl]

You can set the “Session window geometry” key in the .nxs session file to a specific client screen resolution. So for example your screen resolution is 1920×1200:

<option key=”Session window geometry” value=”0, 0, 1920, 1200″ />

Also set these keys to viewport:

<option key=”Physical desktop resize mode” value=”viewport” />
<option key=”Session resize mode” value=”viewport” />
<option key=”Virtual desktop resize mode” value=”viewport” />

So if the remote display resolution is smaller than the client window, the client window will be resized to show the exact remote display resolution; so will automatically match the exact size which is needed to show full remote server display. If remote display has bigger resolution, we will just show scroll bars, but still, remote display will be not be scaled.

[Britgirl]

Thanks for the attachments, but we would need server-side logs with debug enabled to be able to understand what is happening. Please see the following document for instructions on how to extract the logs, https://kb.nomachine.com/DT11R00182, and submit them again. Thanks!

[Britgirl]

We would need server-side logs to be able to understand what is happening as we haven’t been able to reproduce on the fly. Please see the following document for instructions on how to extract the logs, https://kb.nomachine.com/DT11R00182, and submit them to forum[at]nomachine[dot]com making sure to put the title of your topic as the subject. Thanks!

[Britgirl]

Out of interest, are you able to physically set the resolution as you want it in KDE? I.e not by connecting with NoMachine?

Nothing has changed in NoMachine that would change how resolution is handled.

NoMachine client configuration let me choose several different resolutions and now it doesn’t.

Were you maybe using NoMachine Workstation in the past? This would allow different resolutions (being virtual NoMachine desktops). A note from the article I mentioned earlier: The supported resolution for virtual NoMachine desktop sessions (Terminal Server for Linux products) doesn’t depend on the remote hardware and thus the remote screen can be resized to whichever resolution is supported by the user’s local monitor.

[Britgirl]

It’s not supported. We are evaluating whether to make the ProxyJump setting possible for a future version.

[Britgirl]

Most likely the issue was attributed to this larger system error.

Thanks for letting us know.

[Britgirl]

Hi, when you searched the forums, did you also find the article about how to connect over the Internet? And did you follow the tips there?

How to connect over the internet to NoMachine behind a NAT router
https://kb.nomachine.com/AR10R01099

“Failed to map the port on gateway” suggests that the port you used in the port-forwarding rule on your router could already already be in use. Go back to your router and change the external port number to, for example, 24222, the restart the nxserver (NoMachine settings -> Server -> Status -> Restart) or you can do it from the commandline. For safe measure also restart UPnP.

Open CMD as administrator and execute:

c:\ProgramData\NoMachine\nxserver\nxserver.exe --restart
c:\ProgramData\NoMachine\nxserver\nxserver.exe --upnpmap

Is it possible there is a double NAT in place? If so, you will need to map the ports on both routers. So Router A must map to Router B and Router B to the computer you want to access.

[Author]

Posts