Search results

Aha! that would definitely be a very eventful group to be apart of, I can’t imagine the stories.. here’s to many, many more week afters my friend. All the best, Tony!

Man, oh man I feel like the biggest schmuck right now So the position of the NVR in my house is very restrictive, and I finally had time to disconnect everything so I could move it to the Netgear room and check out what’s going on so I could report back to you. I move it there and this is my...

Silly me, couldn’t I just unplug the NVR and take it to the Nighthawk room to troubleshoot? The cameras just won’t be plugged in though since the cables are short and protruding from the wall on the other side of the house.

No, in Australia we have/had a disastrous internet ‘improvement’ rollout in the last decade and the way my internet is designed makes it impossible for them to be connected since they’re on other ends of the house for a reason /:

On the SADP client, it shows me three different online devices, one being the NVR and the 2 others being IP cameras that don't exist (they are configured on the NVR but no idea why or how). The 2 IP cameras when I clicked on their IP used to take me to the webGUI (even though the camera feed...

I had already done that earlier to no avail? Or am I configuring the wrong setting? In the NVR network settings this is called IPv4 address, or do I have to change the internal NIC to 192.168.1.109 and the IPv4 address to something else? Sorry for the confusion.

Yes I can, that's how I configured the settings above, where would I have to go and which settings would I have to change to achieve getting the NVR LAN onto the same subnet?

Als also, in the SADP tool it says the NVR IP address is 192.168.2.xx Hmmm

The settings on my Network tab on the Hikvision are as follows: I assigned the IPv4 address to 192.168.1.109 (my net gear DHCP pool is 192.168.1.1 - 192.168.1.100 ) The IPv4 Subnet mask is 255.255.255.0 And the IPv4 Default Gateway is 192.168.1.1 , just like my Netgear LAN IP. The MTU(Bytes) is...

Yes, it does.

Ah wow, that actually makes me very happy to hear; I'm very glad :)) After pinging both they gave back similar results. The netgear ip presented with: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms...

I checked now, the Nighthawk router LAN IP is 192.168.1.1 I just set the NVR IPv4 default gateway to the same. The TP-LINK client is 192.168.1.16 My pc's one is 192.168.1.5 Where should I go from here and which settings should I tweak? Also I just saw your tagline that you were a Vietnam vet...

Ah I see. I feel like we’re getting so close now! I’ll be home from work in about 8ish hours and I’ll check and reply with the info. Thank you so much for helping me through this you know a lot about this stuff.

My current situation now: The TP-Link is configured as a client with a static IP address, I have this IP set as the IPv4 default gateway in the NVR settings. For the IPv4 I have an Ip that is outside of the DHCP pool assigned by my Netgear router. Where should I go from here?

The NVR is set for DHCP however assigns the IP 169.254.255.254 which means something is off hey? Also, after assigning the TP-Link a static IP and disabling DHCP, I am unable to return to the TP-Link configuration screen no matter what IP I try (be it the new or old one). If I connect the...

I had slaved the TP-Link to the Netgear wifi from the beginning, so that had been done. In which way do you mean how is my NVR's LAN configured (i am so sorry for the most definitely stupid questions)

Hi, thank you so much for the reply :) In the line I quoted, what do you mean by this; how would I be able to check it? Also the TP-LINK is currently set to client mode but DHCP is enabled so I'll disable it now, "assign it a unique static ip in the same subnet as the router and have it slaved"...

Edit: The issue was finally resolved! Only thanks to the help of the brilliant and kind TonyR. It was because partially the Ethernet wasn’t plugged in the right port, yeah…. But it wouldn’t have worked either way if not configured properly, which Tony helped tremendously with; read through the...