Does anyone have experience of accessing files on a windows network file share?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2017 11:29 AM
The file writer snap is not cooperating, it’s says it’s succeeding but doesn’t appear to do anything.
Currently have an account mapped with read/write permissions, using fille:/// anything else generates an error or creates a file with a weird name on the plex.
any help much appreciated.
Yours,
Adrian
- Labels:
-
General Information

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2017 04:29 AM
Hi Adrian,
Are you using file:///
to access the share, or smb:///
?
Cheers
Nic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2017 04:49 AM
Nearly….
Trying for some reason to use file:///<file:///\> to access the network share z://, converting to SMB now.
Yours,
Adrian

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2017 11:58 AM
@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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2017 07:10 AM
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?
