Can't see CCTV DVR on network.

Hi,

I have added a security camera DVR (H264 type) to my network by connecting a LAN cable to my Asus router. The DVR is viewable locally using an attached monitor and is working ok.

My office PC is located 25metres away and I'd like to see the DVR on that. The remote PC is connected to the ASUS router indirectly with another LAN cable to an old Netgear router I set up as a switch and wireless repeater in the office.

If I look at my PC network I can 'see' the ASUS router but not the DVR connected to it. If I look at the client devices attached to the router I see the DVR listed and know it's IP address.

I'm trying to use the provided software to see the DVR output; xmeye. It simply doesn't know the DVR is there.

Any suggestions?

What's the IP address of the DVR and what's the IP address of the Office PC?

In reply to a post by BatBoy:

What's the IP address of the DVR and what's the IP address of the Office PC?

The PC is 192.168.1.3

The DVR is 192.168.1.10

So they're on the same subnet.

Is the Netgear attached to the Asus using Ethernet?

In reply to a post by BatBoy:

So they're on the same subnet.

Is the Netgear attached to the Asus using Ethernet?

Yes. it's set up using the same SSID and password as the Asus so it acts as a wireless repeater. That all seems to work ok. I'm not using the wireless here though of course.

By the way, this isn't my area of expertise in case you hadn't twigged that already!

Can you plug the ethernet cable from the ASUS into the PC instead of into the Netgear?

I could. Temporarily. What would that do?

That would rule out the Netgear as the problem, if the problem remains.

Did that and even rebooted the Asus. Hasn't made any difference.

Where does all that dust come from behind my PC?

Sorry to say that's mainly skin

How does the attached monitor connect?

The monitor local to the DVR (in a cupboard in the house away from my office) is connected with a simple video coax cable.

This any help? http://www.youtube.com/watch?v=OG9UuEaocz0

Hi again,

Thanks for the link. It's actually a vid I have lready referred to. I do everything it says but after I have added the device serial number it eventually puts a red cross on the device icon and states that it is offline. I have checked and double checked the serial number and I think it's correct. Very frustrating!

Can you ping the DVR local IP address?

What ports does the software on the DVR use and can you see any evidence of it listening on those ports?

My preference would be to ensure things are working with the DVR and PC connected to the Asus routers switch ports first, before introducing the access point into the mix.

If I log into the router and ping the DVR IP address I get the following:

PING 192.168.1.10 (192.168.1.10): 56 data bytes
64 bytes from 192.168.1.10: seq=0 ttl=64 time=0.688 ms
64 bytes from 192.168.1.10: seq=1 ttl=64 time=0.495 ms
64 bytes from 192.168.1.10: seq=2 ttl=64 time=0.452 ms
64 bytes from 192.168.1.10: seq=3 ttl=64 time=0.402 ms
64 bytes from 192.168.1.10: seq=4 ttl=64 time=0.617 ms

--- 192.168.1.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.402/0.530/0.688 ms

I looked at the DVR network setup and it was using HTTP port 80. I read somewhere that this was not ideal and followed thier example and changed it to 88. Can't say it has made any difference.

How would I know if the DVR was listening?

Can you ping that IP address from the PC?

To see if a TCP port is listening

telnet 192.168.1.10 80
or
telnet 192.168.1.10 88

It will connect and just give a blank screen but that confirms the TCP port is there and listening.

How did you "look at the DVR network setup"?

Pinged my own pc from my pc followed by pinging the DVR:



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Les>ping 192.168.1.3

Pinging 192.168.1.3 with 32 bytes of data:
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128
Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Les>ping 192.168.1.10

Pinging 192.168.1.10 with 32 bytes of data:
Reply from 192.168.1.10: bytes=32 time=1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\Users\Les>

In reply to a post by ian72:

How did you "look at the DVR network setup"?

I went to the DVR and looked at network setup on the attached screen.

Has the DVR got the correct default gateway address?

Might be handy if you paste the entire IP configuration.

In reply to a post by Samadeus:

Has the DVR got the correct default gateway address?

Might be handy if you paste the entire IP configuration.

ip address: 192.168.1.10
subnet mask 255.255.255.0
gateway 192.168.1.1
primary dns 192.168.1.1
secondary dns 8.8.8.8
media port 34567
http port 88

DHCP is not enabled.

I assume that your computer is using the same default gateway IP?

In reply to a post by Samadeus:

I assume that your computer is using the same default gateway IP?

Not sure of that. Assume so.

Looking at the router it says:

LAN - LAN IP 192.168.1.1

Subnet mask 255.255.255.0

Is that what you meant?

In reply to a post by Flint:

I looked at the DVR network setup and it was using HTTP port 80. I read somewhere that this was not ideal and followed thier example and changed it to 88. Can't say it has made any difference.

I'd say that was a mistake. You should have got the thing working over the network using the default configuration before changing anything - now you don't know if that change has stopped it working or not.

Can you open Internet Explorer and browse to http://192.168.1.10:88 please?

Does that elicit any response?

Edited by deleted (Mon 03-Nov-14 12:16:53)

Yes, it logs on ok. Good enough to get a cctv picture but not the whole GUI etc.

So it's working?

I suspect the xmeye app is being blocked by the firewall on the router, or it's unaware of the change in port.

Edited by deleted (Mon 03-Nov-14 13:07:28)

Seems you are able to access the web panel of the DVR based on other posts now.

In reply to a post by MrSaffron:

Seems you are able to access the web panel of the DVR based on other posts now.

Something still not right. If I enter the IP addresss I can see the CCTV picture but not the multiple displays and control panel that I should.

In the Myeye the first screen you get after logging in is one where 'your devices' are listed. (or not). It says:

Click "My Devices" to view config and playback,
It will download the component automatically to your computer. Please wait a moment as it will take several minitues on your first visiting time!

Well, here's the thing; I can wait ages and nothing happens. If I enter the device serial number manually it appears in the list but after thinking about it for a a minute responds by putting a red cross thrugh the icon and then stating:

Your device is offline!
� Please try the following operation:
� Check the device's Internet is connected?
� Try to reboot the Internet Router.
� Pull out the network cable of device, and then reinsert it back in.
� Check the device's power supply is connected.
� Check the LED is green.
� If you cannot access the device, please update the firmware.


I have tried all the suggestions to no avail.

I do know that the serial number is coirrect as I have entered it about 20 times from various screenshots. I even got someone else to do it.

You prob need to access it in internet explorer and install the active X gubbins that comes with it.

Even with the latest Windows and IE it will probably still work, but you'll need to add the site to trusted sites in IE and lower security settings for the trusted zone so that unsigned active X can install.


...If it is like a lot of the consumer grade ones on the market.....