Jump to content

tdenson

Members
 View Profile  See their activity

  • Content Count

    84

  • Joined

  • Last visited

Posts posted by tdenson

  4. Posted

    If you bought a poe nvr it should at least work. Before I would just consider the extra cost for it a loss and switch to a poe switch, I'd at least try to get the built in poe to work. If you haven't gotten too far in customizing the nvr, I'd default it back to factory settings, or at least default the network section of the nvr and try again. You should not be getting duplicates. If you can't get it, work through it with customer service where you bought it. If it's a problem that can't be fixed, send it back for a refund, exchange, or whatever. You paid more money for an nvr with built in poe- you should have a working nvr that provides that. And while I agree that for some a poe switch is the way to go, for others the built in poe makes things easier to get up and running. And you can hit the cameras web interface with built in poe, but it is a bit convoluted to do it. But one thing I wouldn't do in your situation is just accept a problem with the nvr poe. You paid for that. You could have spent less on an nvr without poe and put that extra money towards a poe switch in the first place. So, solve the issue first and then see what the next step is. At least, that's what I would do. Good luck.

     

    I didn't specifically pay extra because I wanted POE, it just happened that the one I chose to buy had POE (from the models available in the UK). The more I think about it the more I think that ad hoc POE switches are more convenient in that I don't have to run the wiring all the way back to the NVR.

    At the end of the day life is too short and it would be too much hassle to take it up with my supplier.

  6. Posted

    I personally would refuse to buy an NVR with PoE built-in. The problem with the Dahua and Hikvision NVR's with this feature is that they have sort of a router built in. It assigns IP addresses in it's own subnet that's not accessible outside the NVR. The Ethernet connection on the NVR that goes to your home network is separate and the two can't communicate.

     

    If you want to communicate with the camera temporarily, you have to unplug it from the NVR, plug it into your home network with a PoE device, change the IP back to your home subnet using their management software, do what you want. Then change it back to the exact NVR IP address (same one or it will think it's a new camera like you experienced).

     

    Some people have connected one of the PoE ports to their home network to link the two up, but then you lose a port and it becomes more work than it may be worth.

     

    My advice is if you want to access the cameras individually through other software or browser, then you not use the camera ports on the NVR and buy a PoE switch and configure them as you like and add them to the NVR manually.

     

    Thanks. Yes, I am rapidly coming to the conclusion that where I want a POE camera, I will either use a POE injector, or just use passive converters where the cable run is not too long.

  7. Posted

    I have read the Dahua user manual but don't understand how the POE ports on my Dahua work. I have plugged the 48V PSU in appropriately, and connected a POE camera to one of the ports. It works but it appears twice in my camera list and I get duplicate preview windows. One of the entries I can't delete, and if I delete the other entry both disappear.

    However, in the remote devices section of the firmware it lists my camera with a port number of "Port 1" rather than a numerical value. Also it has an ip address of 10.1.1.128 when my main network is 192.168.1.x. If I try and change it through network setting/switch I get an error "switch and device shall not be in the same network segment".

    Can someone please explain to me what is going on here ?

  8. Posted

    For now, forget about anything IDMSS Lite and put it down. Physically go to you NVR and make sure the MAC address and Gateway are set for your router on the NVR(hook up a display to either a tv or computer monitor via hdmi/vga port). If these are not configured then no matter what you do, it will not work. I am not saying port forward anything on the router. Next, while still at the NVR see what your TCP port is set to under Network settings. Write down whatever port is in the TCP section on the NVR. The Dahua NVR will not work on your network using the TCP port if the default gateway and MAC address are not set. (you can quick set it by changing to DHCP and restarting your NVR then change it back to Static with whatever IP address you want)

     

    Go to IDMSS lite and input whatever port was in the TCP section of your NVR into the IDMSS Lite app as the port. (NOT the HTTP Port.....If you are using IE to log into the NVR with the IP address of 192.168.1.150:8000 then 8000 is your HTTP port and NOT your TCP port)

     

    If this does not work then you are either using an IP address out of range or something on your system is blocking the NVR. I have set up dozens of these on dozens of different routers. The TCP port is different from the HTTP port and from your description I think you have those two confused. Take a picture of the Network page on your NVR and post it up if this does not fix it.

     

    You were right and I was confusing TCP and HTTP ports. I now have it working on an iPad although for some reason I can't get it working on my iPhone, although I am sure this is something and nothing.

    Thanks v. much

  9. Posted

    If you did not set your MAC address or your default gateway it will never work. You can not just plug it into a network and expect it to work. Go to your router page and look for locally connected devices. If you do not see it on the router then you still need to configure the NVR. Go back and follow my instructions and it will work locally.

     

    I don't see anywhere in IDMSS to set either my MAC address or gateway. Furthermore I don't see the relevance to a locally connected device of the gateway. As I have said in another post it works fine with IE, Blue Iris, Security Spy and DComplex.

    As far as following your instructions, they were all to do with port forwarding, which has nothing to do with a locally connected device.

     

    I have now tried GDMSS on my Android phone and I get the same timeout problem. This is really strange as I'm sure these apps work, but I really can't see what I am doing wrong.

  10. Posted

    Is your TCP port 8000 in your NVR? By default it is 37777, so unless you changed it, that is your problem.

     

    Yes. As I've already said it works with IE, Blue Iris, Security Spy and DComplex so something as basic as that I have done. I don't use the default as I have a convention for the ip address and ports of all my cameras as 192.168.1.15x and 8xxx, and use the base addresses for the NVR.

  12. Posted

    The bit rate for each channel for main stream and sub stream in the NVR. Usually, time out means there is a network issue and rebooting everything helps out. If your too high on the bit rate, and your ISP service is not liking it, that will also give you time out. What is our download and upload speed? Are you timing out when your on your own network or outside your network?

     

    As I've just said in another post I am only testing it locally ATM. I wouldn't think I would need to adjust bit rates. I can access the camera with IE, Blue Iris, Security Spy and DComplex quite happily. I will look again at how I have set up IDMSS, I must be doing something dumb.

  13. Posted

    Recheck your port forward settings.....it sounds like yours are wrong. Make sure you have forwarded ports 37777, 37778 and whichever http (I use 85) to the NVR IP address in your router. If you are not seeing your NVR on your network router, change the Ip settings on your NVR to DCHP and reboot. After rebooting change it back to Static and input whatever IP address you want (within your router range that is not being used by something else)

     

    I should have said that at the moment I am only testing locally. I like to do things in a logical order and there seems little point involving routers and port forwarding until I can get it working on my local network.

  14. Posted

    Someone told you the app to use and we are telling you that it will work. It works for everyone on this site that has a Dahua NVR.

    So, if we say of course it will work, guess what, it will work. Your settings are not correct, that is why it is not working for you.

     

    I don't think that was called for. I only said "are you sure" because it's not unknown for someone to misread a post and reply about the wrong device, I was only confirming what was being said.

  15. Posted

    Reboot the nvr and router. Make sure you have the correct password in the app. And what is your bit rate set for in encoding?

     

    I have done that to no avail. And yes, I have checked the password. I even changed it from a nul one to a real one just in case that was throwing it. Also, I don't really see the relevance as they both work fine from Internet Explorer. As far as the bit rate is concerned do you mean at the camera or in IDMSS ?

  16. Posted

    Any Dahua device can be accessed from iPhone and iPad with iDMSS (and I am sure that also with third party programs), not just 3208P.

     

    I must be doing something wrong then. I have both a Dahua NVR and a Dahua camera. When I try to connect to either one with IDMSS I get "Time is out". This is the lite version, I would happily buy the full one if I thought it would work, but surely the lite version should at least show the video ?

  23. Posted

    I am thinking of giving up on buying Dahua cameras and instead use cheaper cameras, and then install common or garden PIRs and use those to trigger the alarm inputs to the Dahua - is this a sensible strategy ?

     

    I'm not sure using common or garden variety PIR's would be a wise choice. The cheap PIR's will probably cause you a lot of grief in terms of false motion detection.

     

    I own a Dahua DVR and use Optex http://www.optexamerica.com/security-products/lx-402 commercial grade PIR's as input to my security system which is a HA Omni Pro II system. .

     

    I didn't necessarily mean cheap, I just meant standard PIRs as opposed to visual motion detection. It seems to me that the PIR approach is likely to be far more reliable. Trouble with visual MD are things like insects and rain.

    I have now tried it with a cheap PIR as it happens and it works nicely, but I will investigate the ones you mention (I am in the UK though).

  24. Posted

    I'm having a similar problem with my Q-See QC808 unit. I believe this unit is a rebranded Dahua.

     

    I currently have two Hikvision cameras attached to my unit and even though I can record video manually or on a schedule, I can't seem to get motion detect to work trigger the recording. I upgraded the firmware last night but still nothing. It seems like motion doesn't get detected at all.

     

    I've contacted Q-see tech support and I'm waiting for their reply.

     

    Share any new information you might find.

     

    Thanks

     

    As I said, the only way I've been able to even get motion detect half working is by buying a Dahua camera.

  25. Posted

    I have been there too... MD sucked on a Dahua IP system I set up. Either I missed too many events, or recorded almost 24/7. I end up configuring scheduled recording during business hours. I also remember testing Dahua NVR with a couple ONVIF IP cameras, and while they were recognised ok, MD was not working at all. So only manual, alarm or scheduled recording was possible.

     

    It has been a while, first thing I would do now was to check for the latest firmwares for both NVR and cameras.

     

    Thanks, I'll take a look

×