cRIO Path Windows Compatibility

[falafes]

Hello,

I have built an application on cRIO which receives measurements and logs them in cRIO's SSD.

I would like to have them saved on a Windows machine instead of the cRIO, but whenever I enter the path the whole thing returns an error and I cannot see any files in the specified path. The folder has been shared with the network and every device on the network has access to it, but for some reason cRIO doesn't like it. 

The path I used was //IPaddress/Data/cRIO Data

Any modifications I can do to get it to work? Is this even possible since cRIO is linux based?

Thanks

[rolfk]

It is with SAMBA but Unix works differently. The Unix filesystem only has one single root, not a UNC, Desktop, Disk Volumes and Windows NT kernel root that all use their own naming conventions.

So you "mount" the SAMBA server somewhere in your file system and then access it simply in the filesystem such as /network/myserver/share/dirs

[falafes]

Okay so I tried mounting a folder I created in cRIO to the network folder on the windows machine.

I followed the steps in here https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kKgxSAE&l=en-CA

It replies with Host is Down.

What is the issue here? I tried saying vers=1.0 at the end of the command, i also tried -m SMB2 at the end of the command but neither argument was recognized.

[rolfk]

Windows 10 by default does not install support for SMBv1 anymore. This is because SMBv1 has known vulnerabilities that can be exploited.

You need to configure SAMBA on the Unix side to use SMB2 in order to be able to connect to a Windows share hosted on a modern Windows computer.

https://www.cyberciti.biz/faq/how-to-configure-samba-to-use-smbv2-and-disable-smbv1-on-linux-or-unix...

And you did not mention which LabVIEW version you use but you might have to update to LabVIEW 2020 Real-time to have support for SMBv2 and v3 available in the kernel as indicated in this thread: https://forums.ni.com/t5/Real-Time-Measurement-and/NI-Linux-RT-Mounting-a-network-share-with-SMB-gt-...

Alternative would be to rebuild the kernel for your LabVIEW version with the cifs configured to contain SMBv2 and v3 but that is probably a lot more hassle than upgrading to LabVIEW 2020 unless you are a Linux kernel guru.