BI Finding Amcrest Cams, but not EmpireTech

[Flintstone61]

You need to install cams on a bench first and use a dummy router and assign it a gateway of 192.168.1.1. then you can get to the 192.168.1.xxx network and login and initialize your cam and assign your cameras the STATIC IP address( ie 192.168.0.xxx) you need for another network, save your changes logout and you can then transfer it the "live network" where the install is.

 

[wittaj]

I fiddle with my cameras at my 3 sites over RDP all the time, and have never had a problem.

But yes, anything that changes your computer's IP over RDP has the potential to lock you out and require a road trip to fix!

This is one case where having a VM spun up in HyperV, with the host having 2 NICs, can be super useful. As long as you can RDP into the HyperV host, you will always be able to control the VM inside it, even if you accidentally (or deliberately) kick the VM off the network. Just don't kick the HyperV host off the network

Yes many of us fiddle with the cameras over RDP. That isn't the issue.

My point was going around and changing the IP subnet of the computer your have remoted into can be a recipe for disaster.

Initializing a camera over remote can cause issues as well if everything isn't on the same subnet and you aren't quite sure what you are doing.

 

[Zipsort]

You need to install cams on a bench first and use a dummy router and assign it a gateway of 192.168.1.1. then you can get to the 192.168.1.xxx network and login and initialize your cam and assign your cameras the STATIC IP address( ie 192.168.0.xxx) you need for another network, save your changes logout and you can then transfer it the "live network" where the install is.

Might be a bit past my skill level there. I dont have an extra router laying around right now. Why do the $50 amcrest cameras connect so easily but these $200 cameras dont?

 

[wittaj]

Might be a bit past my skill level there. I dont have an extra router laying around right now. Why do the $50 amcrest cameras connect so easily but these $200 cameras dont?

You don't need an extra router. That is just one of many ways.

You can do it as I mentioned by simply changing the IP address of your computer to the 198.168.1.xxx subnet.

Or get a cheap $10 USB to ethernet adaptor and assign it a 198.168.1.xxx subnet.

Or use the IP Config Tool.

As mentioned previously, Amcrest is the consumer brand of Dahua so many of the cameras they provide with DHCP so that it shows up on whatever IP subnet the consumer may be running on versus a Dahua camera intended for their professional installers and Dealers that provides a static IP address of 192.168.1.108 so that they can do what they need to do without needing a router. Dahua is the professional arm and their installers have different needs than the consumer buying Amcrest crowd.

We are just fortunate to be able to get our hands on the better stuff. And a forum like this to help us when stuck.

Different end user, different expectations.

But as I mentioned, using DHCP with BI is likely to cause problems at some point. Assigning cameras as static IPs is the safest way.

 

[Zipsort]

You don't need an extra router. That is just one of many ways.

You can do it as I mentioned by simply changing the IP address of your computer to the 198.168.1.xxx subnet.

Or get a cheap $10 USB to ethernet adaptor and assign it a 198.168.1.xxx subnet.

Or use the IP Config Tool.

As mentioned previously, Amcrest is the consumer brand of Dahua so many of the cameras they provide with DHCP so that it shows up on whatever IP subnet the consumer may be running on versus a Dahua camera intended for their professional installers and Dealers that provides a static IP address of 192.168.1.108 so that they can do what they need to do without needing a router. Dahua is the professional arm and their installers have different needs than the consumer buying Amcrest crowd.

We are just fortunate to be able to get our hands on the better stuff. And a forum like this to help us when stuck.

Different end user, different expectations.

But as I mentioned, using DHCP with BI is likely to cause problems at some point. Assigning cameras as static IPs is the safest way.

I've tried everything possible in the IP config to no avail, I'm about to be onsite shortly and will try changing the IP address of the computer. The USB to ethernet seems like it could be handy? as I am planning on adding at least another 5 cameras to the property (would like to put a nice PTZ on a pole by the greenhouse)

 

[wittaj]

Yeah this little adapter works great.

Hopefully when you are on site it all comes together.

I assure you we don't have these types of issues and it takes longer for the camera to start up when first powered than to change the IP address.

 

[Zipsort]

Yeah this little adapter works great.

Hopefully when you are on site it all comes together.

I assure you we don't have these types of issues and it takes longer for the camera to start up when first powered than to change the IP address.

So this just enables you to plug the camera directly into the tower and change IP without installing it first?

 

[Flintstone61]

Might be a bit past my skill level there. I dont have an extra router laying around right now. Why do the $50 amcrest cameras connect so easily but these $200 cameras dont?

DHCP IP addressing box ticked on by default in Amcrest. VS Static IP addressing box ticked on in "Network" menu on camera with Dahua.
Oddly enough though, when you plug a new EmpireTech/Dahua into a POE NVR, It functions like DHCP and is given an IP address related to the NVR's internal switch.

Amcrest is a consumer product with a different firmware. Dahua is sold as a Prosumer/commercial product and has more features available in the firmware in most cases.

 

[Flintstone61]

 

[Flintstone61]

Learn Blue Iris

This is channel is dedicated to teaching about the security camera software, Blue Iris. Subscribe for regular content on this topic! If you have requests for consulting, please send them via email.

www.youtube.com

 

[Zipsort]

