CollinR

Hopefully they will try and fix alot of the IP marketing hype. Alot of installation companies have bought into alot of BS that in reality is very questionable. Using customer's prexisting LAN saves wiring costs. This is a pretty technical area, yes it's possible but 90% it's not practical. Current cameras take up too much bandwidth to be just be hap hazardly added onto an existing network. If they have an IT dept or you choose to research enough it can be done right. Often it's less headache to install a dedicated LAN for the cameras and have the DVR/NVR bridge it. This is how it works with analog systems, it's just their network is over coax.

I think you are on your way now. On the original instructions for the router, change the IP address to 192.168.1.6. So extrernal port 81 gets forwarded to internal port 80.

Great idea!

I have no clue where that came from or where it went. Pretty odd as most script kiddies use DHCP, so I have no idea where .100 would come from.

If you have 3 computers plus the DVR then it is depending on your DHCP pool. If the DHCP pool is 192.168.1.2 through 192.168.1.50 then a 192.168.1.100 is surprising. That is unless the DVR is 192.168.1.100 in which case you are almost there. I assume though that if you had told the DVR to be 192.168.1.100 you wouldn't be surpised from seeing it. I am glad to know you have an DHCP clients table on the router, that can prove helpful. Whoever they often don't watch statically configured clients. This is a Wifi router right? If so you should make sure the security is enabled. That could very well be somebody across the street using your wifi to connect to the internet. (You posted while I was editing, so reread. Too )

That image is taken from a TV capture card attached to the DVR output. The car's LCD screen shows the same colors. I can hook it up to an actual TV to check it out. I know that the camera can 'see' the IR on a remote control, though. I agree with Rory on his comments about color effects of IR, I haven't seen it represented as yellow specifically. Although it's not common to duplicate that either... I can see it possibly being percieved as yellow as the washout isn't a true white either. "IR filter"s are not normally a hardline they curve. Light frequency vs % throughput. This means the specific filter used controls how much of what spectrum of light get through. Note the how much... some does get through. Just having an IR filter doesn't mean it can't see any IR at all. IR on remote controls... If you see the light on the actual LED you haven't learned it all. Go in a dark closet or bathroom and see if it can be used to illuminate any distance. If it truely has no IR filter at all you will see that it illuminates a small closet pretty well. Some have different pinouts, I have never wired one up wrong or even had one that didn't use the default pinout. I think you should evaluate this before proceeding too much farther. I would definatley try swapping it too. Thats alot to ask, if you look at how complex your eye is... Lots of stuff going on to make your vision good under most situations.

