Local storage problems

[JimSchuuz]

I have an IP4M-1051 on v. 2.620...3.R, 2019-12-18. I am trying to use a NAS for storage, but this is not working. The network storage does not receive any files for any triggering events. Since there is no place to enter any USER/PASSWORD combination, I have gone so far as to completely remove any authentication from the storage destination share, and it still does not work. I have tested connecting and writing to the NAS share from multiple devices without authentication, so I know this is not the issue.

Can you tell me what protocol this is using for file transmission (sharing, retrieval, etc.)? I would assume it's SMB, but if so I need the version number since they aren't all compatible.

Also, are there any plans for a newer revision of the firmware, maybe one that will include authentication parameters for the NAS storage option?

I actually have multiple installations of this model camera that are in remote locations where it's not practical to install a dedicated DVR for just one camera, and 128 GB of SD storage just isn't enough space. I could use the FTP option, but this requires a remote server to be installed, and that would also require a functioning Internet connection at all times, not to mention the bandwidth implications of transmitting 100 GB every 2 days.

[longedge]

I have had very limited success saving to my NAS in the past using the "NAS" destination option. I found it so hit and miss that I have given up on it. You don't say what make your NAS is, mine is a WD MyCloudMirror and the connection was by Network File System (NFS).

I think people using Synology devices have done so quite successfully. I don't know anything about the Synology system but I believe that this works by way of an app and not simply by use of an implemented file system.

My NAS also supports FTP connections which I've also tried but with similar patchy results.

When you have been trying to set it up, have you had a success result when testing the setup?

[JimSchuuz]

Thanks for your response. I've had no success. Unfortunately, the cameras' interface doesn't have a "test" option with either a "success" or "fail" result like the email/SMTP setup has. In my opinion, it needs this.

I've tested this with a Buffalo NAS (NFS3) and a Windows (SMB2) share. I prefer a Windows share because there is a Windows workstation in each remote office with plenty of available drive space. I would prefer to not have to incur the expense of a Synology NAS in each location. If I did that, I may as well just install an NVR/DVR locally instead.

If this requires NFS or SMB1, then I can enable this. But I don't want to enable it if it's using SMB2 and there are other reasons why it won't connect. The installation manual isn't very clear explaining multiple things, and this is one of them. Does it need a name instead of an IP address? Does it need a port specified? What's the proper syntax for the server and "folder" name? Knowing this information would go a long way towards troubleshooting. I suppose I could also install an FTP daemon on a Windows workstation as well, but I would really rather the NAS function be working properly before going into bigger changes than are needed.

[longedge]

Well my experience is limited to the two types of camera in my sig. The webui/setup/storage/destination tab looked like this, enabled of course. N.B. you must set and save the storage path first before entering the NAS details -

storage.jpg (26.54 KiB) Viewed 1359 times

One thing that caught me out was that I had to add the " /nfs/ " to the remote directory field to make it work, but that of course is talking about my WD.

I don't know of any implementation of SMB for this purpose. Sorry I can't be of more help

p.s. - The test button does not appear until you have set "NAS" in the path tab and saved it and then entered the access details in the NAS tab. In my screenshot it doesn't appear because the option isn't enabled.

[JimSchuuz]

Excellent, this was a tremendous help. I'll change the syntax of the "Remote Directory" field to include a leading '/' and test it again on the NFS share on the Buffalo NAS. If it still doesn't work, I'll create a newer NFS4 share and test that. If it works, I can still create an NFS share on a Windows machine and test further. If it doesn't work, I just might have to revert to a local FTP solution.

Your help is definitely appreciated!