Harrar

Yes, you still need one V3E per POS station. What the manual means is that the "GV System" (DVR) can handle 16 inputs (one for each camera). Prior to the ethernet version, you were limited to the RS-232 or USB with NET Box/Card or Hub. With the new software, you should be able to accept 32.

Hope you don't carry your problems over to the new computer. With the hard lockups and corruption, you may have a problem with your drive. Have you tried running chkdsk on it or some other hard drive diagnostics?

If you're within 100 meters (328 ft), you're better off using a cat5 cable to connect the router to the dvr. Other than the data rates of wired (100Mbps) versus wireless (54Mbps) you may have to consider interference to the wireless signal. Is it line of sight? How many walls/floors between the router location and the dvr? What material are they made of?

Did you check or remember to activate the "Allowed PTZ Cameras" under the "Video" tab of the Webserver setup? If not, they won't be visible over the web.

You can also just have the camera tell you what it's current IP address is but unless they left the factory user name/password in, as thewireguys said, tough luck.

When you consider the cost of two cameras plus their cable runs and either a PoE switch or two PoE injectors for power, you're coming very close to the cost of a Q24. Also, do you plan on recording video? Now you're adding an NVR to the mix or a NAS to store your data. Do the other camera manufacturers offer free software for record/playback? Mobotix doesand you can access from anywhere over the web. You can also just attach a USB drive to record your data.

Good points by Viopmodo with the exception of the audio circuits being permanently "burned out". This is true of only for the microphone in the camera. You'll still be able to program warning messages or make announcements thru the camera's speaker.

Correction to the previous post. It's an M12. Sorry. Just finished some quotes on some D12's and D24's.

Mobotix D12 3MP, dual lens camera. Can be configured for color day and B/W night or 2 color lenses with focal lenghts of 4, 8 or 25mm. Also has a PIR sensor and two way audio. Excellent camera

Look at the DLink DES-1228P. It's a 24 port 10/100 PoE smart switch with 4 Gigabit ports for a good price. Used this at several locations running with 16 to 20 Mobotix cameras. Haven't had a hiccup with it in almost a year now.

Not familiar with the Ruby Gemstone/Gilbarco systems but I've heard they have a lot of little quirks in interfacing with other products. Maybe the below link will answer some of your questions regarding that equipment. http://www.usavisionsys.com/support/faq.php?category=9 Help on the Geo side, just post or PM .

Haven't had any problems with multiview using versions 8.31 or 8.32 but it seems a bit slower than older versions. At a couple of locations we have customers using multiview to monitor 2 servers with 20 cams each without complaints. Over DSL, the Connect to Server on the cams takes longer when viewing all cameras. Cable is a lot better. Never used 8.3. Skipped over that one because of all the bugs. Have you tried multiview over the LAN? Any display/speed problems that way?

A simple answer to your question is yes, it's possible. The simplest solution would be to use IP cameras at each location with a NAS for storage. The cameras would record to the NAS and you would be able to access and live view from anywhere over the net. Go with cable and not DSL. As far as a cost estimate is concerned, there are to many unknowns from your general inquiry. At a minimum, other than the cameras and NAS, you'll need a PoE router or router and PoE switch or router and PoE injectors and cat5 cabling. If your cameras are located over 100 meters from the internet connection, you'll have to add another switch in the line. The choice of cameras will be determined by what needs to be covered at each location. Day/night? There are a bunch of different cameras out there but I would look at Mobotix camera options. We've used them in quite a few remote locations without any problems.

Did you try running the Geo database repair utility? To check your port forwarding, go to http://portforward.com. They have excellent info for many routers and Geovision apps. Save yourself some money.

My first recommendation would be to at least double your RAM. 2GB was fine for earlier versions (8.2 and below) but 8.31 and .32 would put a strain on it. Most of our systems have 8GB but of course they're hybrids or NVR's.

What i the configuration of your servers? What version XP are you using? We have 20 something systems installed running 8.31 and 8.32 and haven't experienced any problems, yet. The only changes we've made was using XP Pro instead of Home and boosting memory as was recommended to us.

For Geovision 8.3x, just use there Fast Backup and Restore utility. Saves a lot of reconfiguring is something happens.

What types of PTZ cameras are you using? Do they support multiple protocols as some do? My thought, crazy as it might be, would be to configure one controller to use one protocol and the other controller the second protocol. Also, does this controller allow you to set different camera numbers to the actual camera address?

You're correct, vulture, the problem appears to be updater program and since you can reestablish a connection after rebooting your router, it would appear its updater program is not up to the task. If your ISP was blocking the http port you would not have been able to access your DVR over the net as you stated in your first post. Also I as unable to find any info on the model router you listed on the Belkin website. As for your DVR, there's no guarantee that it's updater is any better. Haven't been able to find much info on it. For future reference, if you purchase a DVR and require remote access, make sure it has that capability, either its own DDNS service like dipmap for Geovision or a working DYNDNS updater program. The only other option left is to buy a cheap netbook computer, attach it to your router and download the updater program from DYNDNS or whomever and let it handle the updates.

All the Geovision and Dynacolor DVR's we have installed run their own or DYNDNS updater programs behind the router without difficulty. We never use the router's updater. Just assign a static IP to your DVR. In the router, disable DDNS. Under Firewall, select Virtual Server and enter the DVR's static IP and the private and public ports that your DVR requires (at minimum 80 unless your unit uses something else). Check Enable then reboot your router and you should be good to go.

I would first disable the router's DDNS updater program and just use the DVR's updater. You mentioned there are no other computers on this router so just let the DVR request the IP updates for itself. It's been my experience that some routers update programs do a poor job with DYNDNS. An option might be to go to the Belkin website and seeing if there are any firmware updates for your particular router or check their support page on this issue.

What model DVR are you using? Does the DVR have it's own DYNDNS updater program? If so, try using it verses the router's update program.

Is there any way you can have their IT guy disable QoS in the router to test its effect. I think once he's done that you won't have your latency issues with the DVR. Usually QoS is used when bandwidth is limited to allow resources to share more efficiently. There may also be an issue with the other PC on the network. It may have programs running which are loading it down. Is it shut off at the end of the day when you've tried accessing the DVR?

Silly question(s) or maybe I missed it: What version Windows are you running on this PC? XP, Vista or 7? I've had instances with Vista and 7 where I add something to "Trusted Sites" select "Low" level or made changes to some of the settings, hit OK and Apply only to go back and see it defaulted back to Medium. Had to disable UAC to get the changes to stick. Funny thing is it only happened when adding that first site to "Trusted Sites". May be worth a look.

Sounds like a problem with your video board driver. Check the web to see if you have the latest and greatest driver. Where are you located? Is the board configured for NTSC or PAL?