Issue with network storage on different IP ranges
Posted: Thu Nov 04, 2021 11:25 am
Hi folks,
I have a problem by working with network storages on different IP ranges.
I'am using FFAStrans as a farm. The FFAStrans directory and the global media cache is stored on this storage \\10.197.5.8\. I also encode files from that storage. Everything is working well from there.
Now, I have to encode files from another network storage which is reachable at this path: \\10.197.4.10\.
All computers who are working in my farm have full access to both storages (read and write), I use only UNC paths in my workflows and all instances of FFAStrans are running as service.
I'am also able to submit a file to the new workflow from the second storage but it leads always into an error, regardles from which computer in the farm the job will be processed. This error comes up:
The problem is that FFAStrans runs as service. When I disable the FFAStrans REST-API Service in Windows services on one computer in the farm, I'am able to submit files from both storages and the workflow will be processed completly at this computer. But running FFAStrans as application is no good solution for me at all.
Is there anything I can do to keep FFAStrans running as service and submit files from both storages?
Best regards
Michael
I have a problem by working with network storages on different IP ranges.
I'am using FFAStrans as a farm. The FFAStrans directory and the global media cache is stored on this storage \\10.197.5.8\. I also encode files from that storage. Everything is working well from there.
Now, I have to encode files from another network storage which is reachable at this path: \\10.197.4.10\.
All computers who are working in my farm have full access to both storages (read and write), I use only UNC paths in my workflows and all instances of FFAStrans are running as service.
I'am also able to submit a file to the new workflow from the second storage but it leads always into an error, regardles from which computer in the farm the job will be processed. This error comes up:
Here the log from the job:Validate: Permission denied
The problem is that FFAStrans runs as service. When I disable the FFAStrans REST-API Service in Windows services on one computer in the farm, I'am able to submit files from both storages and the workflow will be processed completly at this computer. But running FFAStrans as application is no good solution for me at all.
Is there anything I can do to keep FFAStrans running as service and submit files from both storages?
Best regards
Michael
