Question
FlashCom + 2003 server + write errors on networked-filesystems?
Hi all,
We are using FCS v2. We have been successfully writing log files and recording streams to both local disk and filesystems from networked devices (SMB mounted shares, NFS shares etc) for years. But since setting up FCS on server 2003, we *cannot* successfully record to any drive that is mounted via the network (SMB, NFS etc).
The server itself can use/access the network drive just FINE! All copy/open/delete/etc operations work just fine, from the cmdline and also within Windows itself.
It seems the only app that CANNOT write to the networked drive is FCS2! Has anyone experienced anything like this with W2K3 server? We can reproduce this error with 100% accuracy. Note that as soon as I change the appropriate tag in the XML config files to point to a local disk, everything works just fine.
Its not a show-stopper for us, but it means we have to have some kind of batch job that will offload the recorded content to aforementioned network drives in a lazy-update manner (not ideal).
I would appreciate any and all comments.
Thanks so much,
Rick T.

We are using FCS v2. We have been successfully writing log files and recording streams to both local disk and filesystems from networked devices (SMB mounted shares, NFS shares etc) for years. But since setting up FCS on server 2003, we *cannot* successfully record to any drive that is mounted via the network (SMB, NFS etc).
The server itself can use/access the network drive just FINE! All copy/open/delete/etc operations work just fine, from the cmdline and also within Windows itself.
It seems the only app that CANNOT write to the networked drive is FCS2! Has anyone experienced anything like this with W2K3 server? We can reproduce this error with 100% accuracy. Note that as soon as I change the appropriate tag in the XML config files to point to a local disk, everything works just fine.
Its not a show-stopper for us, but it means we have to have some kind of batch job that will offload the recorded content to aforementioned network drives in a lazy-update manner (not ideal).
I would appreciate any and all comments.
Thanks so much,
Rick T.
