Hello all,
I’m looking for some insight or guidance on a multi-building Lorex NVR setup, and I’ll keep the explanation as clear and concise as possible.
We have two buildings, each with its own Lorex Elite Series 4K 32-channel NVR. Each building houses 16 cameras, for a total of 32 across both locations. The buildings sit across the street from one another, so running additional cabling between them isn’t feasible. However, we do have a fiber optic connection between the two buildings, which ties both NVRs into the same local network via access points connected to a central router.
Here’s the interesting part: While setting up the NVR in Building 2, one of the cameras physically connected to NVR #1 in Building 1 appeared in the device search and could be added to NVR #2. That camera is now visible on both NVRs.
After some investigation, I noticed that the camera which successfully shows up on both NVRs is assigned a 192.168.x.x IP address, unlike all the other cameras, which are on a 10.1.x.x subnet—presumably assigned by NVR #1’s internal DHCP for its PoE ports.
This leads to my goal:
We would like to display all 32 cameras on monitors in both buildings, meaning each NVR would ideally have access to all 32 cameras. I know this should be impossible using the NVR PoE ports alone, since those usually assign a private subnet and isolate traffic. But since one camera has somehow retained or received a 192.168.x.x LAN IP and is visible across the network, I’m hoping there's a way to replicate this behavior.
So far, I’ve tried the following without success:
Disconnecting and reconnecting cameras
Resetting NVRs
Switching network settings to static
Attempting to reassign IPs via the NVR interface
It seems that once a camera is plugged into the NVR’s PoE port, its IP is locked into that private subnet and not visible to other devices on the LAN. However, the fact that one camera is clearly an exception has me wondering if this was a fluke, a static IP config that stuck, or a hint at a possible solution.
My question is:
Has anyone successfully shared cameras across two Lorex NVRs when the cameras are plugged directly into the NVRs’ PoE ports?
Or better yet—can anyone explain how I might replicate this 192.168.x.x IP assignment for the rest of the cameras so both NVRs can see all devices?
Any insight or suggestions would be greatly appreciated. Thanks in advance!
I’m looking for some insight or guidance on a multi-building Lorex NVR setup, and I’ll keep the explanation as clear and concise as possible.
We have two buildings, each with its own Lorex Elite Series 4K 32-channel NVR. Each building houses 16 cameras, for a total of 32 across both locations. The buildings sit across the street from one another, so running additional cabling between them isn’t feasible. However, we do have a fiber optic connection between the two buildings, which ties both NVRs into the same local network via access points connected to a central router.
Here’s the interesting part: While setting up the NVR in Building 2, one of the cameras physically connected to NVR #1 in Building 1 appeared in the device search and could be added to NVR #2. That camera is now visible on both NVRs.
After some investigation, I noticed that the camera which successfully shows up on both NVRs is assigned a 192.168.x.x IP address, unlike all the other cameras, which are on a 10.1.x.x subnet—presumably assigned by NVR #1’s internal DHCP for its PoE ports.
This leads to my goal:
We would like to display all 32 cameras on monitors in both buildings, meaning each NVR would ideally have access to all 32 cameras. I know this should be impossible using the NVR PoE ports alone, since those usually assign a private subnet and isolate traffic. But since one camera has somehow retained or received a 192.168.x.x LAN IP and is visible across the network, I’m hoping there's a way to replicate this behavior.
So far, I’ve tried the following without success:
Disconnecting and reconnecting cameras
Resetting NVRs
Switching network settings to static
Attempting to reassign IPs via the NVR interface
It seems that once a camera is plugged into the NVR’s PoE port, its IP is locked into that private subnet and not visible to other devices on the LAN. However, the fact that one camera is clearly an exception has me wondering if this was a fluke, a static IP config that stuck, or a hint at a possible solution.
My question is:
Has anyone successfully shared cameras across two Lorex NVRs when the cameras are plugged directly into the NVRs’ PoE ports?
Or better yet—can anyone explain how I might replicate this 192.168.x.x IP assignment for the rest of the cameras so both NVRs can see all devices?
Any insight or suggestions would be greatly appreciated. Thanks in advance!
