Soundy

Practically no commercial (ISP, corporate, etc.) SMTP servers will allow you to relay unauthenticated mail from an outside address; that's an open invitation to spammers. What I've found works almost universally is to use the SMTP server for the ISP the connection is with. For example, with customers who use Shaw Cable out here, I set their camera/DVR/etc. SMTP server to smtp.shaw.ca - no encryption, no authentication necessary, because the mail is coming from within their network. For the corporate sites that have their own mail servers, it generally works to use that SMTP - again, it typically works without issue, because like any other mail client in the place, it's all coming from within their network.

Can you describe this "wave" effect a little better, or even provide a picture of it (photo of the screen with a cel-phone camera, etc.)? "Wave" noise is typically caused either by electrical interference, or by a ground loop. The former can be caused by wiring running too close to a high-current power feed or junction box; the latter can be caused by poor wiring and is common in cheap cameras. The fact that it's happening regularly between 5AM and 10PM would indicate that it's the former (electromagnetic interference) and that it's coming from something that turns on at 5AM and runs until 10PM - possibly lighting, a cooling unit, etc. With cheap, poorly-shielded systems, all it takes is one wire running too close to such a source, and the noise that's inserted into the system can appear on multiple cameras.

That is some SEXY $#!+ right there! Wow!

Well the beauty for you is, you can get single- and multi-channel video encoders that will let you attach any analog camera to an IP network, so even in the instances that an analog camera might provide better performance, you can still use your existing infrastructure, or deploy the network infrastructure for future camera upgrades. This gives you the additional benefit of not needing analog capture hardware at the head end. In instances where an all-analog chain IS necessary, you can wire with Cat5e or Cat6 and use video baluns to send the analog signal over that... when the time comes to upgrade, simply take off the baluns and re-terminate for network.

Sounds like you're running at the wrong resolution. A typical 19" 16:10 widescreen VGA monitor will have a native resolution of 1440x900, while a 4:3 "non-widescreen" 14" will usually run at 1280x1024. If your DVR or computer is not using that resolution, the monitor will have to up-scale the image, and it WILL look soft. Worse, if your device is using a 4:3 aspect ratio display resolution, the monitor will be "stretching" it to fit the 16:10 aspect, which will make it look even worse.

IN THEORY, if the DVR is on all the time, it should always have the same IP address. DHCP leases typically work like this: once the "half-life" of the lease is reached, the device (DVR, computer, etc.) asks for a renewal of the IP it has, and should usually get it immediately. If the end of the lease is reached and no renewal request has been made, the IP returns to the pool. I believe most LinkSys routers default to one day for the lease time (this can probably be changed), so as long as the DVR is off less than 12 hours, it should always get the same IP back. The problem I've found with a number of LinkSys routers, and a reason I never recommend them, is that they have a tendency to NOT renew leases properly, even if the machine is never offline. I've had a DVR's IP repeatedly change from .100 to .101 and back to .100 using a LinkSys router, changing on an 18-24 hour basis without even a reboot of the DVR. In those cases, yes, I've had to set the DVRs to use statically-assigned IPs. That all looks right! You've been an excellent student, gold star for you!

4CIF is only 704x480 resolution, so it's not going to be huge to begin with. Possible, if your display resolution is less than the native resolution of the LCD. What size/model of LCD is it? How do the interface graphics (on-screen text, controls, etc.) look? Fuzzy as well? The overall image MIGHT, depending on display settings; that won't affect the video from the cameras, however. You might check the compression settings on your DVR - the higher the compression, the more artifacts and the lower the video quality.

Glad you got it working! Yes. As I explained, any system (such as your DVR) that wants to communicate on a TCP/IP network needs certain information: a unique IP address, a network mask, a gateway, address(es) of DNS server(s), etc. There are two common ways for it to get that information: either from a DHCP server on the network, or to have it entered manually. If you set it to get that via DHCP, there's no need for you to enter it manually, so those options are blocked out. DHCP servers have a timeout, called a "lease", that if it isn't renewed periodically, an assigned IP will go back into the pool for it to give out to another system. If your DVR is off or disconnected for too long, the lease will expire. So, there are two ways around it: One, don't use DHCP, but set the DVR to STATIC and enter that information yourself. Two, see if the router has a "Static" or "Reserved" option under its DHCP Server setup, that lets you permanently assign a certain IP to a specific machine. If you go with the first option, use an address outside of the router's DHCP pool range. Most will default to a range of 50-100 available IPs, such as 192.168.1.100 through 192.168.1.150; if you hard-code the DVR with an IP of 192.168.1.103 (for example), it's likely that at some point, the router will also assign that IP to something else, and you'll have a conflict. To avoid this, use a number outside that range, such as your original 192.168.1.10. Then set your port forwarding to that address. IP addresses can use any number between 0 and 255 for each "octet" (between the dots). 0 and 255 are reserved; 1 or 254 are often used for the gateway; so you should be able to use any address between 192.168.1.2 and 192.168.0.253.

