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
BI Finding Amcrest Cams, but not EmpireTech
- Thread starter Zipsort
- Start date
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
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
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!
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
If I login to the amcrest via browser, under Network > TCP/IP > Mode, it does have DHCP checked.
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
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
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
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
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
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
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..
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