I encountered an issues transferring files using the X-NET database editor after a system I maintain was upgraded to Linux 2023 Q2 image with LV 2021 support on a PXI controller that was running Pharlap. After digging in further I realized that I could not longer map the cRIO file system using WebDav using this approach:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YGytCAG&l=en-US
Generally, this process is easy. I have verified that WebDav 21.x is installed on the target and is listed in MAX under the software target resources. I have tried re-installing the WebDav service. The same behavior occurs on multiple Windows 10 PCs with the firewall disabled. I have a tried a client that supports Secure Webdav, not knowing if windows automatically handles ports changes from a HTTP: and HTTPS: webdav instance.
I'm out of ideas. I've been trying to determine if the process is running logged into the Console with admin rights in Putty. Has anyone else had issues with Webdav after upgrading a Linux image on a PXI RT controller? Was the RT Linux console helpful in troubleshooting the issue.
I have contacted support and they have verified an issue with X-NET with the current image:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kIKuSAM&l=en-US
They have not been able to provide any insight why WebDav is no longer functional and the recommended X-NET functions cannot access the X-NET database on the target.
Thanks for your time.
