House Surveillance

[Nightrider]

For the specialists:

4 cams via cable connected to DVR, DVR connected to WAG200G router via ethernet.
DYNDNS used to have static IP.
This IP points to a webpage.

DVR has internal IP 192.168.1.220
Router has internal IP 192.168.1.1
DHCP allows IP range 192.168.1.100 - 221
DVR set for port 80, FTP / HTTP enabled
Router set to direct DVR to port 80
DYNDNS points towards IP provided by service provider.

On TV I can see all cams crisp clear.
On every computer logging into home network a direct access to the DVR IP or the website via DYNDNS works as advertised, means even through internet.

With same notebook from home, or any other comuter anywhere on this planet, when not logged-in to home network, any browser shows the log-in page as set-up through the DVR, the username and password are accepted and basic frame surrounding the 4 cam pictures as designed in DVR bios-based webpage shows; however, the 4 pics (*.jpg) are simply a blue background. No cam pictures.

The installation company has given up....guess I did not select the best one; luckily payment is not yet completed.

Anyone out here who has an idea to get this system going?

[green granite]

Don't know but this might help.
http://www.mionet.com/downloads/MioNetManual.pdf

[Saab Dastard]

Your description is far from clear!

It may be that a packet sniffer (etherpeek or similar) on a) the internal network and b) the outside will be required to see where the failure is occurring.

It may be that a port or ports in addition to port 80 need to be open on the firewall, or configured to forward to / from the DVR.

BTW, if the DVR is assigned the fixed address of 192.168.1.220, then it is foolish to include it in the DHCP range (192.168.1.100 - 221), although the likelihood of the address being assigned is very low!

SD