kdv666

[kdv666]

That’s very odd.  I did tick that box.  I just opened up the settings, and it’s still sitting there ticked.  ???

I’ll try again with the client sophia.

I’ll leave it hung for a shorter time to see if it produces smaller log files, and try again with both sophia and kath

 

 

Attachments:

1. sophialogs-1.zip
2. kathlogs.zip

[kdv666]

Ahh, it exceeds the allowed size, it would seem.  I’ll see if I can split it up.

 

[kdv666]

Hello,

Ok, just to be clear.  My desktop where I run the client, is sophia(192.168.4.41).  The problem machine is kath(192.168.4.32).

I did a nxserver –logrotate first to keep the reports recent.

I include the requested screenshots and logs.

Please note that I left the machine hung at the second screenshot for about 2-3 minutes.  In that time, the nxserver.log file grew from 93 bytes to something over 13MiB.

Regards

 

Attachments:

1. 

   sophia_ss1.png
   

2. 

   sophia_ss2.png
   

1. sophialogs.zip

[kdv666]

Hi, and thanks for your reply.  It’s appreciated!

Yes, 8.4.2 on all machines.  It’s the latest one on the website, and checking for updates says no newer verstions.

The desktop is X, or to be more specific, Xorg.  FWIW, the running command is:

/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

I can connect from the problem machine (kath, 192.168.4.32) to others without problem, e.g. marie(192.168.4.35), but not vice-versa.

The other thread was

https://forums.nomachine.com/topic/cant-connect-to-the-nomachine-server-after-moving-to-a-new-server

As I said, the solution given there didn’t help me.

And just to add something new since I originally posted:

I reset the link to kath from my main machine.  When I tried connecting to kath again, it did the normal things including name/pw, but then it indicated it was asking permission on kath to complete the link.

However: The question didn’t appear on kath.  It appeared on a different machine on my network, maggie (192.168.4.33).

So weird!

 

[kdv666]

Yup.  The “systemctl stop lightdm” followed by a server restart worked like a charm.

For good measure, I added a “systemctl disable” to the mix so I wouldn’t run into the same problem after the next reboot.

Cheers!

 

[kdv666]

Thank you very much!  I was hoping to be pointed in the right direction, and you have done so.  I really appreciate your taking the trouble to get back to me so quickly!

Not sure why that article didn’t come up when I searched the knowledgebase for  “headless”.  Hopefully, your reply may help others in the future.

 

[Author]

Posts