jonwestuk

Just tried it with another network share. The main process that seems to work is to do the following: 1. New partition, new folder 2. Right click the folder (ensure the name has no spaces special characters etc) and select properties 3. on the sharing tab, do not use the advanced button, use the 'Share' button 4. Add 'Everyone' to the list of users and make 'Everyone' read and write. 5. Next and close 6. Add the share to the camera and Voila!

Success - not sure why yet. This time I ignored the test button, which still fails and just saved the profile. The drive did then appear in the Storage screen and it did initialise!!!

Grr - another attempt tonight. Added my new share with one of my old v5.1 cameras and everything initialised and captured perfectly. Does it work with v5.2 NOPE!

Giving up now...! Just tried loads of different things. The new Camera has Firmware v5.2 whilst old cameras are on v5.12. I think that the firmware is the thing getting in the way at the moment, time to wait for HikVision to sort things out. Jon PS - if enough of us email HikVision then they might get the message to fix this! I sent a note of to them here: rma@hikvisionusa.com

I wasnt right in my last post. You need a separate drive partition, then a folder on that drive which is shared. There should be no other shares on the drive. This hasnt helped me with my issue but that needs some more investigations. Steps in Win 8. 1. Create and quick format partition 2. Create folder on that partition (one word, preferably lower case with no special characters or spaces) 3. Right click folder and open properties 4. On Sharing Tab click Advanced Sharing 5. Click 'Share this Folder' and check name 6. Click Permissions button 7. Add 'Everyone' and give full permissions. 8. Click 'Ok' on dialogs until you are back on folder properties. 9. Go to Security Tab 10. Edit security setting to give authenticated user, admins etc full permissions. 11. Restart 12. Try the share again. Hope that helps and works. It did for me on the first two shares, I now have no luck on the 3rd!

It turns out that for some reason (must be a windows problem) the test fails if the network share does not have its own drive partition. I managed to get it working by creating two new drive partitions one for each camera and then connecting to a network share dedicated to that partition. I have now just purchased a third camera and have the same issue again....I think I remember there being an issue if there were too many partitions. On my drive the new camera is the 4th partition. Does anyone have a clue as to why this issue may be occurring, and what I can do about it?

Interesting development. I was running various testing scenarios and discovered something interesting. Sharing a single drive to the camera resulted in the camera not initializing the drive. However if I share a folder within the drive then the camera seems to initialise properly. I now need to test that both cameras will record, but at least I am one step closer. I have no idea why the share does not work directly from a drive - Very odd.

Has anyone got the cameras working with FreeNFS? I have just tried linking to the NFS share but it is appearing offline? Tried opening the firewall etc. Any ideas?

Thanks for your advice. Which menu do you refer to? The camera menu does not have any option to mount it, however if I refresh the screen it appears that the share does mount. It just mounts with 0 GB free, which is incorrect as there is 50GB available.

Okay it seems like nobody has any idea what the issue could be with my set-up. Does anyone have any good ideas of how I could get this to work using NFS as an alternative? Can I use FreeNFS to set-up the camera? I understand that these cameras are more stable if the drive is dedicated to the camera, does this mean I would need to use two instances of FreeNFS?

Just tried again having done another factory reset and this time leaving the port configuration the same. No difference?

It is strange indeed, my server is used as a central storage device so it has lots of shares on it and I am no stranger to configuring such things. It does feel like the server is accepting the connection. If I change my username for example the server appears offline. So I feel like the config must be right. Maybe there is an issue on the server side that I am not thinking about? It should be a formatted partition that I am connecting to right? Here are some screenshots of my config, I am not sure there is anything particularly strange there. I should also note that I did a factory reset on both after loading the new firmware. The only changes thereafter were: - Password change for admin & new user created - All ports changed (Http, RTSP, HTTPS, Server) for forwarding purposes. Here is my config: Windows 8 Setup

Hi, I recently purchased two DS-2CD2032-I's and am trying to them up to use my Server (Windows 8 OS) as the storage device. I have managed to get reasonably far in that I upgraded the camera firmware to V5.1.2 (build 140116) and then configured the share so that it would be recognised in the storage management screen. When I look at the storage man screen it indicates of the 50GB I have allocated is available. When I format the device it immediately turns to complete and no files are written. The device then appears as uninitialized within the screen. On the Windows side I have allocated two new empty partitions, 50GB, each to the cameras and have created a share for each of them. On the permissions side the username that I am logging in with has been configured with full read, edit and modify rights. I feel like I must be missing something obvious as I cant find any other posts with a similar issues. Can anyone here help?