Following advice from Use-IP I decided to upgrade three of my cameras from V5.2.X to V5.4.41 using iVMS. First two cameras (2132 & 2332) upgraded perfectly and the third upgrade seemed to go well. However I noticed that whilst the other two cameras retained their IP address and other settings the 2632F lost all settings and came back with a new IP address of 192.168.1.64, presumably via my DHCP server. I tried accessing this IP address from my browser but the connection was refused. I then went into SADP which located the camera and showed it as 'inactive'. Back in iVMS (latest version) I was able to activate the camera and headed off to the Configuration tab to correct the IP address and reset the date/time format etc.
However I found that none of my changes would be accepted and the error message HCNETSDK.DLL {29} appeared. I tried powering off/on the camera but on doing so it returned to factory settings. I had to re-activate the camera but the same thing happened when trying to configure it. I notice some changes (date/time) produced the error message but were accepted and lost on reboot. I then tried:
1. Factory reset via iVMS
2. Upgrade f/w to 5.4.5
3. Downgrade f/w to 5.4.0
4. Downgrade to 5.3.0 - prohibited
5. Factory reset using button inside camera
6. Used TFTP to force f/w update - did not respond to the server at 192.0.0.128
7. Used ONVIF device manager - returns "No connection because the target machine actively refused it 192.168.1.64:80"
The camera is still un-configurable although video displays perfectly. I could probably live with the settings however the one problem is that Milestone was looking for a different IP address for the camera so is not recording. I tried adding it as a new device and although Milestone finds the camera at its new IP address it cannot connect (comes back with 'invalid password or user name') presumably because it is actively refusing connections. So the camera is sending data but not prepared to accept data. Camera ID is DS-2CD2632F-I20131111CCWR440444972
Any thoughts on kicking it back to life or should I just give up and order a replacement?
Thanks
David
NB: Is the IP address .64 of significance as a) it is not the next available address in the DHCP list and b) it is the IP address that TFTP would have used for it i.e. 192.0.0.64
However I found that none of my changes would be accepted and the error message HCNETSDK.DLL {29} appeared. I tried powering off/on the camera but on doing so it returned to factory settings. I had to re-activate the camera but the same thing happened when trying to configure it. I notice some changes (date/time) produced the error message but were accepted and lost on reboot. I then tried:
1. Factory reset via iVMS
2. Upgrade f/w to 5.4.5
3. Downgrade f/w to 5.4.0
4. Downgrade to 5.3.0 - prohibited
5. Factory reset using button inside camera
6. Used TFTP to force f/w update - did not respond to the server at 192.0.0.128
7. Used ONVIF device manager - returns "No connection because the target machine actively refused it 192.168.1.64:80"
The camera is still un-configurable although video displays perfectly. I could probably live with the settings however the one problem is that Milestone was looking for a different IP address for the camera so is not recording. I tried adding it as a new device and although Milestone finds the camera at its new IP address it cannot connect (comes back with 'invalid password or user name') presumably because it is actively refusing connections. So the camera is sending data but not prepared to accept data. Camera ID is DS-2CD2632F-I20131111CCWR440444972
Any thoughts on kicking it back to life or should I just give up and order a replacement?
Thanks
David
NB: Is the IP address .64 of significance as a) it is not the next available address in the DHCP list and b) it is the IP address that TFTP would have used for it i.e. 192.0.0.64
Last edited: