Tom

[Tom]

Hello,

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.

[Tom]

Hello,

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.

Regards
Tom

[Tom]

Hello.

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.

Regards

Tom

[Tom]

Hello,
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.

Regards
Tom

[Tom]

Hello.

By default, the sound on Windows 2016 is working fine.

Is Windows 10 a physical machine?

What image (AMI) is Windows 2016 installed on ?

Regards
Tom

[Tom]

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.

 

[Tom]

Hello,

Please try one of these commands:

ssh -fN -R YourOfficeIP:10022:localhost:4000 ubuntu@a.b.c.d

or

ssh -fN -R *:10022:localhost:4000 ubuntu@a.b.c.d

In the first command replace ‘YourOfficeIP’ with the IP address of your office, if the IP address of your office is static.

The second command allows you to connect through SSH tunnel from any address on the Internet.

Regards

Tom

[Tom]

Hello

I understand you have a laptop at home/office.

You have a dynamic IP address.

You configured Duck DNS on it and have domain name eg. exampledomain.duckdns.org.

Being away from home/office you want to connect by NoMachine to this laptop ?

NoMachine does not need to be configured.

First you need on your router to forward port 4000 to port 4000 and the IP address of your laptop. Of course it can be any port eg.5234 forwarding to port 4000 on your laptop.

Then in the external network to connect to your laptop use the domain name you set up in Duck DNS and port you configured on your router.

 

[Tom]

“Hello,

perhaps you installed NoMachine Server package.
On our website you can find a package called “NoMachine Enterprise Client”.

It’s a package that installs only the NoMachine Client.

During the installation of Enterprise Client a nx user account isn’t created.
You can find this package in the tab download, “Enterprise Products Evaluation” section.
Regards

Tom

[Tom]

Hello.

In log I see that you tried connect to IP 10.0.3.1, this is local address.

Is IP address are you try connect over the Internet ?

If so, please check your Internet IP address on this side http://whatismyipaddress.com ( Do not give this address in the forum ).

Try to connect to address from the web side to port 4000.

If no, please give us the model of your router.

Regards

Tom

[Tom]

Hello,

on the headless machine eg. on AWS EC2  navigate to the <user’s home>/.nx/ create directory ‘config’.

In the ‘config’ directory create file ‘authorized.crt’.

Copy to this file contents of your public key file, this file has the extension .pub.

After completing these steps you will be able to connect to the NoMachine using the private key.

[Tom]

Hello,

If I understand your set up clearly, you have 10 developer workstations in your office on your LAN. You have customers/other developers which need to access one/some of/all these computers on your LAN.

For each of the developer machines you want to provide access to/share desktop with you will need to configure your pfSense router to bind one port for each machine on the internal network.

For example you can configure (on the router) port 4001 for Dev 1 machine and forward this port to the local IP address and port 4000 of the Dev 1 machine; port 4002 for ” Dev 2″  and forward it to the local IP and port 4000 of the Dev 2 etc.

Customers can connect to Dev 1 using your external IP and port 4001. Many customers at the same time can connect to one port. Ports 4001 and 4002 are only an example and can be changed.

For you pfSense router you can forward ports in menu “Firewall”, sub menu “NAT”, tab “Port Forward”.

Click on the ‘+’ sign to add port forward.

Set “Destination” to “any”.

In “Destination port range” set the port to which you want to bind to first developer machine.

In “Redirect target IP” set first developers internal IP for example 192.168.0.101.

In “Redirect target port” set to “other” and write 4000.

Save changes.

After this you can connect to ‘Dev 1’ from the internet indicating in your external IP address and port xxxx in the player GUI.

You need to set this up for all the computers, of course, giving another external port for each of them and internal IP.

[Tom]

Hello,

You do not need UPnP and NAT-PMP to connect to your computer from the internet.
You can configure the router to forward the connection from external IP and port 4000 to the IP and port 4000 of the local computer

Of course, port 4000 is only an example, you can set it to a different one if you want.

For example, you can set up port 4689 on your router so that it is redirected to the internal IP and port 4000 of your PC.

In this case, to connect your computer form internet, you will need to set the external IP and port 4689 in nxplayer.

Changes in the NoMachine server are not needed.

[Tom]

Hello,
Can you connect to the Mac from your home network?
Did you set port forwarding on your home router?
On the Mac you have installed the software that can to block ports?
Please give the name and model of router.

Could you provide server log files form Mac?
You can follow this guideline: https://www.nomachine.com/AR07K00677
and send to them forum[at]nomachine[dot]com referencing your topic.

[Tom]

Hello.

Is this a free version of NoMachine?

Is port 4000 open on CentOS?

On CentOS is NoMachine server running?

Please check the following command from console:

sudo /usr/NX/bin/nxserver –restart

After running this are there are any errors?

[Author]

Posts