Accesing IP Camera over Internet on Nighthawk D7000v2

Scorcher00 · ‎2019-05-16

Hello, I am after some help/advice on setting up my D7000v2 Nighthawk to work with a IP Camera (dBPower).I am hoping someone can provide step-by-step instructions on how to achieve this.

I previously used a BT Homehub 5 with BT Fibre on which the Wifi was killed by a recent firmware update (a common problem that I see on various forums without any fixes). So I got a Netgear D7000v2 Nighthawk to get away from using BT router.

The Nighthawk was a breeze to initially set up but I am now having problems in getting the IP Camera set up (which was easier to do on a Homehub).

I have set up the DDNS using a Netgear/NoIP DDNS name (the name has resolved my router's Internet IP address) and added the IP Camera's static IP (192.168.1.100) and port (888) to the Port Forwarding and Port Triggering sections (wasn't sure if both were needed). I can now see the camera on my internal devices but not on external internet devices, nor can I ping the DDNS name or IP Camera from external Internet devices.

I am sure that this can be done but I think I am missing something.

I would appreciate any help / guidance.

Cheers 🙂

antinode · ‎2019-05-16

> [...] D7000v2 [...]

Firmware version?

> [...] a IP Camera (dBPower) [...]

Not a very detailed description of anything. Has it a model number?

Can you talk to the camera from a system on your LAN, using the camera's
LAN IP address? (How, exactly? Web browser? App? Other?)

> [...] So I got a Netgear D7000v2 Nighthawk to get away from using BT
> router.

Is that a DSL or Ethernet connection to the D7000v2? Any other
equipment between it and your ISP?

> I have set up the DDNS using a Netgear/NoIP DDNS name (the name has
> resolved my router's Internet IP address) [...]

Any hints on that address? ("a.b" of "a.b.c.d" would be enough of
your public IP address to satisfy my curiosity.)

> [...] added the IP Camera's static IP (192.168.1.100) [...]

True _static_ (configured on the camera itself) or reserved dynamic
(configured on the (DHCP server on the) (modem+)router?

> [...] and port (888) to the Port Forwarding and Port Triggering
> sections (wasn't sure if both were needed). [...]

Port forwarding should be plenty. I'd clear out any port triggering
stuff. What is your actual port-forwarding rule? (Copy+paste is your
friend.)

> [...] I can now see the camera on my internal devices [...]

"see"? How, exactly?

> [...] but not on external internet devices, [...]

Actual error message?

> [...] nor can I ping the DDNS name or IP Camera from external Internet
> devices.

"ping" doesn't deal with a port, so I wouldn't expect to be able to
"ping" the camera, only the (modem+)router itself, and then only if
you've enabled that option: ADVANCED > Setup > WAN Setup : Respond to
Ping on Internet Port.

The usual problems with this stuff are:

1. Wrong external IP address (different from the port-forwarding
router's WAN/Internet IP address). (An intermediate NAT router, for
example, could cause this.)

2. Bad port-forwarding rule (wrong port(s), wrong target address --
including a wandering target).

3. Server not listening on the port-forwarding target system.

4. External influences: ISP blocking, other firewalls, ...

Note: Various reports suggest that NAT loopback does not work on a
D7000v2, so if you're actually on your LAN, but using the router's
WAN/Internet IP address, then you could see a failure, but things might
work if you were actually running the test from the outside world.

https://community.netgear.com/t5/x/x/m-p/1751841

View solution in original post

antinode · ‎2019-05-16