CCTV / BT HOME HUB / Networking Nightmare.

CCTV / BT HOME HUB / Networking Nightmare.

Author
Discussion

croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
So i've just put in a CCTV system that has the ability to be viewed remotely...all sounds good doesnt it?

Except for some reason I cannot fathom how to make it work despite following the very limited user manual and googles assistance.

It is a Sannce 960 system and their preffered app is XMEYE which links via a QR code - which i've managed and had working for a brief moment yesterday.

However now it would appear our router has decided it doesnt like the idea of this and the CCTV box states it has no signal.

The CCTV system has the following information / options





I'm not sure if the issue is i'm using a wireless ethernet connector? or simply i dont know what im doing.

Help me PH...You're my only hope

ging84

8,827 posts

145 months

Tuesday 24th May 2016
quotequote all
Based on those screens i don't think many people would know what they are doing

The tick box for dhcp enable is ambiguous

Is it a dhcp client or servers?
For client you would expect the network setting to disappear
So it could be a dhcp server so you can connect something like a laptop directly to the cctv box

I would trying unticking dhcp
and/or
leaving dhcp ticked but removing the network address, subnet mask, gateway and dns

megaphone

10,694 posts

250 months

Tuesday 24th May 2016
quotequote all


OP have you opened/forwarded any ports on the router? Most of these systems need port forwarding to allow them to get out of your internal network. Do the instructions talk about port forwarding?

Edited by megaphone on Tuesday 24th May 09:46

marshalla

15,902 posts

200 months

Tuesday 24th May 2016
quotequote all
OP, am I right in thinking that this is a "cloud" CCTV system ? If so, one obvious problem is that push.umeye.cn (bottom of your first screen) doesn't have a valid entry in DNS so it can't be communicated with. Your "cloud" entry also looks like there's a problem finding somewhere to communicate with.

If I'm right, that means that the cloud host is inaccessible so your video is going nowhere.

There's some possibly relevant troubleshooting info here : http://www.ildvr-usa.com/support/how-do-i-setup-dv...


Edited by marshalla on Tuesday 24th May 09:27

croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
Unfortunately the instructions have been written by a 12 year old Taiwanese child it would seem.

It is very blaise about it and says simply plug in , scan the QR code and view via the cloud.

Which is fine if you can actually access said cloud.

The router gives me this info.



Looking at that screen grab it doesnt seem to acknowledge any ethernet link despite it being run through a TP Link Wireless Ethernet Adaptor.

croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
marshalla said:
OP, am I right in thinking that this is a "cloud" CCTV system ? If so, one obvious problem is that push.umeye.cn (bottom of your first screen) doesn't have a valid entry in DNS so it can't be communicated with. Your "cloud" entry also looks like there's a problem finding somewhere to communicate with.

If I'm right, that means that the cloud host is inaccessible so your video is going nowhere.

There's some possibly relevant troubleshooting info here : http://www.ildvr-usa.com/support/how-do-i-setup-dv...


Edited by marshalla on Tuesday 24th May 09:27
I have already set up a DHCP fixed IP via NoIP so am i a step closer?

marshalla

15,902 posts

200 months

Tuesday 24th May 2016
quotequote all
croakey said:
marshalla said:
OP, am I right in thinking that this is a "cloud" CCTV system ? If so, one obvious problem is that push.umeye.cn (bottom of your first screen) doesn't have a valid entry in DNS so it can't be communicated with. Your "cloud" entry also looks like there's a problem finding somewhere to communicate with.

If I'm right, that means that the cloud host is inaccessible so your video is going nowhere.

There's some possibly relevant troubleshooting info here : http://www.ildvr-usa.com/support/how-do-i-setup-dv...


Edited by marshalla on Tuesday 24th May 09:27
I have already set up a DHCP fixed IP via NoIP so am i a step closer?
No, because the problem is at the other end. The cloud server that you need to communicate with doesn't seem to exist at the moment.

ETA: attempting to access umeye.cn produces this : (translated through google) https://translate.google.com/translate?sl=auto&amp...

and attempting to access www.umeye.cn produces nothing. Someone hasn't paid their bills ? Or has upset the Chinese government ?

Edited by marshalla on Tuesday 24th May 09:38

croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
Apologise for my naievity but what you're saying is that the issue is the Cloud system and nothing my end? How would I go about resolving this.

I'm not a technophobe - however this is a step beyond me!

marshalla

15,902 posts

200 months

Tuesday 24th May 2016
quotequote all
croakey said:
Apologise for my naievity but what you're saying is that the issue is the Cloud system and nothing my end? How would I go about resolving this.

I'm not a technophobe - however this is a step beyond me!
Yes. You probably can't. Return the kit as unusable and get a system that doesn't rely on Chinese hosting.

megaphone

10,694 posts

250 months

Tuesday 24th May 2016
quotequote all
croakey said:
Unfortunately the instructions have been written by a 12 year old Taiwanese child it would seem.

It is very blaise about it and says simply plug in , scan the QR code and view via the cloud.

Which is fine if you can actually access said cloud.

