Harrar

Thanks for the fast replies and recommendations. That's why I like this forum. Time for a little research now that you've provided some direction. Looks like I'll have to go with the active baluns because the resolution needs to be 1280X1024 minimum to show all the cameras they require. Thanks again.

To anyone interested in getting an idea of how much storage you may need for Mobotix cameras, I found the below link to be very helpful. You just select the variables for resolution, quality, codec, number of cameras, number of days, etc and it will give you a fair estimate of storage requirements. Hope it helps someone. It did me. http://www.overlandstorage.com/mobotix_storage_calc.html

For the Netopia router, you have to access "Expert Mode" and then go to NAT and enter Define Custom Service to forward port 7000 to your DVR. Make sure you set up a static IP for the DVR in its setup page.

It's been my experience that to access Swann DVRs over the internet you also need to forward ports 5000, 5001, and 5002. Check your Swann manual to be sure.

We have a couple of dozen units installed (four per store) at various area McDonald's. The newer installs have a parallel printer configuration and we just add the V3E between the register and printer, run cat5 from the V3E to our router/switch and forward port 4000 for the V3E. After configuring the data capture boxes in the Geovision software, all transactions appear fine on the cameras. Note - I always set up each V3E with a static IP address. The E model was definitely a step up from the older versions. Any specific questions??? Fire away.

One left field question. Did you try changing your HTTP server port to something other than 80? (assuming you're using 80) My first experience with a 2Wire had me running in circles because the ISP swore they were not blocking any ports but when I reconfigured everything to port 81 it all worked. Another thought is turning off Windows or any other system firewalls. One thought on checking all your ports are open is to use the telnet command from the cmd prompt. Just type in telnet, the IP address or dipmap or dyndns name then the port number. If the port is blocked somewhere your request will time out. Had better luck identifying problems with this then pinging a site.

The Two Wires I've configured, require you to go to the Firewall Section and add a new application for each port. Then you can tell it what port to forward where. Easy help is to go to portforward.com, chose your 2Wire and the application. You'll get step by step instructions.

Little confused on what you're trying to do. If you're running a server and a website on your home computer and have a dynamic IP address from your ISP, that is the only time you need something like DynDns to be running. There is no cost for this service. As an individual, you can sign up for 5 free domain names. With Go Daddy hosting your account, who cares if you have a dynamic or static IP. They take care of the dynamic naming service.

You can set up a Geovision system to view cameras on a MAC using Quicktime Player. First, you have to enable the 3GPP on the Geo WebCam Server and forward those ports (TCP 8554 and UDP 17300 thru 17380) thru your router. On the MAC, open the Quick Time prefernce panel from System Preferences. Click Advanced tab and select Custom. Select UDP from the Transport Protocol dropdown list. In the RTSP Port ID Field enter 6970 then press OK. Start your browser and enter the IP address or domain name of the Geo system , enter the ID and password then select the camera. NOTE - You DO NOT have full functionality with a MAC as with a Windows based system (no active X). Basically all you can do is view your cameras

If you can't run PassUnInstall.exe, try it in SAFE mode. If that doesn't work and you are comfortable with editing the registry, try this: 1) Click Start and click Run 2) Type in: regedit 3) Click on HKEY_LOCAL_MACHINE 4) Click on SOFTWARE 5) Click on Microsoft 6) Click DataCode 7) Highlight all the "default-*" in values on the right pane and delete them by right clicking on the mouse. Exit Registry Editor and reboot the computer 9) Geovision software, You will be prompted for a new ID and passord. Type in the new login information.

Forgot to add that many standalone DVR manufacturers have a built in DDNS that will reference and update using dyndns so you can enter your registration info into the DVR instead of the router. Check your DVR documentation for this feature.

If your router is a Linksys or Dlink or one of the dozen or so that support DDNS (check the setup page of the router) you can still register with Dyndns and enter that info into the router setup. One of the options will be the device (LAN IP address) it goes to. You will need to configure your standalone DVR's network settings to a static IP basically the same way I explained previously for a PC and then port forward the DVR specific ports to it

