Forum / NoMachine for Windows / Local Windows drive sharing to remote Linux fails
Tagged: sharing issue windows
- This topic has 3 replies, 2 voices, and was last updated 6 days, 11 hours ago by kubaszym1.
March 16, 2023 at 12:11 #43433tcnParticipant
I am trying to diagnose an issue where I would like to share a local drive with my Linux workstation. The result is always the same, a gray swirl beside the drive and nothing gets mapped.
I enabled debug log for both server ans node. On the Linux machine, I have been able to identify the handshaking for the drive sharing. It looks fine.
However, on the Windows machine, even before I initiate the share, I get this error in the log:
DeviceServiceDisk: WARNING! Cannot open directory for reading. The reason is 87.
This error gets in the log multiple times when I initiate the share. There is no indication of what the directory name is and thus, I am stuck here.
What exactly is this directory? The drive does exist; the remote attach directory does exist …. I can’t figure it out.
tcnMarch 17, 2023 at 13:45 #43447kubaszym1Participant
Do you have access to the drive that you want to share? Error 87 is a WinAPI error that indicates invalid parameters. In this case it is probably the path of the directory. This directory can be drive name (like C:, when listing drives) or some folder name (creating/removing directories). NoMachine checks if the directory is empty. It can return failure if the user doesn’t have permissions to the given directory.
What are you trying to share? Is it a standard C or D disk or something else?
KubaMarch 17, 2023 at 17:39 #43459tcnParticipant
The drive is a simple drive, and yes I have access; it is X: in my case; but even C or E doesn’t work. But the error comes before I even start sharing which I find weird. It multiplies with I start trying.
tcnMarch 22, 2023 at 14:43 #43540kubaszym1Participant
Please check this directory: C:/ProgramData/NoMachine/var/log. If there is a file called nxtrace.log, it means that one of NoMachine’s processes crashed. The information from nxtrace.log would be very useful for further investigation.
This warning multiplies because NoMachine monitors drives’ list in a loop – it probably occurs in each iteration. You can also check nxfs.log which is located on your Linux server (because you share from a Windows to a Linux) in ~/.nx/nxdevice/D-<display>-<session-ID>/disk/. There might be some errors from our sshfs client. This process starts when you click to share a drive.
If something crashes on Linux server, core files will be located in /var/crash.
Can you share a drive from the Linux server to your Windows client machine? If you can’t do that as well, you can look for nxfs errors in C:/Users/<username>/.nx/nxdevice/D-<display>-<session-ID>/disk/nxfs.log
I hope this will help. Let me know if you discover new information.
You must be logged in to reply to this topic.