BI Finding Amcrest Cams, but not EmpireTech

Bruce_H said:
So what is the IP and subnet etc for your current network, you can get the info by running IPCONFIG in a terminal window(command Prompt), and what are you putting into the edit screen!
Click to expand...
IPv4 Address. . . . . . . . . . . : 192.168.0.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Thats my IPconfig, and I am putting that into the subnet and gateway into the edit screen
 
Did you set the user ID and password in the utility to what was set when you configured the camera, click on the "Search Settings" button to set that info
 
Bruce_H said:
Did you set the user ID and password in the utility to what was set when you configured the camera, click on the "Search Settings" button to set that info
Click to expand...

I've never configured the camera, it's brand new, I havent been able to connect to it yet. So it should still be admin/admin yeah? There is a little triangle icon next to it that does say password error though... What else could be the default PW? edit: I also just tried the pw "default" and nothing
 
Zipsort said:
I've never configured the camera, it's brand new, I havent been able to connect to it yet. So it should still be admin/admin yeah? There is a little triangle icon next to it that does say password error though... What else could be the default PW?
Click to expand...

There is no default user password. It must be set when you first initialize it.

I would go with a factory reset again.

Power up the camera and press and hold the reset in for 1 minute to force a couple of resets.

Then let go of the reset button and try again.
 
Does the camera say initialized on the config screen, if not then you MUST do that first, no need to do the factory reset!
 
wittaj said:
There is no default user password. It must be set when you first initialize it.

I would go with a factory reset again.

Power up the camera and press and hold the reset in for 1 minute to force a couple of resets.

Then let go of the reset button and try again.
Click to expand...

I reset the camera, initialized it with password, getting the same results. It simply isn't letting me change the IP. Man fellas, I think I'm about to throw in the towel on this. Getting frustrated. The $50 amcrest cameras took all of 3 seconds to connect, and this $200 one has taken me 2 days and I've gotten no where!
 
Once you initialize the camera, you must put the UserID and password into the config tool, so that it can access the camera to change the IP
 
OK so something happened and it is just coincidence it happened now, but was going to bite you at some point anyway and we get a post about it almost every week, is that the IP probably changed on one of the Amcrest.

One of the updates BI made that was trying to make life easy for those that don't understand IP addresses and was using DHCP and was tying the camera to the MAC address instead and then would potentially give you a different IP address that BI didn't see.

In theory it should be a good feature because many people use DHCP. Most consumer cams are dhcp by default.

So blueiris is able to follow the camera if the dhcp lease get revoked, but it can also cause problems.

Make your camera a static IP address and then check the Skip Initial MAC, HTTP, DNS reachability tests

1733965455226.png




Here are a few threads that discuss it.

Blue Iris is changing IP addresses randomly

BI changed camera IP addresses

New BI doesn't return the signal for some cameras after router/switch reboot, gets stuck at no signal, was fine on old BI
 
wittaj said:
OK so something happened and it is just coincidence it happened now, but was going to bite you at some point anyway and we get a post about it almost every week, is that the IP probably changed on one of the Amcrest.

One of the updates BI made that was trying to make life easy for those that don't understand IP addresses and was using DHCP and was tying the camera to the MAC address instead and then would potentially give you a different IP address that BI didn't see.

In theory it should be a good feature because many people use DHCP. Most consumer cams are dhcp by default.

So blueiris is able to follow the camera if the dhcp lease get revoked, but it can also cause problems.

Make your camera a static IP address and then check the Skip Initial MAC, HTTP, DNS reachability tests

1733965455226.png




Here are a few threads that discuss it.

Blue Iris is changing IP addresses randomly

BI changed camera IP addresses

New BI doesn't return the signal for some cameras after router/switch reboot, gets stuck at no signal, was fine on old BI
Click to expand...

Sheesh, okay. I'll look into that now. I don't live at the property that this system is setup on (our cabin), but I use RemotePC from my home desktop to make changes (and I had my neighbor reset the camera physically) I was planning on setting up a second blue iris at home but now its looking like I need to go to dang school for IT to figure it out lol. I am decently familiar with computers but this is stumping me. I might need to pay someone to zoom call with and hold my hand. I'm just really bummed, I wanted to see what all the hype on these dahuas was about..
 
Oh that can add a whole other set of problems trying to set up remotely.

Depending on how you remote in, you could have accidentally locked yourself out if you had gone my route of changing the computer IP address.
 
  • Like
Reactions: Bruce_H
wittaj said:
Oh that can add a whole other set of problems trying to set up remotely.

Depending on how you remote in, you could have accidentally locked yourself out if you had gone my route of changing the computer IP address.
Click to expand...

Yeah thats the reason I haven't done it yet, I physically set up yesterday and everything I've tried failed ( short of you having my change my ethernet settings). Ill be back up there tomorrow, but for some reason I dont have high hopes of that working
 
Zipsort

Have you considered the possibility that trying to configure a camera remotely might be part of your problem, The remotePC software could possibly be interfering with what you are trying to do. This is something that I have never tried to do, I always do the camera setup when I am physically at the site or the camera is at my home and I can initialize it and set it for DHCP before taking it to the remote site! I have three BI systems running at remote sites that I connect to using OpenVPN on the routers and then use Microsoft Remote Desktop (only on Pro and higher versions of Win11) to connect to and control the BI PC .
 
  • Like
Reactions: TonyR
Bruce_H said:
Zipsort

Have you considered the possibility that trying to configure a camera remotely might be part of your problem, The remotePC software could possibly be interfering with what you are trying to do. This is something that I have never tried to do, I always do the camera setup when I am physically at the site or the camera is at my home and I can initialize it and set it for DHCP before taking it to the remote site! I have three BI systems running at remote sites that I connect to using OpenVPN on the routers and then use Microsoft Remote Desktop (only on Pro and higher versions of Win11) to connect to and control the BI PC .
Click to expand...
I did it in person as well with no luck. I have windows pro on both machines as well I can give it a try but I set up the camera physically and cant get the IP to change, I went home for the night and still was trying to mess with it via remote to no avail
 
It's painful for me to read this thread because there's surely a simple explanation waiting to be found, which I'd guess is either an IP address conflict or not using the tools correctly. This is not meant to be a ding, because some of the steps aren't intuitive until you learn the hard way how to conform to them. I don't want to jump in with specifics and add another "cook" into the soup. Just a general statement that I use configTool to initialize cameras and change their IP address, and once I learned the hard way how to use it correctly, it's fast, easy, and reliable. Its very big gotcha is that after initializing a camera you have to go back to Search Setting and change the password to the camera's password. If you don't do this, changing the camera IP will fail. It's a bad design, and in the more recent versions they've made an attemp to "fix" it with some documentation, but it's still a gotcha.
 
  • Like
Reactions: Bruce_H
wittaj said:
Depending on how you remote in, you could have accidentally locked yourself out if you had gone my route of changing the computer IP address.
Click to expand...
Bruce_H said:
Have you considered the possibility that trying to configure a camera remotely might be part of your problem, The remotePC software could possibly be interfering with what you are trying to do.
Click to expand...
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 ;)
 
You must log in or register to reply here.
Top Bottom