Forum / NoMachine for Mac / Windows client disconnects from Ventura server
- This topic has 15 replies, 5 voices, and was last updated 3 weeks, 6 days ago by fra81.
November 17, 2022 at 16:51 #41504
I have a Mac running Ventura and the latest NoMachine server and am having issues when connecting to it from a Windows machine using the latest NoMachine client. When connecting it initially looks like it’s working (i.e., I see the screen), but I can’t interact using the mouse or keyboard then it disconnects after about 30 seconds. Connecting from another Mac using the latest NoMachine client works properly.
I see the following in the Mac’s nxserver.log when the Windows client connection fails:
2420 2420 2022-11-17 09:26:25 897.355 NXSERVER Connected from remote machine ‘192.168.3.32’ using protocol ‘NX’.
Info: Handler started with pid 2420 on Thu Nov 17 09:26:25 2022.
Info: Handling connection from 192.168.3.32 port 57716 on Thu Nov 17 09:26:25 2022.
2420 2420 2022-11-17 09:26:28 878.523 NXSERVER User ‘admin’ logged in from ‘192.168.3.32’ using authentication method NX-password.
Info: Connection from 192.168.3.32 port 57716 closed on Thu Nov 17 09:26:29 2022.
Info: Handler with pid 2420 terminated on Thu Nov 17 09:26:29 2022.
2420 2420 2022-11-17 09:27:22 440.499 NXSERVER ERROR! Received error message from node ‘:’, ‘Session is in ‘Suspended’ status for too long.’.
2420 2420 2022-11-17 09:27:22 508.266 NXSERVER ERROR! Status ‘Failed’ for ‘started’ session ‘187AE96C3DA3AE923B90CBBE4B0576EC’.
2420 2420 2022-11-17 09:27:22 519.325 NXSERVER User ‘admin’ from ‘192.168.3.32’ logged out.
2420 2420 2022-11-17 09:27:22 519.849 NXSERVER Remote machine ‘192.168.3.32’ disconnected.November 17, 2022 at 18:30 #41518
I should’ve also noted that the Windows client has no problem connecting to other Mac servers running on macOS(es) other than Ventura (13.0.1).November 21, 2022 at 08:53 #41556
Doug, the logs you wanted to send us did not attach. Please send any attachments to forum[at]nomachine[dot]com. Ideally, we would need both player and server-side logs.
Check here for details:November 21, 2022 at 16:18 #41559
Please find the attached client and server side logs.
Attachments:November 28, 2022 at 10:20 #41683
Hi thanks for those. After analysis of the logs, it seems no connection is occurring. At this point we need to look at the player side logs. So you should tick the box “Don’t delete log files on exit” in the Player settings (Security), reproduce and then share the .nx folder with us. Thanks!November 28, 2022 at 15:52 #41691
Please find the attached zip file containing the player’s .nx directory per your request.
Also, it should be noted that when connecting it initially looks like it’s working (i.e., I see the screen), but I can’t interact using the mouse or keyboard and then the player disconnects after about 30 seconds.
Attachments:December 8, 2022 at 14:53 #41883MasterOfusParticipant
We have the same problem with the Windows client connecting to a NoMachine server on Ventura. It is working great with other versions of MacOSX.
I upgraded a Mac mini 12.0 to the latest Ventura.
– First connection working great. The login screen shows up and I can enter the desktop interface.
– When the user disconnects his apple session (on the Mac mini) there is no login\pass prompt but only the wallpaper showing up.
– If the user closes the Client NoMachine Windows and tries to reconnect to the Mac mini, Mac Mini refuse the connection with this message:
“Error is 108: Connection reset by peers”.
I have to force shutdown the Mac mini. Then the client can do a first connection, the same process apply.
Any suggestion ?December 9, 2022 at 16:39 #41916
To Doug, the logs of the client side do not show the issue (no correspondence to the server side logs). We need to receive the correct player side logs. What I suggest you do is make sure that “Don’t delete old log file in the player” checbox is enabled, reproduce the problem and send both server and player logs again. Thanks.
To MasterOfus, your issue seems to be a different issue which we are investigating and will come back to you soon.December 12, 2022 at 17:26 #41948
I don’t know why the logs weren’t correct, but I’ve cleared out everything, reproduced the problem, and collected the logs and attached them. Thanks for taking a look.
Attachments:December 13, 2022 at 09:34 #41967
hi Doug, send the server logs directly to forum[at]nomachine[dot]com.December 13, 2022 at 14:02 #41977
I e-mailed the logs and have also combined them into one zip file and attached it.January 6, 2023 at 16:55 #42344raleighr3Participant
Any updates on this issue?January 9, 2023 at 17:46 #42385
To Doug, we’re analyzing all the information you sent us and will come back to you soon.
To MasterOfus, your issue could be a different issue and so we will need the full set of logs from the Mac server. Check here for details: https://kb.nomachine.com/DT07S00244 and submit to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.
To raleighr3, the logs from your Mac server would also be useful as per my request to MasterOfus. Thanks everyone.January 9, 2023 at 22:11 #42392MasterOfusParticipant
I connected the mac, then disconnected (logoff), restarted the mac so I could reconnect and take the logs.
I took the client logs when I couldn’t reconnect after logoff.
I used the option “SessionLogClean 0”. Maybe the server logs get reset when it restart ?January 25, 2023 at 12:31 #42705
MasterOfus, we need the server logs, not just the player side logs.
So, on the server
$ sudo /etc/NX/nxserver --debug --enable allfrom a terminal
on the player side
Settings – security – Don’t delete log files on exit.
Reproduce the problem.
Then on the server
$ sudo /etc/NX/nxserver --debug --collect
Zip up everything and send as attachments to forum[at]nomachine[dot]com.
You must be logged in to reply to this topic.