- This topic has 4 replies, 3 voices, and was last updated 6 years, 3 months ago by
.
-
Posts
-
I have NoMachine Workstation (licensed) running inside a Docker container (running as a privileged container). Inside the container, I have Ubuntu 18.04. No settings were changed from a stock install of NoMachine Workstation, as downloaded yesterday. With Windows, I am able to connect and everything (except audio) works fine. The node session log with Windows shows the following:
NXAGENT – Version 6.2.4
Copyright (C) 2001, 2018 NoMachine.
See http://www.nomachine.com/ for more information.
Session: Starting session at Thu Jul 12 14:49:24 2018.
Info: Agent running with pid 4985.
Info: Slave server running with pid 5001.
Info: Display running with pid 5002.
Info: Listening to slave connections on port 12001.
Info: Audio server started with pid 5009.
Info: Audio client started with pid 5010.
Session: Session started at Thu Jul 12 14:49:25 2018.
Info: Encoder running with pid 5016.
Info: Connection with remote peer completed.
Info: Using link parameters 8/1/8000/25/200.
Info: Using cache parameters 16384KB/16384KB/16384KB.
Info: Using pack method dynamic with session rootless.
Info: Using product LWSN/lid id removed
Info: Forwarding audio channels to the client devices.
Info: Transport running with pid 5183.
Info: Established display connection.
Info: Using image parameters 1/1.
Info: Accepted new connection to audio server.
Info: Accepted new connection to voice server.
Info: Audio server for NXAudioServerLightweightSessionID connected on Thu Jul 12 14:49:25 2018.
Info: Audio client for 5573F6EBC725A613EB299165814F5152 connected on Thu Jul 12 14:49:25 2018.
Info: Audio reader running with pid 5232.
x264 [warning]: frame MB size (400×135) > level limit (36864)
Session: Session reconnected at Thu Jul 12 14:49:27 2018.
Info: Using screen size 6400×2160.
Info: Forwarded new slave connection.
Info: Closed connection to slave server.
Info: Forwarded new slave connection.
Info: Closed connection to slave server.
Info: Forwarded new slave connection.
Info: Closed connection to slave server.
Info: Audio reader running with pid 5726.
When someone connects using a Mac however, we are getting a session log as follows:
Copyright (C) 2001, 2018 NoMachine.
See http://www.nomachine.com/ for more information.
Session: Starting session at Thu Jul 12 14:52:12 2018.
Info: Agent running with pid 5795.
Info: Slave server running with pid 5811.
Info: Display running with pid 5812.
Info: Listening to slave connections on port 12002.
Info: Audio server started with pid 5819.
Info: Audio client started with pid 5820.
Session: Session started at Thu Jul 12 14:52:12 2018.
Info: Encoder running with pid 5826.
Info: Connection with remote peer completed.
Info: Using link parameters 5/1/3200/25/200.
Info: Using cache parameters 16384KB/16384KB/16384KB.
Info: Using pack method dynamic with session rootless.
Info: Using product LWSN/lic id removed.
Info: Forwarding audio channels to the client devices.
Info: Transport running with pid 5994.
5795 5994 14:52:13 798.349 ClientChannel/ChannelBase: WARNING! Finishing channel for FD#32 with remote congestion.
Session: Reconnection failed at Thu Jul 12 14:52:13 2018.
Info: The session was closed before reaching an usable state.
Info: This can be due to the remote display refusing access to the client.
Info: Please check the authorization provided by your application.
Session: Session disconnected at Thu Jul 12 14:52:13 2018.
I am not able to find any other information in the logs that would be relevant to debugging this. It seems to be somehow something on the remote side that is triggering this. The only thing I can suspect is that something about the audio setup is triggering a problem on the mac side, but doesn’t cause a problem on the Windows side.
Any thoughts? Thanks!
Hi, so everything is working fine when connecting from Windows, but not from Mac. From what you copied from the logs it’s not possible to say what the cause is of not being able to reconnect.
Did you follow the instructions for setting up Docker first?
https://www.nomachine.com/DT10O00161If you’re using a subscription of Workstation, have you considered opening a support enquiry in your customer area from where you downloaded the software? They’d also need to see logs.
I haven’t opened a ticket yet, I was looking for any obvious issues first. I worked through the docker stuff, but it doesn’t exactly apply to our situation, so it isn’t quite as documented. That said, since it works for Windows, I wouldn’t expect that it would break on a Mac. The most notable part of the logs is this:
Info: The session was closed before reaching an usable state.Info: This can be due to the remote display refusing access to the client.This to me says that there is something going on with the client side that may be impacting the display of the application. I don’t have a Mac to test this with, this is one of the users having the issue, but was hoping someone else had encountered this and resolved it. Google didn’t help with this one. 🙁
Update: The issue only appears to happen when using floating windows on Mac. If a full desktop is used, then the problem goes away. This is also in the context of using SSH as the protocol, not the NX protocol, so this may also be related. As the desktop works, and we have few mac users, this effectively resolves our issue.
Thanks for the update. Probably you need to install XQuartz on the Mac client host. Start the X11 application under the Utilities folder and it will point you to the download page.
Should it not work, something else is going bad on the Mac client side. If you cannot get the client log, would you provide more info about that? I’ll try to reproduce on my own. I’d need to know:
- The Mac OS version
- If problem occurs with some specific application run in floating window mode
This topic was marked as solved, you can't post.