Jump to content

shockwave199

Members
  • Content Count

    2,222
  • Joined

  • Last visited

Posts posted by shockwave199


  1. Eastern looks an awful lot like what q-see uses. Typically, the dvr acts as the updater for ddns so there is no need for the dvr and router to match. No need for both to be set for ddns. Some use the dvr, some prefer to use the router. So just use the router for port forwarding and use the dvr for the ddns service. The free embedded service in the dvr is found here to sign up for an account-

     

    http://www.easterndns.com/

     

    Sign up and make note of your login, password, and whatever host name you create with that account. Then in the dvr, plug that information into the appropriate fields and make sure ddns is enabled. That's it. In the router, forward the ports you'll need for http, remote and mobile. Associate the DVR IP address to those forwarded ports in the router. That's basically it. Plenty of people think dnyndns is worth the yearly cost, and the benefits that go along with that- certainly the increase of usable host names for multiple systems.


  2. Assuming it's not a 3rd party camera to the nvr which might need to be ONVIF compatible, try setting the camera that won't show up in the nvr poe to DHCP mode first, before you hook it up to the nvr. Then when you hook it up to the nvr poe it should adopt the switches gateway. I think it's a good idea to keep cameras in DHCP mode so no matter where you have them hooked up, they'll always adopt the default gateway they're hooked up to.


  3. If you're on your own network, try adding http:// in front of the address when you're in a browser. If all else fails, you could try assigning a new address to the Dvr. Recently we had a power outage and I couldn't hit the Dvr anymore remotely or locally. I use No-ip and know how to network all this stuff. Something got screwed. I fixed finally by assigning a new static address to the Dvr. Also you should consider using something like No-ip for remote access, instead of using the public ip address.


  4. So according to that, 8 channels and cameras is 1400? I just put together an 8 channel 3mp system for 1600, and that includes two 3tb hard dives and a 21.5" hdmi with audio monitor. That was not alibaba either, all local vendors. I might have gone for cvi, but the numbers were out of wack. To me it's priced too high considering the image quality is lower than IP. It's not on par in that respect, it's lower quality. I only said what I said to the Op because he stated that the whole place is pre-wired with cat6. It doesn't seem like a good idea to go with cvi in that case. I have nothing against cvi, but I think it's still over priced- mostly the Dvr's. They're priced like nvr's, and they are not that. That, and the misrepresentation from places like qsee, that sends garbage cables with their kits. You can't install cvi on garbage pre-made cables, and I'd be willing to bet a large contingency of people expected that you could. It's still largely marketed with lingo to that effect. That's a real gotcha if you're not careful.


  5. The only thing I see cheaper is cvi cameras. A 1080p Dvr is still a lot of bucks and it's limited to 2mp. I like dahua products. I suppose cvi has a place. Heck, I considered it too. But IP 2mp has a better image than cvi 2mp. And since you can put together 3mp systems without breaking the bank these days, there isn't much sense to going with anything less now. Just my opinion is all.


  6. No. Does the camera also have a power adapter on the end of the cable? You could use a 12v-1a power adapter in that case. Or, you could pick up a cheap poe injector from amazon too. It never hurts to have one poe injector around in case it's needed.

     

    http://www.amazon.com/TP-LINK-TL-PoE150S-Gigabit-Injector-compliant/dp/B001PS9E5I/ref=sr_1_1?ie=UTF8&qid=1409546130&sr=8-1&keywords=poe+injector

     

    ALSO- is this a dahua camera you're talking about? What brand of camera?


  7. The camera is most likely not set to DHCP mode. Try to log into the camera while it's on your LAN, not plugged into the nvr at all, and once you're in there set it to DHCP and then log out. Then when you put it on your nvr poe, it should automatically get assigned an address within the poe switch subnet. That can take up to 45 seconds or so, so be patient.


  8. It seems as though most newer dvr/nvr can act as the updater and nothing further is needed in the router. Or, you can choose the router to be the updater and leave it be in the dvr/nvr. As long as one thing is acting as the updater, which is associated with gear you need it for, it doesn't need to be set in everything. With no-ip, I have two host names in my free account. An nvr I have that is associated with one host name was taken out of line for the time being. In 27 days I got an email saying that host name was about to expire, obviously because the nvr was no longer in line as the updater. So to solve that, I set the router for that host name. My other host name is set in my dvr and that keeps that host name refreshed. So the router is refreshing one host name and the dvr another. As long as one thing is updating the host name, all is good.


  9. Once your dvr gets an address handed out to it via dhcp, change the dvr to static. It will then keep that address always. THAT is the address you associate with each port you forward for that dvr in your router.You'll need to use a ddns service, either a free one that may come with the dvr, or something like no-ip or dnydns. THAT service tracks your public IP address for your residence, which will keep that associated with your ports forwarded. What I've noticed lately since having to do this frequently, is that my public IP address changes almost never. I suppose a prolonged power outage might force a change. But day to day, I essentially have a static IP address anyway. It's almost as though I don't really have to concern myself with ddns. I wonder if that is becoming more true for everyone overall.


  10. ^^ Take a look and see if corridor is an option. That fov is optimized for tall narrow views such as hallways.

     

    Higher MP (usually over 3MP, but it is sensor dependent) resolutions generally require more light to provide a clear image too. I can demonstrate this with a Mobotix camera in my driveway if you really want me to.

    I really want you to. Not because I disagree at all. Just because I LOVE demos of anything! Thanks, if you get around to it.


  11. Port 37777 had been set forward on my modem/router

    What's the deal there with your setup. If you have a modem/router and a router in line it gets complicated to the point that I don't know enough about how to bridge them for forwarding. What you have set thus for port forwarding and inputting settings looks to be correct.


  12. You need a monitor on a Dvr for initial setup. You can't administer it remotely without setting it up in the Dvr initially, hence a monitor on the Dvr. Once you setup everything, for the most part you can tweak things remotely and pull the monitor off the Dvr if you wish. I prefer to keep a monitor in line and always recommended people do so if possible.

×