Forum Replies Created
-
Posts
-
Hello,
It seems the issue might be with port forwarding if multiple routers are involved. Ensure that:
Port Forwarding: If you have a secondary router, forward the port from the first router to the second router’s IP, and then from the second router to your NoMachine server’s local IP.
A similar topic is here: https://forum.nomachine.com/topic/double-nat-remote-through-internet
UPnP: Check if UPnP is enabled on all routers or manually configure port forwarding if needed.
External IP and Port: Use your public IP (e.g., from WhatIsMyIP.com) and the port configured for NoMachine when connecting remotely.
Firewalls: Temporarily disable firewalls on routers and the server to rule out connection blocks.
If the issue persists, let us know more about your network setup for further assistance.
Hello,
Thank you for sharing the details of your setup! To assist you further, could you please provide the following information:
- The operating systems running on the three computers.
- Are you using valid credentials (username and password or PIN) for each specific computer to log in?
- Can you log in remotely using these credentials through other methods, such as SSH, if available?
This information will help us better understand the issue and suggest appropriate troubleshooting steps.
Hi, thanks for reaching out.
It sounds like you’re encountering a common challenge when working with mixed-resolution setups. NoMachine provides several options for configuring how the remote desktop is displayed, allowing you to adjust the resolution and scaling to best suit your setup.
I recommend checking out this guide: https://www.nomachine.com/configuring-how-you-view-the-remote-desktop. It explains how to experiment with different view modes, including scaling and resolution options, to find the one that works best for your 1080p laptop and 4K work machine.
Here are a few tips to consider while experimenting:
Use the “Fit to Window” mode to ensure the remote desktop adjusts dynamically to your local screen.
Try the “Resize remote display” option, which resizes the remote desktop to match your laptop’s resolution.
If you prefer setting a custom resolution for your NoMachine session, you can do so in the Display Settings on your remote machine or via the NoMachine session settings.
Cheers
Hello,
It’s important to note that the NoMachine app for Android is a client-only application. This means that while you can use the Android device to connect to other NoMachine-enabled devices (such as your Windows desktop), it cannot act as a server for incoming connections. This is why your Windows machine cannot see or connect to your Android tablet.
For further guidance on setting up and using NoMachine on Android, please take a look at our official guide: https://www.nomachine.com/getting-started-with-nomachine-for-android.
Hello,
Please send us the logs from the NoMachine server. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Send them directly to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
Hello,
Be sure that you installed the server product suitable for your license, then follow the instructions here: https://kb.nomachine.com/AR04T01157
Hi,
NoMachine Network is not yet available. It’s planned for the next NoMachine 9 and we are working diligently to deliver this next major version as soon as possible.
Hello,
thank you for your post.
NoMachine prevents a shutdown/sleep only when the session is active. Can you please try without an active session?
By default, .nxs files are stored in the directory specified in the ‘Connections and recordings’ field under Settings -> Player -> Folders panel of the User Interface. Here’s the default directory for each operating system:
Linux: /home/USERNAME/Documents/NoMachine
macOS: /Users/USERNAME/Documents/NoMachine
Windows: %USERPROFILE%\Documents\NoMachine
Hello,
Our Terminal Server Family range of products for Linux supports the ‘virtual desktop’ functionality, which allows users to have their own personal ‘virtual’ desktop on the host machine.
Specifically, NoMachine Workstation supports up to four virtual desktops per Linux host, Small Business Terminal Server supports up to ten, and Terminal Server supports unlimited.
30-day evaluation links are available on the links above.
A schematic diagram for a typical NoMachine server setup on Linux can be seen here: https://kb.nomachine.com/DT06S00226
Instead of terminating the session, we suggest using the
--disconnectcommand. Could you please provide more information about the issue you are experiencing with the lost X session?You can try using the following commands:
sudo /etc/NX/nxserver --disconnector
sudo /etc/NX/nxserver --disconnectPlease let us know if the problem persists even after using the above commands.
Hello,
Nokia 1 comes with Android Go Edition, which has strict requirements for the apps that are allowed to support it. These requirements include a small memory footprint, limited app size on-device, and more. However, we cannot meet some of these requirements due to various reasons. Unfortunately, we cannot distinguish unsupported devices and support only compatible ones. It’s an all-or-none approach, which means we either support all Android Go devices or none, regardless of their hardware specifications.
Hello,
You can check if connection files are being created in Document/NoMachine. If not, make sure folder permissions are correct. If issues persist, send us client log directly via email to forum[at]nomachine[dot]com making sure to reference the title of the this topic (in the subject).
How to collect the logs: https://kb.nomachine.com/DT07S00244
Hello,
Thank you for your proposal. We will definitely consider it in the future. You are always welcome to send us your recommendations!
Hi,
We’re not sure what you mean with “real IP”, maybe you mean the “external IP” (but it would be more clear if you can provide an example). If that is the case, very likely the different behaviour of version 8 is because we disabled UPnP by default, so the external port is not mapped on the router. So you should enable it again in the ‘Server settings -> Ports’ panel.