We have a Windows environment, and we have IFS Connect file senders pointing to network shares.

The IFS Connect file sender uses Java or UNIX style slashes, where they go forward instead of backward, even on a Windows extended server.

//some_server/some_share

By default, the IFS middleware runs as the Windows SYSTEM account. That means if your server is SOMESERVER, you need to grant access to the SOMESERVER$ Computer principal in order for IFS to have access to write to the network share. (Don't forget to grant both the share and the folder.)

I also learned that the IFS Connect file sender will want to write a temp folder one level higher, so your grants will need to extend one folder upward to make that work.

EDIT: I apologize; I didn't see this was in the DocMan group when I posted my response.