- This topic has 5 replies, 2 voices, and was last updated 2 years, 1 month ago by
.
-
Posts
-
Dear Team,
I have NoMachine free versions running on a Linux Server, accessed by Win10 and Linux clients, with port-forwarding setup ok on my router. When I log in from a client machine I have to use the Public IP address of my home system, and since this changes I want to use the DDNS service offered by the TPLink router.
I can log in using the Public IP address, but the DDNS address is not working.
Public address like 12.34.234.45 is ok.
DDNS address like bob@[DOMAIN].com fails for NoMachine, but is ok for other remote systems like [removed]
Can you offer a solution?
Regards,
dje666
A NoMachine connection uses either the hostname/domain name or the IP address. You cannot use an email address in the host field.
I understand that if you use the IP address, you can connect with NoMachine? Or do you have problems there? If so, what error are you seeing?
With the other product are you connecting to an email address?
What kind of model router do you have?
Hi BritGirl
Thanks for the reply. Iām not using an email address, rather a standard SSH login format, user@ipaddress . This format works for the [removed] system.
In this instance the Public IP address is substituted for the DDNS address that the TP-Link service gives me.
Can you provide an example of the Host filled be completed using a DDNS address rather than a Public IP address?
Regards,
dje666
Can you provide an example of the Host filled be completed using a DDNS address rather than a Public IP address?
Maybe you should show us how you are configuring your NoMachine connection. Please submit a screenshot so we can see.
Hello Britgirl,
This issue is now resolved. It turns out that my DDNS web address was blocked by over enthusiastic PC protection SW. With this site added to a list of permitted addresses, the NoMachine system is up and working brilliantly… š
Thanks for your support.
dje666
This topic was marked as solved, you can't post.