Oh it's no problem, I try to be helpful and I have a helpful business model. You should just think of this when you need a new camera or a buddy says they want CCTV. This is free support, paid is usually much better. Okay I'll help you understand the situation as you might be able to stumple across the answer just testing. Is the windows firewall on, on the DVR? Is port 80 a valid exception? Because the internet is based on IP addresses and there are fewer IP addresses available then their are people wanting to get on the internet not evryone can have a unique one. Some smart guy thought up a service called NAT, or network address translation. This allows your router to have 1 IP address yet allow many computers to connect to the internet through it. Thats a simplification and not the only issue with IP addresses but that is why you have 2, 192.168.1.X and whatever my avatar says which is what your router was assigned. Okay so now you should better see the problem. So the IP in my avatar is your external IP, it represents all computers on your local network. Inside the router is an DHCP server, what it does is automatically designate IP addresses when your computers log on. HDCP makes setting up networks very easy however it's not so hot for servers. Your router should have a DHCP "pool" of addresses, usually thats 192.168.1.x through to 192.168.1.x. What we are tring to do is make sure your DVR has a specific internal IP address, 192.168.1.2 or 192.168.1.6 or 192.168.1.55 makes no difference. What matters is: The IP address is valid (192.168.1.256+ is not valid) You know what the address is The address never changes (DHCP not used) internally The address IS NOT CURRENTLY IN USE by another computer, 192.168.1.2 probably was. Since as you said you have three. If all computers were rebooted I think you may be done, or if you know which one was 192.168.1.2 just reboot it. Otherwise pick a different number, 192.168.1.100 might work for you, it should not be in the DHCP pool if possible. I personally setup all my servers so they come first .1 is the router/DHCP/NAT/Firewall, .2 through .10 are servers or other routers and .50 through .5x are the network clients. This gives me enough room for 49 servers if needed and over 100 network clients, more then I have ever needed. Thats all more then you need to deal with now but if you add in a mailserver of FTP server you'll start seeing how this can benefit you. EDIT: You are better off redefining the DHCP pool to a small number of IPs with room for the DVR either above or below them. This way after a power failure you know no other computer will be assigned it's internal IP address. A DHCP pool like I mentioned above works well, 192.168.1.50 through 192.168.1.54 in your case. Then the DVR as 192.168.1.2. Hope that helps some. [/edit] The next issue is ports, these should be looked at just like the physical ports on the DVR. Keyboard is for keyboards, mouse is for mouse. In TCP/IP there are thousands, 80 is http (web servers), 21 is FTP, 25 is outboand email. Your ISP usually provides several levels of service from really cheap residential to crazy high commercial. If you pay for residental services your terms of service will usually prevent you from running a public webserver. The easiest way for them to enforce that is to simply kill port 80 inbound, no more webservers. This is why we are tring to make internet requests come in on port 81, it may well be that port 81 is blocked too. If thats the case try port 82 and so on until you find something pinholed. When computers talk to each other via the internet it is extrnal IP to extrenal IP. For most routers you can browse to the external IP address to test locally without calling someone else. Again the IP in my avatar is your external IP address that the rest of the word can talk to. Each time they do communicate it is over a specific network port that relates to the kind of communications that will be happening. Hopefully now you know why we are saying external IP :81 forwarded to internal IP :80. If you use DHCP and not specify and address on the DVR. You can BIND the DVRs MAC address to a specific IP howvere I think thats more difficult and often not an option in residential routers.

You install it on a machine in the control room. You can get by without it without any issue. I use microsoft's RDP or VNC as much as I do control center.

Google it, you can see IR and you can see through many synthetic materials like nylon and polyester. Basically the stuff they make swimsuits out of. However you won't be able to see much in respect to focusing an illuminator. I think thats the best plan and how I am still doing it. I also try to schedule the install to start so that it finishes after dark. What sucks is convience stores, I need thm to kill all their interior lighting. Sometimes that poses a problem.

First! What happens when you http://IPINMYAVATAR:81 ? The IP in my avatar will be correct for you very often, it doesn't actually trace requests it's just using the info the browser sends. If you try to hide your true IP that avatar won't know. Okay assuming that didn't work right. On the DVR 1. Click Start 2. Control Panel 3. Network Connections 4. Connection properties (right click the connection you use, choose properties) 5. Choose Internet Protocol (TCP/IP) from the box 6. Click Properties 7. Check "Use the following IP address:" 8. IP address = 192.168.1.2 9. Subnet Mask = 255.255.255.0 10. Gateway = 192.168.1.1 11. Check "Use the following DNS server addresses" 12. Preferred DNS server = 192.168.1.1 13. Alternated DNS server = blank 14. Set the DVR back up as it was (port 80), however you changed it. On the router 1. Go to 192.168.1.1 2. Username: Admin Password: password 3. Click Security in the on the top bar. 4. Click Port Forwarding. 5. Click the Red "Add" link. 6. Under "Networked Computer/Device" enter 192.168.1.2 7. Under "Protocol" click the Red "Add" link. 8. Click the red "Add Server Ports" link. 9. In the Drop down menu for Protocol, select TCP 10. Under "Source Ports:" Set to "81" 11. For "Destination Ports" Set to "80" 12. Click "Ok" 13. On the "Add Port Forwarding Rule" Menu, Click Ok. You should be finished, and problems please post. Now the IP in my avatar should work for you. You should probably print this! If things go bad and you are unable to recover an internet connection! First try and see if it is a DNS error you are having, attampt to connect to my website directly by it's IP address. http:\\208.109.140.67 If you get the LVS homepage you know you only have a DNS problem (the router isn't working as a DNS server). If that is the case try and get the DNS servers from the router's status page. Go to step #12+#13 on the DVR and change those DNS server addresses to the ones in the router's status page. All else fails... On the DVR Redo all the steps up to #7, set the two values on that page to: "Obtain and IP address automatically" and "Obtain DNS server address automatically" Report back.

