Disregard what I said for the IPC-D121-M IP 192.168.254.8 Camera.
As you have now swapped over to a IPC-B120 Camera.
If you know the existing password your friend should get then on line for you.
Good Luck.
Cannot get IP camera to work
- Thread starter Ironside69
- Start date
As you have now swapped over to a IPC-B120 Camera.
If you know the existing password your friend should get then on line for you.
Good Luck.
Since everything is gone now it’s probably too late to state the obvious. The very first time you activated that camera, changed the password, along with entering the password reset questions.
You should have set the camera to DHCP.
This would have rebooted the camera and if attached to the NVR / Router would have acquired the new DHCP leased IP address.
When you define a static IP address you run the high risk of a IP conflict and taking down the entire internal network.
Best practice is to reserve a IP address tied to the MAC address that is outside of the DHCP pool. Doing so allows all global network changes to propagate downstream without incident.
The use of static IP addressing in a enterprise environment assumes proper book keeping, well defined schema, and consistency in its use and deployment.
Back in the day static addressing was used heavily due in large part because of hardware limitations in being able to properly release / renew said DHCP address.
This caused untold grief to everyone because that end device was in a unknown state of obtaining the new IP address but never - ever did!!
Regardless, the use of static IP addressing should be limited in its use and always placed on a completely different subnet that isn’t related to the main LAN. Following this best practice limits the impact to other networks and systems.
You should have set the camera to DHCP.
This would have rebooted the camera and if attached to the NVR / Router would have acquired the new DHCP leased IP address.
When you define a static IP address you run the high risk of a IP conflict and taking down the entire internal network.
Best practice is to reserve a IP address tied to the MAC address that is outside of the DHCP pool. Doing so allows all global network changes to propagate downstream without incident.
The use of static IP addressing in a enterprise environment assumes proper book keeping, well defined schema, and consistency in its use and deployment.
Back in the day static addressing was used heavily due in large part because of hardware limitations in being able to properly release / renew said DHCP address.
This caused untold grief to everyone because that end device was in a unknown state of obtaining the new IP address but never - ever did!!
Regardless, the use of static IP addressing should be limited in its use and always placed on a completely different subnet that isn’t related to the main LAN. Following this best practice limits the impact to other networks and systems.
what is your network IP range and the pc? if you don't know open a command prompt in windows and type ipconfig and post it here
Yeah, it's funny how much you learn after the event. Even though I've had the CCTV system working really well for quite a while. I don't think It was setup quite rights at the beginning.Since everything is gone now it’s probably too late to state the obvious. The very first time you activated that camera, changed the password, along with entering the password reset questions.
You should have set the camera to DHCP.
This would have rebooted the camera and if attached to the NVR / Router would have acquired the new DHCP leased IP address.
When you define a static IP address you run the high risk of a IP conflict and taking down the entire internal network.
Best practice is to reserve a IP address tied to the MAC address that is outside of the DHCP pool. Doing so allows all global network changes to propagate downstream without incident.
The use of static IP addressing in a enterprise environment assumes proper book keeping, well defined schema, and consistency in its use and deployment.
Back in the day static addressing was used heavily due in large part because of hardware limitations in being able to properly release / renew said DHCP address.
This caused untold grief to everyone because that end device was in a unknown state of obtaining the new IP address but never - ever did!!
Regardless, the use of static IP addressing should be limited in its use and always placed on a completely different subnet that isn’t related to the main LAN. Following this best practice limits the impact to other networks and systems.
can you change the ip of the camera to 192.168.1.223? in SADP? your camera was in the wrong network
SADP Is obviously detecting the IP camera on the network. However, I can't do anything to manipulate the IP address. For some reason it's not filling in the gateway. If you look at the image I attached. A few days ago, it would change to a proper IP address, I think it was 192.168.1.221. But it's not doing that now.
What is strange is when I enter my password. I am getting a little box which says "device rejected". I'm not getting a "wrong password" box,
well now you are on the correct network that is a plus. what browser do you use to access the cameras web interface? perhaps you can find your passwords there. I use avast assword manager so I don't have to remember all my passwords
My mate isn't getting any further than me. HikVision have corresponded with me on Twitter and have said they would contact support for me if I gave them my email information. Whether they will remains to be seen. But I'm afraid that if we can't resolve this issue then my whole system is a trash job. There's no way I am ever going to use HV again. With hindsight, is just too complicated when you have password problems. The fact that you can't reset any of the cameras I've got from the camera itself is crazy.
One thought. One of the cameras that I recently purchased has been activated, and I know the password. However, that still won't work when we plug into the NVR. What settings do you have to manipulate in order to get the box to work with this camera that we know the password to ?
Before you do anything on the camera you have direct access to is this:
- Define the challenge phrase and email for the password reset (IF) available on this camera.
- Add a new Operator with full privilege's and confirm you can access the same via IE.
- Insure the camera(s) are all set to DHCP until you have finalized your installation and only assign a static IP address through DHCP MAC reservation outside of the pool.
- It goes without saying never install a camera directly to the NVR unless you're 100% confident in your abilities and the network attributes are known. Every camera should be activated via SADP tool and set to DHCP and than configured for root access: Admin / Operator
Basically, I'm screwed. I might as well just give up now because this is getting more complicated by the minute. Oh well, this is been a very expensive learning curve.
Unless HikVision pull their fingers out of their backside and help me retrieve the passwords then I'm up the creek without a paddle.
I had hoped one of my dome cameras had a reset button. But when we removed the top pair to be one anywhere. At the moment I have a bullock type camera plugged into a POE and I can see it on my network. I don't think this one has got a reset button.I have to gather you checked this camera (physically) to make sure there isn't a reset switch on the camera as called out by the QSG? Than again most of the manuals from Hikvision are all encompassing and general so this might be related to other hardware in the same line.
Hikvision IPC-B121H-Ma 2.8mm HiWatch
You're probably right as the majority of the time the reset switch is called out in the manual and illustrated pictogram. The manual from the official site doesn't show it besides indicating the How To process which seems rather confusing if not there! 