The router gives me this info.



Looking at that screen grab it doesn't seem to acknowledge any ethernet link despite it being run through a TP Link Wireless Ethernet Adaptor.
I'd get rid of the TP Link adaptor, until you've proved the system, run a cable back to the router.

Looking at the IPs of your other kit that's online, the DHCP IP addresses start at 192.168.1.100 , so it looks like your DVR is not getting an IP.

marshalla

15,902 posts

200 months

Tuesday 24th May 2016
quotequote all
megaphone said:
Looking at the IPs of your other kit that's online, the DHCP IP addresses start at 192.168.100.xxx ,
They start 192.168.1.

croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
megaphone said:
I'd get rid of the TP Link adaptor, until you've proved the system, run a cable back to the router.

Looking at the IPs of your other kit that's online, the DHCP IP addresses start at 192.168.1.100 , so it looks like your DVR is not getting an IP.
I've got a 30m lenght of ethernet in the post today so will try this before throwing it all into the garden and setting it on fire.

megaphone

10,694 posts

250 months

Tuesday 24th May 2016
quotequote all
marshalla said:
megaphone said:
Looking at the IPs of your other kit that's online, the DHCP IP addresses start at 192.168.100.xxx ,
They start 192.168.1.
Typo. I've edited my post, they appear to start at 192.168.1.100

TonyRPH

12,963 posts

167 months

Tuesday 24th May 2016
quotequote all
OP a couple of questions:

The CCTV has an IP address of 192.168.1.10 - did you set this yourself?

If you go to a DOS prompt on a PC, can you ping 192.168.1.10 ?

From your description, you have a wireless card plugged into the CCTV - is this correct?

If so, which wireless card is it, and how specifically is it connected?


croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
TonyRPH said:
OP a couple of questions:

The CCTV has an IP address of 192.168.1.10 - did you set this yourself?

If you go to a DOS prompt on a PC, can you ping 192.168.1.10 ?

From your description, you have a wireless card plugged into the CCTV - is this correct?

If so, which wireless card is it, and how specifically is it connected?
I'll answer as best i can...

I have not altered any of the setttings on the DVR.

I'll have to google how do ping via DOS.

It wanted an ethernet connection - Its a fair distance from router to the DVR so i sought advice and bought a TP Link Ethernet wireless adaptor. I understand it works by utilising the houses internal electrical circuits to send data signals.

croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
croakey said:
TonyRPH said:
OP a couple of questions:

The CCTV has an IP address of 192.168.1.10 - did you set this yourself?

If you go to a DOS prompt on a PC, can you ping 192.168.1.10 ?

From your description, you have a wireless card plugged into the CCTV - is this correct?

If so, which wireless card is it, and how specifically is it connected?
I'll answer as best i can...

I have not altered any of the setttings on the DVR.

I'll have to google how do ping via DOS.

It wanted an ethernet connection - Its a fair distance from router to the DVR so i sought advice and bought a TP Link Ethernet wireless adaptor. I understand it works by utilising the houses internal electrical circuits to send data signals.
Result of Ping on 192.168.1.10 is DESTINATION HOST UNREACHABLE.

TonyRPH

12,963 posts

167 months

Tuesday 24th May 2016
quotequote all
Ah I understand now.

At a guess the CCTV has obtained an IP address from your router, however we can't be sure of that, without knowing your exact router configuration, although it's unlikely the CCTV cam preset with an IP.

To do a ping...

Press the Windows key and 'R' at the same time to bring up the "run" box on your PC.

In the run box, type cmd and click 'Ok' or press enter.

You should be presented with a black window, with a bit of text in the top left corner, which you can ignore.

Type "ping 192.168.1.1" and press enter.

You will either get:

Pinging 192.168.1.10 with 32 bytes of data:
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
(this will be repeated 4 times)

OR:

Pinging 192.168.1.10 with 32 bytes of data:
Reply from 192.168.1.10: Destination host unreachable.*
(this will be repeated 4 times)

  • note - the reply might come from your router which I believe to be either 192.168.1.1 or 192.168.1.254
Run box:



Dos prompt: (with instructions in red)



Edited by TonyRPH on Tuesday 24th May 10:41

Rutter

2,070 posts

205 months

Tuesday 24th May 2016
quotequote all
When you open this page on a web browser is your address 192.168.1.1 or 192.168.1.254 as is the default for home hubs?



If its 192.168.1.254 then you might have to change your default gateway on the cctv system to reflect this, but i'd imagine you will need to do some port forwarding as well.

croakey

Original Poster:

1,193 posts

187 months

Tuesday 24th May 2016
quotequote all
192.168.1.254 appears to be the IP required to access the router settings.




Edited by croakey on Tuesday 24th May 10:45

TonyRPH

12,963 posts

167 months

Tuesday 24th May 2016
quotequote all
OP - do yourself a favour and remove those addresses above: (anything that doesn't begin with 192)



Edited by TonyRPH on Tuesday 24th May 10:47


Edited by TonyRPH on Tuesday 24th May 10:47