- This topic has 6 replies, 2 voices, and was last updated 1 day, 20 hours ago by
.
-
Posts
-
Hi, Been a user of NoMachine for almost a decade now. I recently needed to reinstall NoMachine (and have installed the latest free version as well — 8.16.1), but getting my remote computer connected keeps failing with “A connection timeout has occurred while trying to connect to ‘192.168.50.8’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.” It will not let me get to the stage where I enter username and password.
The computer I am trying to connect to is running Windows 11, the one I am connecting from is Windows 10
When I tried loading NoMachine onto a different computer connected to the same WiFi, it made a connection to the machine I wanted instantly and seamlessly, so I am very confused about what the issue is. The reported IP matches not only what NoMachine says is the IP, but there’s a wholly different and unrelated program that is using the same IP to share a data connection and that also matches that IP.
But I can’t connect from a remote location using that.
I am a pretty low-info user, and get really confused by a lot of the terms thrown around in the documentation, so “Explain Like I’m Five”?
Thanks for any help!
Hi,
so just to clarify, you have 3 computers on the same network (1 Win 11, 1 Win 10, and 1 other which you tried and which was working, let’s call it MachineC), and they are all on the same LAN.
The reported IP matches not only what NoMachine says is the IP, but there’s a wholly different and unrelated program that is using the same IP to share a data connection and that also matches that IP.Can you give some more details? Is this program on the Win11 machine? If you disable it, can you then connect? You won’t be able to connect to your computer if the port that NoMachine uses is in use by another application.
If you’re still not able to connect, can you confirm that they are all on the same LAN? Can they all “see” each other. With that I mean whether your Machines panel is showing the other machines on your same network (https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network). Can you see, from MachineC for example, the other two? Can you see, from your Win10, the Win11 computer?
When you connect to any of your machines, are you connecting by creating a connection manually (via the Add button), or are you connecting through local discovery? You can answer with a screenshot of the Machines panel if you prefer.
Not quite. The w11 machine has the program (a program that uses filemaker as its core) that connects to a wholly different (not any of the “three computers”) w10 machine on the Local Network. But this connection is a hardline connection, using “fmnet://192.168.50.8” to do so. There is no port information, or way to adjust this elderly program AFAIK. This is a red herring, I think, because when I am trying to connect using NoMachine, this w10 machine is off and not connecting to w11 at all. I only mentioned it because this Filemaker based program is successfully using the IP listed, so the IP is, in theory, correct. For about a decade NoMachine has had no problems “sharing” space in the previous installation — even when both w11 and this w10 connection were live. However, once again, as I am trying to get NoMachine to connect, this w10 is off.
The w10 machine in this “three computers” example is a different computer from the w10 referenced above, and more importantly, it is OFF SITE, and not connected to the LAN at all. I purely use it to log in from home to access my (work) w11 computer. It can’t “see” any of the work computers, unless it is connected via NoMachine. This is the one showing the “connection time out” message when using the IP that NoMachine told me to connect with (192.168.50.8 on port 4000).
The third machine (MC — also a w11 machine, btw) is literally fresh out of the box new computer which I have not installed anything except NoMachine to (And, in fact, already uninstalled from after this test, since I will never want to remote to or from it). Its a literally brand new computer with zero other software or connection. It’s not networked to anything else at the minute, but I thought I would quickly test if it, being in the same building, could connect using the IP presented by NoMachine. It’s using the same wi-fi as W11, but otherwise has no other connection to the Local Network, and can not “see” W11. It instantly connected using the displayed NoMachine IP protocols listed in original message, however.
When connecting either MC or w10 to w11 I used the “add” button. Add, paste the IP from w11, connect button. MC connected in 2 seconds, flawlessly, w10 gives me “connection error”
I hope that helps clarify?
I need w10 (which is OFF SITE) to connect to w11 via internet; MC will not be involved going forward. Sorry if the other, digressive, information is confusing things….!
Let’s concentrate on the W10 and the W11 computers to keep things simple 🙂
Please take a look at the following article and make sure you have followed the steps for enabling automatic port-mapping, https://kb.nomachine.com/AR04S01122. You can also see here https://www.nomachine.com/getting-started-with-nomachine#internet. If you are connecting over the Internet, you need to use the IP address that is facing the internet, ie. the public IP address. If it is not showing up in NoMachine, you can check it using, for example, whatismyip.com.
Ah, its that port mapping thing — I never could have found that on my own while I was looking at the knowledge base. All fixed now, so thank you very very much!
You must be logged in to reply to this topic. Please login here.