You also need to look at what hardware they are actually using, technically most cards have some sort of hardware compression. Once you get past 4 channels it's a must, you just don't have enough CPU left for anything else. The NV7000h can natively compress H.264 with hardware. The much cheaper and more available NV7000 is still a hardware solution it just doesn't support H.264, so it's more of an issue of DVR $ vs. storage $ for the NV7000 vs. NV7000h. GV250 through GV800 have the ability to compress to MPEG2 with hardware, however the software doesn't allow it. The GV2004 and 2008 can and I am not sure what other codecs as well. I don't use combo cards so I can't help much after that. Basically whats happening in most is hardware to MPEG2 PS and then software to transcode it to MPEG4, H.264, ... You know you have a 100% hardware solution when you have XP and your DVR running headless and solid on a 600mhz CPU. With a display connected and rendering the video you should have less then 25% total CPU utilization on a modern P4. If it's more then that something is happening in software.

You can do it either way and they should both work. If you run into trouble be sure to make note of the make and model of your router. ALSO make note of your model and part # of the modem, this way anyone reading this can look up the manuals if we need them.

IMO you are better off modifing the router forwarding config rather then the DVR config. In the router just change: port 80 to port 80 to port 81 to port 80 This way the DVR never knows the difference and you can have one configuration for all customers. You can also use dynamic DNS to handle the port 80 to port 81 from the client side too.

Might I suggest welding goggles. Google "$10 IR Goggles" The problem is the sun puts out sooo much more IR then any illuminator I have ever seen. It makes it very difficult to discern whats, what and where.

Just using the cat5 spare pairs for standard 12vdc power right? That is correct What is your experience with Max length,voltage loses and current drop ? It's super crappy. I still double up with 18-2 for the most part. I wouldn't even think about using it with a PTZ. It does actually work fine for alot of stuff though. EDIT: If you were asking about REAL POE rather then using Cat5 as a power cable it's not a problem. 40VDC will go the 300' maximum for ethernet.

Totally agree and why I suggest them to inexperienced installers, they can make it very easy. Varifocals also cost more and don't provide the quality some fixed lenses do. Thats of course fujinon to fujinon not fujinun to fujinon. It's a bigger deal in megapixel then SD analog systems so don't expect a glaring difference.

If you have little experience go varifocal, if you already know you need a standard lens just buy that. Few situations require you to change it after it's installed.

Ditto but I think something like 12mm caps that out. (PLEASE let me know if I'm wrong. ) Also the wider the lense the more light it generally lets through, you are better off getting closer and using 6mm rather then being easy and using 50mm.

Run the Keylock utility, then you don't get the desktop.

Right thats what I was getting at, LRP is not usually a 1 camera deal. If it is you see next to nothing of the pumps and parking lot. LRP done right and functional is not cheap.

you need to ditch that ENTIRE mindset... Here I'll redo it for you... You will always have jack@sses that will ~claim~ they can do everything for nothing. Don't get involved in that. When I ampresented with this I basically explain to the customer how my contract works. I explain that some of the features they have requested increase their costs significantly. In order for me to provide the level of service the contract discribes for that function the price is XXX. Explain many will claim their systems will do this, but few actually do. Fewer provide refunds for functionality paid for yet not realized.

It's strange how much megapixel effects everything. The obvious. Robust network DEDICATED to CCTV. Greater camera cost. The not so obvious... You need fewer cameras, sometimes radically fewer. Camera positioning is radically different as well.

Yeah, I wouldn't be buying from them...

IP is too new for that, the ones under $500 although some are good have poor bang:buck ratios when compared with the analog counterpart. IP vs Analog is a wash on VGA level cameras, there isn't much point in paying for the IP functionality. Megapixel however changes that bigtime.

Yes you can use baluns but I don't know if it's worth the $. Composite to SVHS doesn't make much difference in cameras, SVHS has in the past carried 800x600 @60hz without issue. Unless the camera really has the added capacity I doubt it's really worth it. Especilly since the good ones all have stereo audio as well which just jacks the price up more.