I'm assuming you have a PC based DVR system. What you will need to do is register your computer with one of the free DDNS servers on line. As mentioned earlier no-ip is one but I prefer to use dnydns as it's client program is built-in to most routers. If you have a Geovision system, this package is included with the software under DDNS. Anyway go to dyndns and set up a free account chosing whatever name you wish and then select an extension (dvrdns is pretty good). Next, download the DNS client software to your PC and run it as a service at startup. DYNDNS has good info and tutorials for setting it up. The client program will constantly monitor the dynamic IP address from your ISP and keep it pointed to your DVR so you can access it using the name you created from anywhere on the web. If your router supports it, you can skip downloading the client and configure the DDNS under the setup tab with the information you used to create your account. Hope this helps.

You may be confusing a static IP line from your ISP and a static ip address for your computer. With multiple devices hooked up to your router, typically whenever they are powered on and off, the router DHCP will assign a new internal IP address to that device i.e. 192.168.1.100 thru 255. What you need to do is assign a static IP to your device outside of the DHCP range of your router. As an example, Linksys routers typically start assigning IP addresses starting at 100 and above. IP addresses from 192.168.1.2 thru 192.168.99 are considered static. What you need to do is set your DVR to an address in this range. If it's PC based, go to the control panel and select Network connections. Right click The Local Area Connection and select properties. Select Internet Protocal TCP/IP then click Properties. Select Use the following IP Address. Type in the address for your device i.e. 192.168.1.50 (this will be your static IP address for this device) The subnet mask will default to 255.255.255.0. Enter the IP address of your router as the default gateway i.e.192.168.1.1. Next, select use the following DNS server addresses and just enter the IP address of the router again as the preferred DNS server. Leave secondary blank. Click OK and you've just set your system up with a static IP address. Verify that your router's port forwarding references this new address and you should be good to go. One note though, if you're using a Linksys router, go to the Security tab and make sure the Block Anonomous Internet Requests is unchecked. If you're using a compact DVR the same will be true in setting up this information in the Networking section.

I've recently had problems with accessing some sites over the internet. On getting to the customer site, I've been finding the DNS client has an error "Incorrect user name or password entered". Reenetering the proper ID and password and saving has no affect. The only way to remedy the situation is to register the name again. The curious thing is I always register the same name and password as before and do not receive the error message that the name aleady exists. Afterwards, the DNS client updates successfully and everything works fine. The problem only appears to be with Version 8.2 and the newer DNS Client. I have not had this problem with any of my Version 7, 8.0 or 8.1 sites. Has anyone else experienced this problem? Ver 8.2 bug? DNS client bug? Dipmap problem? Any thoughts would be appreciated as some of my customers are not very computer savvy and a 200 mile rive for a quick fix is expensive. Thanks for any responses.

I'm sure this is a "fun" topic for everyone. Up on a ladder or lift, trying to adjust outdoor cameras with the monitor 2 rooms over and 2 flights down and talking over your cell phone or walkie-talkie as you make your adjustments. My question is has anyone tried hooking up a WIFI transmitter to a camera and using a WIFI equipped pocket PC as a video monitor to make the adjustments. Thought I'd throw it out to this forum and see if anyone tried it before I buy a wireless transmitter and found out I'm wasting my time. Thanks, in advance

I'm sure this is a "fun" topic for everyone. Up on a ladder or lift, trying to adjust outdoor cameras with the monitor 2 rooms over and 2 flights down and talking over your cell phone or walkie-talkie as you make your adjustments. My question is has anyone tried hooking up a WIFI transmitter to a camera and using a WIFI equipped pocket PC as a video monitor to make the adjustments. Thought I'd throw it out to this forum and see if anyone tried it before I buy a wireless transmitter and found out I'm wasting my time. Thanks, in advance

Thanks for the responses. Since I already have a WIFI equipped pocket PC and WIFI camera transmitters are available for under $100, I thought this would be a little more economical. As for the focusing reply, obviously a course focus is done ahead of time but final focus, pan and tilt have to be made when the camera is in its final mounted position to ensure the customer is seeing the desired coverage area.