because no dynamic-DNS service, free or not, is 100%effective. i've had ISPs that force IP changes every 1-2 hours... when DDNS updates can take up to an hour to propagate, DDNS becomes nearly useless. i have never had any issues with www.dyndns.com. their free service is great and the windows client program works perfect. It's not an issue with DynDNS or any other dynamic-DNS service *specifically*... it's a potential issue with the whole domain name system and the fact that changes can take time to propagate throughout the DNS directories around the 'net. A static IP is still the BEST idea for ANY type of server where you need ready remote access, be it a DVR, a webserver, mailserver, etc. Dynamic DNS *as a concept* is still just a workaround.

Dear ini, Here I compare NUUO Nvrmini with VS-5012. 1. NUUO supports about 400 cameras 2. NUUO supports compression formats: h.264, mjpeg, mpeg4, mxpeg(mobotix) 3. NUUO supports upnp. 4. NUUO supports autodetection for cameras. 5. NUUO offers GUI to change recording schedules 6. NUUO supports video backup 7. NUUO supports video export into AVI or ASF 8. Video supports video enhancement. 9. NUUO suppots PTZ-presets. 10. NUUO supports automatic data backup 11. NUUO nvrmini has reports of system info, hdd usage, disk status 12. Support for NUUO CMS 13. Support for POS For more information, please go to http://support.nuuo.com/mediawiki/index.php/Nvrmini NUUO Tech Support Hmm. http://dictionary.reference.com/browse/compare The above isn't comparing anything... it's just spam.

because no dynamic-DNS service, free or not, is 100%effective. i've had ISPs that force IP changes every 1-2 hours... when DDNS updates can take up to an hour to propagate, DDNS becomes nearly useless.

