Forum Replies Created
-
Posts
-
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!
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….!
Last thing first:
C:\Users\Ocean 2>”C:\Program Files (x86)\NoMachine\bin\nxserver.exe” –upnpmap
NX> 500 ERROR: Only a user with administrative privileges can use option: upnpmap.C:\Users\Ocean 2>”C:\Program Files (x86)\NoMachine\bin\nxserver.exe” –upnpstatus
Local IP 192.168.1.115
Gateway IP 192.168.1.1
External IP 10.1.10.10
NX port 4000 mapped to: 10.1.10.10:24564Using the link you provided above, I only got an IPv6 returned to me, but I thought to google search alternatives and found some that were returning a IPv4 of 67.170.220.172 — so, not a match.
Still fuzzy on the next step, sorry!
“connecting over the Internet will require manual configuration of the host computer’s firewall and router.”
Can someone describe how to do this?
I honestly don’t mean to be a problem, but when I say “explain it like I am five”, I really mean that.
As noted, I successfully set up NoMachine on one of my two machines that I am trying to remote into. It works GREAT! But it’s the second computer that is giving me problems.
I recognize all of the words of ” Can you try to forward the port on the router manually” but I don’t actually understand the HOW of it. When I follow your “How to connect link” I see an instruction there of
*****
If you using NoMachine (free), edit the server configuration file (namely server.cfg) and set:
EnableUPnP NX for users connecting with the NX protocol
Then restart NoMachine.
*****
But what on earth does “set” mean in this context? “EnableUPnP NX” does NOT have a “#” in front of it in the server.cfg file, so that makes it “set”? Is that right? (Honestly: I don’t know!) It *looks* right to me (on BOTH computers, too)
[I’m not even truly sure which way we’re using “client” and “server” here — the server is the computer that is trying to initiate the contact, and the client is the computer you’re trying to log in to, correct? Because the log I sent *was* from the initiating computer, not the “client”]
As I noted, the link Kroy mentioned to find the IP didn’t result in a “IPv4” result of “10.1.10.10:24564” that NoMachine on the remote computer told me was the IP — it gave me a “IPv6” result of “2603:3024:1e02:c2f0:8d60:74d0:393f:afab”. But I don’t know what I am meant to be doing with that?
Basically: not sure what my next step is here.
Hi,
I did forward the logs to the email address listed above by Bilbotine.
As for Kroy’s response: I’m just a fairly dumb user, so I’m really not sure about most of the terminology that’s being used here (and even looking these terms up still isn’t precisely clear)… but AH-HA! using that IP finding link above it appears that the IP for that computer is a “IPv6” and not “IPv4”. (I have noted the long long string, for later)
What, exactly, I need to do with this information isn’t clear to me, however?
Can someone explain it like I am five?