- This topic has 9 replies, 3 voices, and was last updated 6 years, 10 months ago by
.
-
Posts
-
I enable disk forwarding and trying to connect disk D (my win10 workstation) to my NoMachine VDS (CentOS6).
I get exclamation mark and error: “Failed to connect the disk D:/.”.Does not matter what option I choose (private/public, any disk, any location).
I also disable firewall on VDS and restart Win10 – no luck.How to fix that ?
Client and server versions are the same (latest 6.0.66).
VDS: openVZ, CentOS release 6.9 (Final), Linux *** 2.6.32-042stab126.2 #1 SMP Wed Dec 6 18:08:29 MSK 2017 x86_64 x86_64 x86_64 GNU/LinuxAttachments:
Hello unlim
We would need some more information from you to resolve this issue.
First of all you can check if there are any errors in Session log on server side.
From my understanding you are connecting from Win 10 to Centos 6, which mean server is Centos.
Session logs are in path:
$ /usr/NX/var/log/node/”generated folder”/session.log
That “generated folder” is created each time you create session and deleted after you close it (removing is set up by default, You can change that in settings).
Example path:
$ /usr/NX/var/log/node/C-Nomachine-Lenovo-XXX-XX-1002-B20D597696B309D5712A9A3F8C6B8DBE/session
Best way would be if you connect to that Centos, recreate issue and check session log in most recent folder.If there will be nothing helpful in there, you can follow this article (its common issue):
Enabling disk serviceAlso article which explain how to collect logs:
How to collect logs./mushroom
That’s only I got in session log, when connects the disk:
==> /usr/NX/var/log/node/****/session <==
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: Forwarded new slave connection.
Info: Accepted new connection to filesystem server.
Info: Closed connection to slave server.
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.Hello unlim
We tried to reproduce the issue in our labs, but everything is working.
Few more questions, so we can work this out:
Did you check other session logs in folder /usr/NX/var/log/node/ ?
Can you paste here output of that command:
$ sudo df
Also do you have full access to that Desktop folder, like creating folders, changing names?
Did you try to follow instructions in article about enabling disks on Centos, which we provided before?
One more thing is to switch Selinux off for testing only, you can do it with that command:
$ sudo setenforce 0
Enabling it again with:
$ sudo setenforce 1If issue will still occur then could you send us server logs from active session?
In my previous answer i send you link how to do it./mushroom
>> Did you check other session logs in folder /usr/NX/var/log/node/
Yes. I look into all logs:
tail -f /usr/NX/var/log/node/*/session>> Can you paste here output of that command:
>> $ sudo df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/simfs 199229440 112007320 87222120 57% /
none 16349940 4 16349936 1% /dev
none 16349940 5556 16344384 1% /dev/shm>> Did you try to follow instructions in article about enabling disks on Centos, which we provided before?
Yes.# yum install fuse dkms dkms-fuse
…
Package fuse-2.8.3-5.el6.x86_64 already installed and latest version
Package dkms-2.4.0-1.20170926git959bd74.el6.noarch already installed and latest version
No package dkms-fuse available.
Nothing to do
…>> One more thing is to switch Selinux off for testing only, you can do it with that command:
Yes – nothing changes:
# setenforce 0
setenforce: SELinux is disabled
# setenforce 1
setenforce: SELinux is disabledLogs just sent to forum[at]nomachine[dot]com.
Ok, we got the logs.
There are some errors in there but nothing about disks.
Do you have possibility to connect from other machine?
Also can you try reverse mounting:
1) Connect from Windows to Centos, and export disk from Centos to Windows.
2) Connect from Centos to Windows, and import disk from Windows to Centos (so mounting would be on Centos side).Some helpful logs can be on client side also.
To check player logs on windows go into:
$ C:/Users/username/.nx/R-"numbers"/session
And try to reproduce the issue.Do you have our official NoMachine server installed or some other derivative?
/mushroom
Unfortunately, I can’t test other conf.
I have win10 (local) and CentOS6 (VDS).Yes, I use NX client and server both 6.0.66.
"C:/Users/username/.nx/R-"numbers"/session" log attached.
Thanks for the additional info. We still haven’t been able to reproduce the problem replicating your set-up and configuration. It might be a configuration problem of your environment.
What we can do is send you debug binary files which you can install, then reproduce error and submit a full set of logs.
To do that, reply here or submit an email to forum[at]nomachine[com] notifying us that you wish to receive this package. We will send you instructions as well.
/mushroom
As a follow up I suggest you read the following article:
What should I do if I have a problem with Linux or my desktop environment?
https://www.nomachine.com/AR11K00740To be able to debug your system thoroughly, it would be better to do that under the provisions of a support contract. The forums are indeed a means to request assistance, generally used by those installing the free version or evaluation software and need help with basic configuration. But issues which appear to be related more to your environment and not the NoMachine software (since we are not able to produce the problem using your set-up and distro out-of-the-box from the provider) would need quite a deep analysis. If you are interested in taking this investigation further, please contact our team via the website.
This topic was marked as solved, you can't post.