- This topic has 5 replies, 3 voices, and was last updated 9 years, 11 months ago by
.
-
Posts
-
Client: Mac OS X 10.9.5 running latest version of NX (4.3.30)
Server: CentOS 5.10 64-bit
User attempts to connect to Linux server from Macbook Pro. Initial connection is successful after entering password. User selects Gnome and hits Connect. Connection drops with error “The connection with the server was lost. Error is 5: Input/Output error”.
Other users are able to successfully connect to this same host. I believe the problem lies within the user’s home directory on the server side. I’ve renamed user’s .nx directory, forcing NoMachine to recreate it – same issue. User was using an older version of the NoMachine client and had him update to the latest for Mac. Same issue, except application sometimes crashes. Requested user create new .cshrc in home directory on Linux server. Same issue. We have our users’ home under /users/<username> mapped via NFS across the entire infrastructure. Each blade is randomly selected to handle the task of authentication, but the problem happens across all blades – which would make sense since his home directory is exactly the same across them all.
Attached are the logs from the NX session. This has been happening now for a few weeks. Would like help pinpointing which files within the user’s home directory could be checked that might be causing these issues.
Unfortunately logs from client side are not enough to clarify the issue. Please gather a complete set of logs as explained in https://www.nomachine.com/AR07K00677. If you prefer, you can send logs to forum[at]nomachine[dot]com. You can also check if there are any core files in the user’s home on server side.
They could have been too big for the forums to accept. Send them to the email referenced above and make sure you included the topic title in your subject 😉
I’ve emailed that address. Thanks. Any particular reason why the size limitation for attachments is so incredibly small?
@loadedmind, the logs show you are using a derivative of NX which we are not responsible for. I suggest you contact the appropriate project forum.
This topic was marked as solved, you can't post.