Forum Replies Created
we confirm the problem.
We are working on a solution.
on your MacOS, when you connect with a VPN and turn on NoMachine, you won’t see computers with NoMachine installed, as you do on your local network, mDNS doesn’t work over VPN. Computers with NoMachine installed from a network connected via VPN have no way to send information that they are ready to connect. In this case, they will not automatically appear in the NoMachine list as ready for connection.
In the attachment, the address you are trying to connect to is blurred, is it really a local address from the network you connect to via VPN?
To connect you will need the local IP address of the computer you want to connect to.
Try to connect via NoMachine to this IP address with the VPN enabled.
TomJuly 7, 2020 at 09:14 in reply to: How to connect to VM without external ip in Google Cloud platform #28432
you must configure Bastion host as an intermediate host between the home computer and the destination host (Linux host).
I assume that the Linux desktop you want to connect to has disabled external IP connections. Bastion host and Linux desktop are in the same internal LAN.
In the VPC network in Firewall:
1) Add a rule allowing connections to port 4000 (you can set a different port) e.g. using „Targets tags”. If your Windows host has a fixed IP you can set the connection permission only for that IP.
2) Add a rule that accepts connections from the local network to any port or only to port 4000 e.g. using „Targets tags”
In Compute Engine:
Assign this rule 1 to the Bastion host, e.g. using „Targets tags”.
Assign the rule 2 to a Linux host, e.g. with “Target tags”.
Log in to the Bastion host and add rules to redirect traffic on port 4000 to Linux host using iptables
Set traffic redirection from port 4000 to Linux host:
iptables -t nat -A PREROUTING -p tcp –dport 4000 -j DNAT –to-destination x.x.x.x:4000
iptables -t nat -A PREROUTING -p udp –dport 4000 -j DNAT –to-destination x.x.x.x:4000
iptables -t nat -A POSTROUTING -j MASQUERADE
Where x.x.x.x is the local Linux host IP.
Now connecting to Bastion host on port 4000 using NXPlayer the connection will be transferred to your Linux host.
TomJune 22, 2020 at 15:50 in reply to: Connecting NoMachine Ubuntu 16.04 to NoMachine Windows 10 within VPN #28243
in the attached logs there are no NX Player logs from Linux.
In the link you can get help on how to do it:
Server and NX Player logs should be done at the same time.
The server logs indicate that you tried to set the server port to 3389. There were problems running nxd.exe during this attempt.
Have you tried connecting to such a port via NX Player?
The rest of the entries indicate that this port has been changed.
Trying to connect from Linux (client) to Windows (server) you always have to connect to the port that has been set on the server side.
The easiest way is to set the server to the default port 4000 and try to connect to it, after successful connection you can change this port to another one.
In the link you can see how to check the server status and port:
What version of Windows do you have?
Do you have home or professional version?
Can you connect with NoMachine to the computer on the LAN from this Windows?
Is the Windows computer in a different location than the Mint computer?
TomMarch 4, 2020 at 11:15 in reply to: How to install on Digital Ocean Droplet via command line #25848
if you have desktop environment installed you can download NoMachine package from nomachine.com.
If your fedora does not have a desktop environment installed, you must install it first before installing NoMachine.
There are several options for downloading the package without desktop.
Install wget and download the package from the site using these commands.
yum install wget
Or download the package from the NoMachine website to your computer, then send to DigitalOcean using the scp command.
scp nomachine_6.9.2_1_x86_64.rpm email@example.com:~
x.x.x.x is your Fedora IP
How to install NoMachine form console you can find in this article
Do you have double WAN connected to router?
Is your IP dynamic?
Please check on host, where NoMachine is installed, what IP shows on website https://whatismyipaddress.com or similar.
Compare the IP shown by NoMachine with that of the website.
You can tray tracert or traceroute (system dependent) to check which route your packets are going through. If NoMachine shows the address 32.160.xxx.x and your service shows the address 68.108.xxx.xxx. Packages pass through them in order of address 32.160.xxx.x first and then 68.108.xxx.xxx?
Numbers after the colon are open port on your router for NoMachine connection to this host.
TomAugust 19, 2019 at 08:29 in reply to: Can’t connect to ssh or NoMachine on Google cloud platform Linux VM #23296
Thank you for your comment.
You have a connection to the machine but you cannot login?
Do you use VM “External IP” to connect?
What error do you get when you connect?
In the link below you can check how to solve the most common problems with the ssh connection
TomAugust 14, 2019 at 16:10 in reply to: NoMachine connection P2P but not WAN other than port 4000 #23290
Thank you for your comment.
The information about your gateway settings is a little bit confusing; we are not sure if you have these mentioned two ports (4000 and 4023) redirected on router by your ISP or if you have admin access to the router and you are able to redirect it by yourself.
Technically, every computer in your LAN should have a specific port redirected on your router.
If you want to reach more than one computer from WAN, you must set, on the router, the port forwarding to local IP and port 4000.
first computer – WAN port 8001 forward to IP 192.168.1.10 and port 4000
second computer – WAN port 8002 forward to IP 192.168.1.11 and port 4000.
please connect to your Windows via https protocol.
To do this please add to security group two rules:
Custom UDP for port 4443 for source set your client IP.
Custom TCP for port 4443 for source set your client IP.
After this you can connect to Windows via browser on your client using https://machine_ip:4443
Please use the same username and password as you do an for RDP connection.
NoMachine doesn’t change a computer’s IP.
Changing the IP address may be due to the fact that you do not have a static IP address assigned by your ISP. The address may change from time to time or during the restart of your router.
The solution to this problem may be the use of Dynamic DNS eg. https://www.noip.com, https://dyn.com/dns/. Your router may have the ability to configure such service.
Software for informing Dynamic DNS about changing the IP address may also be installed on the computer on which you have installed NoMachine.
Do you use RHEL 7?
If so, then after installing desktop with the command – sudo yum groupinstall -y “Server with GUI”, set the default run level using the command – sudo systemctl set-default graphical.target.
Install NoMachine, add new user and restart your Red Hat.
After restart and new connection you should see login screen.
We thought about two routers, because you wrote about IP 192.168.200.101 and another IP x.x.x.133 .
Now we understand that your NoMachine Server ( computer you want to connect to ) IP is 192.168.200.99. Router has internal IP 192.168.200.101 and you have external IP x.x.x.133.
If this line “1 NoMachine 24004 TCP 4000 192.168.200.101 Enabled” show me set forwarding port 24004 on your router please change this to IP 192.168.200.99. Router must forward traffic on port 24004 to your computer IP.
Please remember that on computer with you want connect you must set in connection IP x.x.x.133 and port 24004.
By default, the sound on Windows 2016 is working fine.
Is Windows 10 a physical machine?
What image (AMI) is Windows 2016 installed on ?
TomJanuary 3, 2017 at 12:11 in reply to: NoMachine doesn’t work after rebooting remote machine #13392
NoMachine allows you to view the display server to which you are connecting. This makes it possible to connect to the desktop of another user. If you restart your PC you will see the login screen with user accounts created on this machine. NoMachine does not log on to the system as user, it checks the user privileges to show you the system display.
Do you want users to access a common desktop or should each user have access to only one virtual machine? If the latter, maybe a solution for you is to set “Automatic login” on this machine. Then after restarting, when you connect to this machine you will see the logged user’s desktop only.