Is it normal to heave two IP entries for the NVR?
- Thread starter JPmedia
- Start date
If you notice, the first entry in the top list is the correct IP series (192.169.X.X) and the 11th entry is not part of my LAN IP series (192.168.X.X). Is this the default address? If so, why would it be listed as well as the one being used for my LAN IP series?
bigredfish
Known around here
No, and I’ve never seen cameras with port 35000 either ?
And cameras with port 37777 usually indicates they were manually added or are on the LAN, but those seem to have NVR PoE switch addresses (10.1.1.x)
And cameras with port 37777 usually indicates they were manually added or are on the LAN, but those seem to have NVR PoE switch addresses (10.1.1.x)
bigredfish
Known around here
None of those addresses (192.x.x.x or 10.1.x.x) need to be hidden. Everyone has those, they are internal to your network and not routable over the interwebs
bigredfish
Known around here
Yes. The 35000 port appears as part of the NVR device info, so maybe it's part of the DDNS Lorex provides?
bigredfish
Known around here
I see. I wonder why the 192.168.XX.108 is an IP address on the device list as it is not in the IP range of the network. The 192.169.XXX.XXX IP address for the same NVR is.
And it's not 192.168.1.108. The 3rd set of numbers is not 1
Between this and your comments/concerns on another thread, you need to replace this NVR with the new one you have sitting around.
You are spending enough time screwing around with this that the other one could have been set up by now!
My neighbors Lorex only had 10.x.x.x cameras for cameras connected to the NVR ports.
That device N882A6 comes back as a NVR, so it is either this NVR or perhaps it is hacked and another is connected somehow or some weird entry from trying different things in the past.
As mentioned, no need to block out the LAN addresses.
You can list the private LAN IP addresses as it does not tell anyone anything - they are the same as everyone else.
The IP address of your service provider for your WAN is what you don't provide...Everything on the inside past the modem is fine to put out.
Everything on the inside, the local LAN will fall under these ranges and you are not telling anyone anything about how to hack your system because these ranges are reserved for the "home side" of the service so every home internally will be within this same range):
10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255
You are spending enough time screwing around with this that the other one could have been set up by now!
My neighbors Lorex only had 10.x.x.x cameras for cameras connected to the NVR ports.
That device N882A6 comes back as a NVR, so it is either this NVR or perhaps it is hacked and another is connected somehow or some weird entry from trying different things in the past.
As mentioned, no need to block out the LAN addresses.
You can list the private LAN IP addresses as it does not tell anyone anything - they are the same as everyone else.
The IP address of your service provider for your WAN is what you don't provide...Everything on the inside past the modem is fine to put out.
Everything on the inside, the local LAN will fall under these ranges and you are not telling anyone anything about how to hack your system because these ranges are reserved for the "home side" of the service so every home internally will be within this same range):
10.0.0.0 – 10.255.255.255
172.16.0.0 – 172.31.255.255
192.168.0.0 – 192.168.255.255
I think I might be procrastinating because I am trying to setup all the cameras before the switchover. I know how to access the live view from my phone to align the cameras as I install them with the Lorex Cloud app.
Along with the installation of the NVR, every camera has a different password, and all cameras currently have IP addresses assigned by the Lorex NVR. I'm worried about having to reset all of the cameras as the turrets will need to come down to access the reset button.
The other is the proper setup of the NVR, installing, connecting and configuring the mobile and desktop apps. It could be time consuming learning a new device and interface. Takes me a little longer to understand some things
bigredfish
Known around here
You’re likely making the inevitable switch worse
Right out of the shoot, cameras using an NVR PoE switch do not need separate passwords. Zero benefit. But it will make adding them to your new NVR that much more time consuming. The port differences may force you to factory reset all of them.
I’d stop and bite the bullet now
Right out of the shoot, cameras using an NVR PoE switch do not need separate passwords. Zero benefit. But it will make adding them to your new NVR that much more time consuming. The port differences may force you to factory reset all of them.
I’d stop and bite the bullet now
I can change all the passwords from the camera GUIs, but the port number situation may be another story
What is the port number used by Dahua NVRs?
And can the cameras be reset from the GUI? Like, can I disconnect each camera from the Lorex NVR and connect them directly to my laptop one at a time and reset them?
You have no idea what crippling effects the Lorex NVR could be doing to the cameras that will then carry over to the new NVR.
As an example, my neighbors Lorex kept cutting the bitrate to 4192 regardless of what he set it up in the camera GUI. That carried over and he had to go in and make changes to each camera.
As I told you in your other thread, if you haven't done anything crazy and did a normal install, when you swap out NVRs, the cameras will take on new IPs and the username/password of the new NVR.
Now if you tried to get cute and made each camera a separate password thinking it would make it more secure, well all you did was create more work for yourself as that has zero benefit as everything is behind the NVR.
As I mentioned, I just went thru this switch with my neighbor from Lorex to Andy's NVR and 16 cameras and it was under an hour. The longest part was waiting for the camera to boot up.
You don't need to be concerned with the port numbers unless you effed it up dinking around setting up the Lorex system. If you simply plugged them in and let the NVR handle it, it is easy.
Literally it is this easy:
Unplug Lorex NVR and unplug all the cameras.
Plug in Andy's NVR and initialize it - best to make it same user/password as your old one.
Plug a camera into port 1.
Wait for it to show up on the NVR.
Plug a camera into port 2.
Wait for it to show up on the NVR.
Repeat.
Download DMSS app.
Scan Serial Number
Then we had to go into each camera to see what Lorex Effed up with its throttling. This is the step you are making worse by trying to get the cameras going first.
As an example, my neighbors Lorex kept cutting the bitrate to 4192 regardless of what he set it up in the camera GUI. That carried over and he had to go in and make changes to each camera.
As I told you in your other thread, if you haven't done anything crazy and did a normal install, when you swap out NVRs, the cameras will take on new IPs and the username/password of the new NVR.
Now if you tried to get cute and made each camera a separate password thinking it would make it more secure, well all you did was create more work for yourself as that has zero benefit as everything is behind the NVR.
As I mentioned, I just went thru this switch with my neighbor from Lorex to Andy's NVR and 16 cameras and it was under an hour. The longest part was waiting for the camera to boot up.
You don't need to be concerned with the port numbers unless you effed it up dinking around setting up the Lorex system. If you simply plugged them in and let the NVR handle it, it is easy.
Literally it is this easy:
Unplug Lorex NVR and unplug all the cameras.
Plug in Andy's NVR and initialize it - best to make it same user/password as your old one.
Plug a camera into port 1.
Wait for it to show up on the NVR.
Plug a camera into port 2.
Wait for it to show up on the NVR.
Repeat.
Download DMSS app.
Scan Serial Number
Then we had to go into each camera to see what Lorex Effed up with its throttling. This is the step you are making worse by trying to get the cameras going first.
bigredfish
Known around here
^^^
Yup
Though FWIW I use the serial number of the NVR instead of the QR code when connecting it to DMSS
Yup
Though FWIW I use the serial number of the NVR instead of the QR code when connecting it to DMSS
...and no need to go to the trouble of redacting private (non-public) IP addresses such as 192.168.XXX.XXX, as we all have 'em. My fiber router is 192.168.200.1, my Blue Iris server PC is 192.168.200.250.
It's the WAN (public) IP that should not be posted. It's the one that is revealed when you go to whatsmyip.org
It's the WAN (public) IP that should not be posted. It's the one that is revealed when you go to whatsmyip.org
Sheesh, you don't know until you know. My intentions were good. Sometimes I'm stubborn in my process
By the way, when I initialized the Dahua NVR after doing the updates, I chose NOT to enable P2P. How do I enable it to use the DMSS app?
I thought I was being careful. Didn't want to inadvertently post info I shouldn't....and no need to go to the trouble of redacting private (non-public) IP addresses such as 192.168.XXX.XXX, as we all have 'em. My fiber router is 192.168.200.1, my Blue Iris server PC is 192.168.200.250.
It's the WAN (public) IP that should not be posted. It's the one that is revealed when you go to whatsmyip.org
