Set up Q-See QT5816 for remote access
I had to replace an older QC-series DVR with a new QT5816. I'm having a lot of trouble getting web access to see the cameras. The older system provided web-based monitoring with no troubles.
Here is the setup:
Zyxel ADSL Modem at 192.168.0.1 with a static public address - so no need for DynDNS.
QT5816 at 192.168.0.2 (static)
I have tried using only UPnP but the modem didn't seem to hold the settings.
I have the QT5816 http port set to 85 and the standard data port of 6036.
The modem seemed to drop the port 85 setting in UPnP.
The original used port 80 and I'm not sure if it used UPnP mode or Port forwarding.
Next I tried port forwarding 85 and 6036.
Some things work and some things don't work.
Super Cam works on my iPhone.
addressing the dvr at the modem's static public address plus :85 ends up with
[ipaddress]:85\WebClient.h
Some browsers work and some don't.
Some only want to search and not just go to the address.... etc.
I need to make this work reliably.
Update: I've attached a diagram just to make things clear.
I have changed the HTTP port to 80 and have forwarded it in the modem/router to the camera DVR.
This seems to work more reliably but I'm getting reports that phone monitoring is flaky.
Analog-Camera-Network-Diagram.pdf
Here is the setup:
Zyxel ADSL Modem at 192.168.0.1 with a static public address - so no need for DynDNS.
QT5816 at 192.168.0.2 (static)
I have tried using only UPnP but the modem didn't seem to hold the settings.
I have the QT5816 http port set to 85 and the standard data port of 6036.
The modem seemed to drop the port 85 setting in UPnP.
The original used port 80 and I'm not sure if it used UPnP mode or Port forwarding.
Next I tried port forwarding 85 and 6036.
Some things work and some things don't work.
Super Cam works on my iPhone.
addressing the dvr at the modem's static public address plus :85 ends up with
[ipaddress]:85\WebClient.h
Some browsers work and some don't.
Some only want to search and not just go to the address.... etc.
I need to make this work reliably.
Update: I've attached a diagram just to make things clear.
I have changed the HTTP port to 80 and have forwarded it in the modem/router to the camera DVR.
This seems to work more reliably but I'm getting reports that phone monitoring is flaky.
Analog-Camera-Network-Diagram.pdf
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
as I said: .... with a static public address - so no need for DynDNS. That means no addressing by any name.
The DVR loads a client onto monitoring computers. Google Chrome isn't compatible.
The phone monitoring is for the cameras, not involving the Zyxel.
The DVR loads a client onto monitoring computers. Google Chrome isn't compatible.
The phone monitoring is for the cameras, not involving the Zyxel.
I think we are talking past each other, where did you see a recommendation for dyndns?
what is the issue that you would like further assistance with?
what is the issue that you would like further assistance with?
ASKER
Arnold: You said:
In order to address your DVR externally by name, you have to have a domain on which you can create a host that will be referenced in http://somehost.yourdomain.com:85Depending on more details to the context (such as no static public IP address), this often means the need for dyndns which will then allow addressing by name. I had not said anything about addressing by name otherwise. So, sorry if I jumped to a conclusion that wasn't warranted.
ASKER
Thanks all!
ASKER
The answer from Q-See support tells it all.
ASKER