tng5737

You'll probably have problems with space - the apps in busybox are 'lite' versions which give some but not all functionality of the originals. As it is now, if you just changed the admin pwd from its default you'd be ok - at least your better off than having a fixed pwd like vizxv

I think that the files you see in /bin like telnet all point back to busybox

Geez, now you tell me!!!

Yes, that worked - the bit after 7ujMko0 is the current pwd. Furthermore, the userid and current password can be any existing userid. I think it must be a admin id to login though! It is good to know that you still have to know the password to can access and that it is not 'wide-open' thx

It was already installed on my camera.

Neither of those two pwd work on my HDW4300C (soft v2.210 build 2014-613)

yes it comes with its own driver and software. I'm looking at the Belkin Network USB hub F5L009 and the Belkin N1 MIMO wireless router. Supposedly this will make the remote usb device look just like it was plugged into the pc.

I have a Dahua NVR3216V which I am unable to upgrade using either USB or the ConfigTool methods. I have tried various bin files. Current firmware levels are soft.: 2.610.WI00.0 and web 2.1.7.72 with build date of 2012-12-18. My seller no longer has a contract with Dahua and is unable or unwilling to offer assistance. The NVR was re-branded as ESC-NVR3216V. I am able to Telnet into the nvr and look at the log "printf-xxxxxxxxxx.txt" files and I find that it appears to be failing the Vendor check in the install.lua the log does not tell me what the actual vendor value in the NVR is - just that it fails the check. I have a RS232 Serial interface on order so that I can diagnose this further. Has anyone else run into this issue? I guess it is possible that the seller changed the vendor code but how and where is it? More importantly WHY would you want to do this? Thanks in advance

I had a similar problem with one of my cams last night. the IR switch was constantly cutting in and out. I took it inside and the cam was fine - put it back out and it started up again. I checked the cam settings and switched it from WDR to BLC and the problem went away. I don't know why that fixed it, but it worked for me!

Deleted - after reading about subnets - there is no reason to do this.

I am curious what software pkg you used to make your diagram - well done!

I have traced the pinouts on both a HFW2100 and HFW3200 I do not know if Dahua always wires their cameras this way but here is what I have found. (see diagram) The Ethernet cable follows the 'A' standard not 'B' Pins 4&5 are tied together internally as are pins 7&8. I cannot vouch for about the actual wire functions (ie, Video, etc.. Accept the POE lines are pretty clear. Note that 4&5 are POE+ while 7&8 are POE- This is different than the diagrams shown above. I also found that there are four wires going to the +12v power jack I assume they double up to handle the larger currents. I have rebuilt the connectors on both cameras using this and they function ok I hope this helps.

The other thing to watch out for is dust. Attics are very dusty places with insulation etc... moving around. If you are THAT concerned just have snapshots of alerts sent to an email addr and have the mail server set to keep x days. That way if they steal the darn house you've still got a record of the perps!

I don't believe that the 888888 and 666666 and admin accounts can be deleted but you should be able to change their passwords. What do you mean by 'viewing online'? If you simply mean viewing from a browser within the confines of your home network - then simply do not FORWARD any of the ports in your router. If you have any account access which is admin then you can easily check to see what (if any) additional accounts may have been added. These can be removed if it concerns you. I always make sure that I have a backup admin account just in case... As was said earlier if you don't trust this guy then by all means get another installer who you DO trust and have him check things out!

It was 3800 If you do a port scan on the nvr you'll see that it is open It seems odd that the upgrade would work thru THAT port but not the default 37777 port but it DID work - saved me from having to TFTP

I finally got the upgrade to work by changing the port number in the ConfigTool to 3800. However the new firmware level also removed/changed the static password for root I used to access the device with telnet. Which I guess is a good thing from a security standpoint.

I own a dahua NVR-3216V The default device ID is 008. I had to place black electrical tape over the front of my DVR since the ROKU remote interferes with the NVR If you search around on the Dahua support pages you'll even find the tech telling folks to use the mouse and not the remote

After pressing 'Add' - change the three digit code from 000 to 008 and see if that won't fix it