Forum Replies Created
-
AuthorPosts
-
January 4, 2024 at 19:05 in reply to: Version 8.10.1 NM services will not start until after local login on remote machine #46598dje666Participant
Dear Team,
Yes, auto login for a nominated user is the solution I’m using for now.
ta,
DJE666
dje666ParticipantThe update to v8.10.1 has improved matters for me. I shall post further updates if the behaviour reappears.
ttfn,
dje666
dje666ParticipantHello BritGirl,
Can you confirm if the NoMachine icon that appears on my remote Linux desktop (top right), is an indication of the server being active or an indication that the Linux box is being accessed remotely?
If I access the Linux machine directly the NoMachine server GUI reports that the NM server is active, but the NM icon can take a few minutes to appear, if it appears at all.
TTFN,
dje666
dje666ParticipantHello 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
dje666ParticipantHi 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
-
AuthorPosts