Forum Discussion
Nearly….
Trying for some reason to use file:///<file:///\> to access the network share z://, converting to SMB now.
Yours,
Adrian
@AdrianH, We interface with a file share on many of our pipelines using thing following environment and parameters:
- Groundplex Nodes running on Windows Server on AD Network
- Groundplex Nodes running as a Windows Service with specified logon credentials (not as System or Local Network)
- Above mentioned logon credentials have R/W access to both the network share and target file path
- The Snap’s file name value requires four "/"s in the protocol spec: “file:////{server}/{share}/{path}/{path}/{filename}”
The above works for us, so we have not tried actually mapping the file share to a drive letter.
- mukesh-neosalph8 years agoNew Contributor II
We are facing a similar issue where a network drive is not accessible on windows machine. Tried with above given suggestions but it doesn’t seem to work for us
“file:////{server}/{share}/{path}/{path}/{filename}”Anybody else facing the issue or have resolved it recently?
- nganapathiraju8 years agoFormer Employee
what @del mentioned is a straightforward configuration. Please work with the support to get it resolved.
- mukesh-neosalph8 years agoNew Contributor II
@nganapathiraju I have contacted Support and waiting for their help.
We are using Basic Auth as account type, if it has any correlation with the issue we are facing for network drive access on windows machine.