CCTV / BT HOME HUB / Networking Nightmare.

[Rutter]

croakey said:

192.168.1.254 appears to be the IP required to access the router settings.

In that case your default gateway fro internal devices like the CCTV will need to be 192.168.1.254 not 192.168.1.1

The other settings you have shown are for external connectivity so won't be needed by other devices on your network.

[croakey]

Rutter said:

croakey said:

192.168.1.254 appears to be the IP required to access the router settings.

However in the settings menu accessed via that IP address it provides the following details


In that case your default gateway fro internal devices like the CCTV will need to be 192.168.1.254 not 192.168.1.1

The other settings you have shown are for external connectivity so won't be needed by other devices on your network.

So through the DVR settings change its IP to 192.168.1.254?

Deleted them as per advice... and typical PH someones quoted them

Edited by croakey on Tuesday 24th May 10:49

[megaphone]

OP. I'm pretty sure your DVR is not getting an IP from the router, possibly because the TP Link adaptor is not working correctly. Can you plug a laptop/pc into the TP link via cable and check if it's getting internet? Turn off the WiFi on the laptop.

[Rutter]

croakey said:

So through the DVR settings change its IP to 192.168.1.254?

Deleted them as per advice... and typical PH someones quoted them

I deleted the quote now but you have requoted them!

In the DVR you will need to change the "gateway" address to 192.168.1.254 not the IP address of the DVR

[TonyRPH]

croakey said:

Result of Ping on 192.168.1.10 is DESTINATION HOST UNREACHABLE.

Which means that there is no connectivity between your CCTV unit and the router (which figures, as 192.168.1.10 doesn't show up as a DHCP assigned IP address in the router listing).

Try it again when you connect with a cable.

What is the model number of the TP Link device you have? I wonder if that is running it's own DHCP server, and this is where the CCTV is getting it's IP address from?

[croakey]

i'm going to run a hardwire to it later to confirm - have to wait for the plumbers to get out the way first!

This is the TP Link system

http://www.maplin.co.uk/p/tp-link-tl-pa4010kit-av5...

[TonyRPH]

I looked at the specs for the TP Link - it doesn't have a DHCP server - they are just a bridge (as you would expect for devices like this).

In your first screenshot - it's not clear (to me at least) if the "DHCP Enable" box is checked or unchecked.

Try checking / unchecking that and see what you get. It can't harm anything.

When it is working properly you should have: (in the case of your network)

IP Address: 192.168.1.1xx (where xx could be anything from 00 to 99)
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.254 << this one is important
Primary DNS: (depends on your router config but is likely to be 192.168.1.254)
Secondary DNS: (depends on your router config - no idea what it's likely to be - could even be blank - and that's ok)

The rest should stay as it is.

Try it and report back.

This assumes that your TP Link devices are working correctly - if you have a laptop with an Ethernet port, trying plugging that in to the TP Link (on the CCTV side - but NOT the CCTV!) and see if you get internet access (after disabling the wireless of course).

[marshalla]

OP- just to be sure, you've plugged in and switched on both of those TP-Link adapters, haven't you? and run a cable from one to the CCTV and from the other to your router?

And, out of curiosity, how are you producing the screen shots of the CCTV interface?

[croakey]

Haha...yes i've checked the wires are in the actual sockets.

The photos are taken on my phone of a tv i've rigged to it via a HDMI to set it up

[TonyRPH]

Actually - thinking about it - even though we're uncertain how the CCTV has got an IP address, the network address it has is correct (even if the gateway is wrong) - so it should have responded* to a ping (even with the wrong default gateway) - so it looks as though those TP-Link devices are not working properly.

• Assuming it has no built in firewall - but the error the OP reported earlier suggests it's not even on the network.

[marshalla]

TonyRPH said:

it should have responded to a ping

Not necessarily. Not everything responds to ICMP.

[TonyRPH]

marshalla said:

Not necessarily. Not everything responds to ICMP.

Ahem - yes I know this - and it looks as though I was editing my post as you posted your reply - I added - assuming it has no firewall - and of course I realise there are other reasons why it may not respond to a ping, but in this case it's fairly unlikely it's that sophisticated.

I'm willing to bet that once the OP tries a cable, it's magically start working.

[marshalla]

Back to the TP-Link homeplugs. OP - where is the CCTV unit physically located, and where is the router ?
Are they on the same ring main ?

[Woody]

I had some of those home-plug type things - utter gash, I ended up just getting a wireless USB dongle for my old desktop as the plugs seemed hit & miss as to whether they worked or not.

[croakey]

Router is in the office downstairs... Dvr is in the loft space.

Cable has arrived.

As soon as I can access the loft space I'll run a wire through the house and see what occurs!

[croakey]

so...

It would appear wired it works absolutely fine.

Reality is to run a cable properly to its location is going to be a major major pain in the arse.

I'm going to unpair and then repair the TP link things in the hope that they've just lost contact.

Other than that any other suggestions??

[croakey]

And in conclusion:

Appears the TP LINK prefers (as in will work) when it is the only thing plugged into a socket.

All working as it should.

Many many many thanks to those who assisted