DHCP IP addressing box ticked on by default in Amcrest. VS Static IP addressing box ticked on in "Network" menu on camera with Dahua.
Oddly enough though, when you plug a new EmpireTech/Dahua into a POE NVR, It functions like DHCP and is given an IP address related to the NVR's internal switch.

Amcrest is a consumer product with a different firmware. Dahua is sold as a Prosumer/commercial product and has more features available in the firmware in most cases.

View attachment 211941

Alright, still learning. I will not let this camera defeat me! Also, hello neighbor! My gaming PC is my space heater

 

[wittaj]

So this just enables you to plug the camera directly into the tower and change IP without installing it first?

Provided you first set this adapter up to be the IP subnet of the camera, then yes.

Lot's of different ways to take a camera like a Dahua OEM with the 192.168.1.108 IP and gain access to it. This is what most would say is the order from simplest to most complicated:

• Have/Change the home router IP subnet be 192.168.1.1 - many routers that is the default IP address. Or the .1. might be a .0. If every device in the home is DHCP (which is common), then simply changing the router to 192.168.1.1 will take care of it now and for future purchases of any camera on that subnet. This doesn't address the concern many have about giving the camera internet access to phone home as it will have that direct line with this method.
• Use a dual NIC in your BI computer where the 2nd NIC is on the 192.168.1.xxx subnet.
• Set up a spare unused router on the 192.168.1.xxx subnet
• Use an old computer no longer used just for setting up cameras and set it to the 192.168.1.xxx subnet.
• Temporarily change the IP address of the computer to 192.168.1.xxx where xxx is anything but 108
• Use a USB to ethernet adapter set up on the 192.168.1.xxx where xxx is anything but 108
• Use IPconfig (Dahua) or SADP (hikvision) or some other similar program to change the IP address.
• Use a managed switch with VLANs where one of the VLANs is on the 192.168.1.xxx subnet.

I am sure there are some other ways as well.

 

[Zipsort]

Provided you first set this adapter up to be the IP subnet of the camera, then yes.

Lot's of different ways to take a camera like a Dahua OEM with the 192.168.1.108 IP and gain access to it. This is what most would say is the order from simplest to most complicated:

• Have/Change the home router IP subnet be 192.168.1.1 - many routers that is the default IP address. Or the .1. might be a .0. If every device in the home is DHCP (which is common), then simply changing the router to 192.168.1.1 will take care of it now and for future purchases of any camera on that subnet. This doesn't address the concern many have about giving the camera internet access to phone home as it will have that direct line with this method.
• Use a dual NIC in your BI computer where the 2nd NIC is on the 192.168.1.xxx subnet.
• Set up a spare unused router on the 192.168.1.xxx subnet
• Use an old computer no longer used just for setting up cameras and set it to the 192.168.1.xxx subnet.
• Temporarily change the IP address of the computer to 192.168.1.xxx where xxx is anything but 108
• Use a USB to ethernet adapter set up on the 192.168.1.xxx where xxx is anything but 108
• Use IPconfig (Dahua) or SADP (hikvision) or some other similar program to change the IP address.
• Use a managed switch with VLANs where one of the VLANs is on the 192.168.1.xxx subnet.

I am sure there are some other ways as well.

I just ordered the USB adapter, only $9 will be here tomorrow. The dual NIC is interesting, I actually do have a PCI ethernet card as well as the onboard motherboard ethernet..

 

[Zipsort]

Provided you first set this adapter up to be the IP subnet of the camera, then yes.

Lot's of different ways to take a camera like a Dahua OEM with the 192.168.1.108 IP and gain access to it. This is what most would say is the order from simplest to most complicated:

• Have/Change the home router IP subnet be 192.168.1.1 - many routers that is the default IP address. Or the .1. might be a .0. If every device in the home is DHCP (which is common), then simply changing the router to 192.168.1.1 will take care of it now and for future purchases of any camera on that subnet. This doesn't address the concern many have about giving the camera internet access to phone home as it will have that direct line with this method.
• Use a dual NIC in your BI computer where the 2nd NIC is on the 192.168.1.xxx subnet.
• Set up a spare unused router on the 192.168.1.xxx subnet
• Use an old computer no longer used just for setting up cameras and set it to the 192.168.1.xxx subnet.
• Temporarily change the IP address of the computer to 192.168.1.xxx where xxx is anything but 108
• Use a USB to ethernet adapter set up on the 192.168.1.xxx where xxx is anything but 108
• Use IPconfig (Dahua) or SADP (hikvision) or some other similar program to change the IP address.
• Use a managed switch with VLANs where one of the VLANs is on the 192.168.1.xxx subnet.

I am sure there are some other ways as well.

Would you be open to maybe helping me out with a few more things? Recording settings, notification settings, Only one of my 3 cameras is sending push notifications and I cant figure out why. I can venmo you some cash for your time to walk me a couple things

 

[wittaj]

Did you finally get the camera going?

Sometimes the cameras get wonky in BI. The first thing I would suggest is delete the camera and re-add and set up and that usually fixes the problems.

 

[Zipsort]

Did you finally get the camera going?

Sometimes the cameras get wonky in BI. The first thing I would suggest is delete the camera and re-add and set up and that usually fixes the problems.

No not yet, I am going to give it a go tomorrow (have to get on a ladder to reset). I have 3 amcrests running though.