It's possible the program isn't sending the right control codes... I've had similar strange issues using Pelco P and D via Vigil software. Some cameras seem to expect different control codes to kick them into their setting menus, and the problem with such "generic" protocols is that different software and cameras handle anything outside the most basic controls differently. On one site, for example, I have two Capture PTZs (both Fastrack II, but one a much older revision) and two Pelco PTZs (one a Spectra III dome, the other an Esprit). One Capture doesn't like computer serial control AT ALL, the other all functions work great . The Esprit also works fine with all tour/preset/menu commands through the software... but with the Spectra, the menu buttons just open up the iris (which is odd, because I've seen lots of other sites using Spectra IIIs successfully with Vigil).

More commonly known as "Siamese cable" - it can be convenient to have both in one, but it can also be a hassle, as it doesn't wrap as easily as separate cables (ie. if you have to create a service loop or coil it up for later payout), and doesn't slide as easily through tight spaces or around tight corners when you're pulling it.

Not so - the only thing that would change is your "outside" IP. If you're using dyndns.org, that shouldn't be an issue, as the name will update to reflect the change. The DVR's IP would (and should) stay the same, since it's getting that address from the router on the internal network. That doesn't seem right... the DNS entry should have either the router's internal IP (192.168.1.1) or an outside DNS server. Is there not another entry for an IP address for the unit? When you're on Static, it should have spaces for you to enter an IP, a Netmask, and a Gateway address. None of that should have any effect on this issue. That should all be correct, as long as the DVR's IP is right... I still think something is wrong there, though. Also, you only need to forward TCP; UDP isn't required for this. Is Video Server E also using port 80? If it uses other ports, they'll need to be forwarded as well. DHCP stands for Dynamic Host Configuration Protocol. In short, it allows the server (your router, in this case) to automatically tell the clients (your PCs and DVR) the proper network settings to communicate on that network: an IP, the netmask and gateway settings, the DNS server address(es), and so on. Since each device must have a unique IP address, it gives each of them an address from its "pool" - usually something in the range of 192.168.1.100 to .150 or so. If you're setting the router's IP to "static", you need to enter the IP, netmask, gateway and DNS info manually... since the DHCP Client Table lists what addresses the router has given out to connected devices, and the DVR is not getting that information from the router's DHCP server now, the Table won't have a listing for the DVR. Now all that aside, assuming everything else is set up correctly (I still think there's something missing in that network config), if it still doesn't work, it's possible that your ISP is blocking port 80 (many of them do). In that case, you could try using a different port, such as 81, 88, 8000, 8080, or any other port that's not in use by something else. You'll need to change it in the router as well as the DVR; then when trying to access that from an outside web browser, add the port number to the end of the URL like so: http://aliciac.dyndns.org:8080 (assuming you used 8080). Note that, especially with Internet Explorer, the "http://" is *required*, or it will get confused (other, more intelligent browsers, will assume http by default).

"Best" for what? What sort of features is he looking for? What form factor? Standalone or PC-based? Does he want/need IP camera support? POS integration? Access controls? Redundancy? Multi-site support? What are the storage/retention requirements? From my own experience, Camacc/3xLogic have a great system in their Vigil DVRs. I've installed systems that will do up to 30fps on each of 32 analog channels (960fps total) as well as supporting a wide range of IP cameras and network storage. They have advanced POS integration and great technical support and have even created customized code for one of our clients to support their Squirrel POS systems. Their new versions now have built-in analytics as well. Compared to other similar systems I've seen, they're also quite reasonably priced for what they give you.

I've worked with a professional stock-car team - believe me, anything that will add weight or rob power is NOT desirable in a pro car. A PoE switch would be a big waste of power: you'd have to step the power up to 120VAC through an inverter, which is a horribly inefficient device to begin with, just so the switch can knock it back down to 48VDC. The only way to improve that would be to have a switch or injector that can take 12VDC in and bump it up to the required 48VDC, which would still require some form of inefficient voltage inverter. Now, if the OP is just a racing hobbyist or racing in an amateur division, it might not be as much of a concern...

shoreview is on the right track - the movement of the "snow" in low light is probably what's triggering your motion. I've also seen it where a B&W camera (such as a day/night camera in night mode) triggers motion because the shifting color artifacts are seen as moving objects by the DVR - the fix there is to reduce the saturation on that channel.

Yeah, DC resistance of that wire should be AT MOST a couple ohms over a hundred feed... that's your problem, something is introducing a LOT of resistance in that wire (probably poor manufacturing), which is causing excess voltage AND signal drop.

That's what it really comes down to - basic motion detection 99.9% of the time is too unreliable for an alarm system, usually because false positives are way too common. A bush or tree moving in the wind can trip it, or an animal, the glare of passing headlights... lines of electrical noise... even the shifting of color artifacts when a day/night camera goes to B&W mode can cause constant tripping of the motion detection.

Plz don't type as one line post I hate scrolling Not his fault... the board will normally size the display to your browser and wrap the text automatically, but in this thread, the extra-wide pictures are forcing the display to a wider size. test 111111111111111111111111111111111111111111111111111111111111 222222222222222222222222222222222222222222222222222222222222 333333333333333333333333333333333333333333333333333333333333 444444444444444444444444444444444444444444444444444444444444 u see my point Yeah, you hit ENTER after each line of numbers. Unless you're breaking something up into paragraphs, most people don't do that as a matter of course, especially when the text-entry box is a lot narrower and does display with wrapping. If you keep typing a sentence though, it will naturally go to the display width of the page, which on a page with big pictures, will be wider than normal. And you get long sentences with no linefeeds that force you to scroll...........................................................................................................................................................................................................................................!

Not necessarily - it depends on your internet provider. Since DVRs typically run 24/7, they don't randomly connect to the 'net and don't usually change their IPs on a frequent basis, unless the ISP forces a change (like some DSL providers I've dealt with). The best solution is to ask your ISP for a static IP. Most broadband providers will accommodate it for a small extra fee ($10/mo isn't uncommon). Some provide it automatically if you have a business internet account.

Should probably be discussed in the Vendors' forum, but it seems impossible to get access to that anymore... I first asked I think close to two years ago, never even got so much as a "no" reply.

Plz don't type as one line post I hate scrolling Not his fault... the board will normally size the display to your browser and wrap the text automatically, but in this thread, the extra-wide pictures are forcing the display to a wider size.

Kinda depends on exactly what "these" are... I've (re)built a number of Vigil DVRs using HiCap and XECAP (ComArt-based) capture cards on a wide range of boards using Intel, SiS, and VIA chipsets, mostly using Windows 2000 and XP Pro, but I did experiment with Windows 7 as well. Vigil run without a hiccup on all of them.

What sort of DVR is this? If it's PC-based, you can probably just go into the data drives and back up the necessary files...