Accessing two subnets under same LAN - ? bridging ?

[rfeyer]

Hi all,

first - I do believe I have a good grasp of computer use, but my LAN/ IP skills - well, usually get confused by it.

What I have - A Win7 AMD with ActionTec Router/ wireless and a Hikvision Security system NVR

the problem: My home network runs under 192.168.0.**** with the router being ****.1

The NVR has an IP assignement of 192.168.0.44 BUT
the NVR has an INTERNAL NIC assigned 192.168.254.1

The NVR does see my cameras which are directly connected to the router on the PC LAN, but I can not access any of the cameras which are directly connected tot he NVR (POE's) as they are being assigned IP addresses such as 192.168.254.**** - and again, my PC/LAN is 192.168.0.**

Is there any way to have the LAN see the cameras under the NVR's internal submask?

I did try to change the int NIC to an ip under the 192.168.0.** but it gave an error

Any help would be appreciated

 

[bill001g]

It depends how the NVR is designed. You might be able to use the ROUTE ADD command and do
ROUTE ADD 192.168.254.0 mask 255.255.255.0 192.168.0.44.

This assume the NVR can act as a router.

You are really stuck though if the NVR does not run that way. Many of these systems you must log into the box and let it access the camera on your behalf.

If you REALLY want to do this a very non standard and painful to maintain method would be to overlap the 2 networks. What you do is plug a port from the internal nic on the NVR to your router. You have now overlapped the networks. You can put a secondary IP on your PC nic card in the 192.168.254.x subnet. That is the easy part the hard part is you likely have DHCP enabled on both networks and with them connected together it will assign random addresses. Generally since you like to have fixed addresses on cameras anyway I would assign static ip in the 192.168.254.x subnet to the cameras and disable the DHCP on the NVR. It works but it is not a recommended thing to be doing just because it is hard to troubleshoot if you have issues.

 

[rfeyer]

TY VM - I will try the Route Add command - does it have to be from route, does it matter here in the cmd tree I am?

 

[rfeyer]

just read my reply and it does not make sense (multitasking)

question: in the cmd window, do I need to be at c:/ (i.e. root) or a specific place to enact the Route Add command

 

[bill001g]

I think it works anyplace. Try route print first..

I see to do route add you must run the cmd window as administrator. I guess I never see this because I have a shortcut that opens it as admin all the time

 

[rfeyer]

So I did open CMD under admin, added the line for Route ADD ***
it returned with OK, but still could not access the NVR.
two more questions befoer possibly giving up on this
1: you mentioned connecting cable to internal NIC - I have my cable connected to one of the POE ports of the NVR, is that OK?
2: You mentioned in the Route ADD command to enter 192.168.254.0, but the internal NIC is 192.168.254.1 - is that still OK?

Thanks again

 

[bill001g]

You can connect to PoE ports as long as it is really PoE and not some propriety thing. The standard 802.3af is smart enough to only provide power to device that request it.

I guess it might be confusing. The route command is telling your PC that the complete network is behind the NVR. You always use the .0 address to represent the network and from your pc view point it must use the 192.168.0.44 address since you pc is on that network. The route command is telling the PC to use the NVR as a gateway for just that subnet it will send all the other addresses to your real gateway.


If you are going the other method of connecting a cable then you must go into the interface configuration on your PC and put in a secondary address. You do not need the route ....if you were to do a route print you will see the second network as local.

Another option if you happen to have a second nic card in your PC is to cable that to the inside network...on the PoE ports and assign it a IP in the 192.168.254.x network. This is a variation of the secondary address and is a much more stable configuration....of course it mean you must have a second nic available in your PC.

 

[abailey]

Could the OP not just change his internal LAN to 192.168.254 and let the NVR do the DHCP? Does the NVR "IP Assignment" have to be on a separate subnet from the NVR "Internal Nic"? I guess his statement "I did try to change the int NIC to an ip under the 192.168.0.** but it gave an error" would suggest that it cannot be on the same subnet.