Dipmap Multiple PC's

[3RDIGLBL 0]

Hey Folks, got a customer with two Geovision PC's. They have 32 cameras and and two computers each housing a 16 channel card. I guess they had this all set up before you could piggy back two cards in one system.

 

Anyhow. They want to remote in to there PC but since they have two how would they go about doing this. Should I be using dipmap like I've done in the past? Maybe set it up on separate parts and the customer would have to use dipmap with a port number such as dipmap.com:8080 for PC 1 and dipmap.com:8081 for PC two?

 

Thanks

[rory 0]

Change the command ports and the data ports, and the audio ports if you use audio.

if you are going to use a web browser then also change the HTTP ports.

Same applies to the Remote View Log etc ports. Depending on what server version you are using, in the newer 8.3+ versions at least there is menu section that lets you change all the ports in one window. OR if you are adventurous you can go into the registry as it is all there also.

 

You can use DipMap or DynDns or Static .. same thing applies.

If in the browser put a different HTTP port after the IP, if in a client app the Command, Data, and Audio ports apply, Http port not needed. However I would just change the HTTP ports anyway just for good measure.

[3RDIGLBL 0]

Thanks Rory. Everything worked perfectly.

 

One issue the customer is having is the spot out. It all of a sudden stopped working. I verified all settings are correct and rebooted the DVR. Still no go. I swapped the spot out with the second PC and the spot out was working so I believe the spot out circuit on one computer is bad.

 

What I would like to do is swap the two 1480 cards around so that way the spot out will be working again to display the cameras he cares about.

 

Question, can I swap the 1480 cards with no issue? I would assume the software settings and everything should remain the same but I'm not sure if there is a hardware identifier in the software that may see a change and I really mess up his system. Should, I hope be an easy swap but I don't want to take a chance.

 

The software running on there is 8.12!

 

Thanks

[rory 0]

The main software will remain the same but you will MAY have to reinstall the driver depending on whether the cards are the same versions or not. If they are the same version cards, the ID will be different but it should still find the driver and install it automatically as it was not removed. Worst case scenario, cancel the default hardware install wizard popups and then run the Geo Driver installer.

 

BTW do you mean the spot out on the combo card itself?

If so just try uninstalling the drivers and then reinstalling again.

[3RDIGLBL 0]

Ya the spot out on the combo card seemed to have flaked out. Not sure why but there is no error or anything posted. The software seems to think it is working but there is no video coming out of it. Connecting the TV to the other PC works just fine.

 

Customer can't locate his cd. I will have to have him dig around because I don't want to do a full system upgrade on it as it is all tied into his grocery store POS computer. If I mess that up it could be more costly to him then just simply getting his spot out working.

 

Thanks again Rory. Not sure about the card versions but since they were both built at the same time I will assume they are the identical version.

[rory 0]

you could register for free at one of our forum member sites, www.ezcctv.com, and download any of the geo software versions there, up to and including 8.33. They have the drivers also. Ask the client to check the version if he can, it will be one of the menu items, as need that info before installing, or download a bunch of them and just use it when you know which it is.

 

I had a similar issue with a client but cant for the life of me remember how i fixed it as it was a year or so ago .. might have just been a driver reinstall though, or another thing to do is disable the spot out feature .. restart everything .. reenable it .. then restart again .. and see if it works. Might be a corrupt or damaged registry value or ini file (it uses one of those, dont recall off hand which exactly).