Vigi C300HP wrong network segment
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
I have a couple of C300HP cameras.
I've recently changed the network configuration. One of the C300HP is working fine - the other one is not - it won't connect to the network properly. I've done a packet capture and I can see it has a fixed IP address and isn't using DHCP to get a new network address (it seems to be stuck to a Static IP Address.)
The other C300HP was doing the same thing - but after a few power cycles, worked ok and picked up the new IP address from DHCP.
How can I force the other C300HP to connect on the new network?
Regards, Bill
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @OzzyBill
Thanks for posting in our business forum.
If the cams are getting a static IP, you should change that to DHCP mode. Or you should manually change their IPs to fit the new subnet.
Actually three ways now:
1. Change the subnet to the old subnet where they used to have.
2. Log in to the cams by setting up a static IP on your computer. Log in to the cams one by one. Change the IP to suit the new subnet.
3. Reset cams and start over so they can get the DHCP IP by default. It would work again without too many hassles.
- Copy Link
- Report Inappropriate Content
Thanks @Clive_A ,
Because they're C300HP's there's no Web Interface for the cameras.
I found the answer in the end:
The scenario:
* NVR and Camera's were on old network segment
* switched NVR and all Cameras to a new segment - some camera's (C300HP) would not pick up an IP address on the new segment even though DHCP available
The solution:
* set up router so that I had both subnets available (old and new)
* ensured that the two subnets could reach each other
* put the equipment that was working on the new subnet - onto the new subnet (NVR and two newer cams)
* put the equipment that wouldn't switch to the new subnet, back onto the old subnet (these were the two C300HP's - which have no web interface)
Now, I logged into the NVR web interface, and was able to add the old C300HP's using their old subnet addresses. But now I was able to change the IP Address of the C300HP's using the NVR web interface. This worked, and then I was able to move the C300HP's onto the new subnet and the camera's worked find along with the NVR.
Note: the Vigi PC Client application did not appear to be able to make the network changes correctly.
Regards, Bill.
- Copy Link
- Report Inappropriate Content
Hi @OzzyBill
Thanks for posting in our business forum.
If the cams are getting a static IP, you should change that to DHCP mode. Or you should manually change their IPs to fit the new subnet.
Actually three ways now:
1. Change the subnet to the old subnet where they used to have.
2. Log in to the cams by setting up a static IP on your computer. Log in to the cams one by one. Change the IP to suit the new subnet.
3. Reset cams and start over so they can get the DHCP IP by default. It would work again without too many hassles.
- Copy Link
- Report Inappropriate Content
Thanks @Clive_A ,
Because they're C300HP's there's no Web Interface for the cameras.
I found the answer in the end:
The scenario:
* NVR and Camera's were on old network segment
* switched NVR and all Cameras to a new segment - some camera's (C300HP) would not pick up an IP address on the new segment even though DHCP available
The solution:
* set up router so that I had both subnets available (old and new)
* ensured that the two subnets could reach each other
* put the equipment that was working on the new subnet - onto the new subnet (NVR and two newer cams)
* put the equipment that wouldn't switch to the new subnet, back onto the old subnet (these were the two C300HP's - which have no web interface)
Now, I logged into the NVR web interface, and was able to add the old C300HP's using their old subnet addresses. But now I was able to change the IP Address of the C300HP's using the NVR web interface. This worked, and then I was able to move the C300HP's onto the new subnet and the camera's worked find along with the NVR.
Note: the Vigi PC Client application did not appear to be able to make the network changes correctly.
Regards, Bill.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 350
Replies: 2
Voters 0
No one has voted for it yet.