Please need help , changed google nest to eero & no camera works on BI

C

Carluzky

Young grasshopper
Sep 1, 2020
33
7
Usa
Hello everyone, hope all is well
I had blue iris connected to my google nest and everything was working fine for a few years , yesterday I decided to change it to EERO PRO due to some speed issues , all devices connected perfectly except blue iris on my windows 10 PC, I figure I had to do port forwarding again & so I did , all of a sudden my Dell changes from NETWORK 2 to NETWORK 3 (I am assuming that’s the new eero network ) , got my internet back , however , when go inside BI, all the cameras lost their connection (please see photo) . I tried fixing it for 3 hours but nothing , i tried putting it back on the old network and still nothing , resetting the cameras also did nothing , then on my eero app I see an option to port forward each individual camera , however , when I try putting their IP address I get an error code (please see attachment ) .
I am truly desperate, if anybody has any solutions ,please let me know ! Thanks
 

Attachments

  • D60ABAD8-9395-43C3-97EF-F5B83DF01829.png
    D60ABAD8-9395-43C3-97EF-F5B83DF01829.png
    577.9 KB · Views: 12
  • 9976446D-2ECA-403B-9361-6194EB95464F.jpeg
    9976446D-2ECA-403B-9361-6194EB95464F.jpeg
    2.2 MB · Views: 12
  • 33A855A4-E627-47B3-A391-3A96E741DA24.png
    33A855A4-E627-47B3-A391-3A96E741DA24.png
    788.5 KB · Views: 12
Do not use port forwarding....and you shouldn't have to on an isolated local network. Check all of your IP addresses and subnet mask to make sure they're in the same range (see the error message in your last photo) and use IP ping to test each one. If devices fail to respond to IP ping requests then that's a network related issue and not Blue Iris.
 
Google Nest was likely assigning IP addresses in the 192.168.1.xxx range and your EERO is using a different range. All your other devices don’t care what IP address is assigned to them, but the BI pc and cams do. If my guess is right, you need to reset the DHCP settings in your EERO to the range you were previously using.
 
+1 to both the above ^^^.
Also, insure that NETWORK 3 (the new eero network ?) didn't receive a change from "private" as in the old network properties to "public" in the new network properties.
 
  • Like
Reactions: looney2ns and Swampledge
We all know that hindsight is 20-20 and it's easy to sit back and advise, but should you face a similar thing in the future I suggest this:
  • Find out what subnet you're on (the router's gateway) of the existing equipment BEFORE you replace it.
  • When you've installed the NEW router, if it's on a completely different subnet from the old, considering logging into the NEW router and changing it's LAN IP to the same subnet as the OLD router. You likely will have to give your PC being used for these configurations a temporary static IP in the new router's subnet so you can log into it; once you've set it to the desired subnet you may have to adjust the DHCP pool as well.
IMO, it's easier to change one device (the new router) than several devices (BI server and IP cameras). :cool:
 
  • Like
Reactions: Mike A., looney2ns and Starglow
Starglow said:
Do not use port forwarding....and you shouldn't have to on an isolated local network. Check all of your IP addresses and subnet mask to make sure they're in the same range (see the error message in your last photo) and use IP ping to test each one. If devices fail to respond to IP ping requests then that's a network related issue and not Blue Iris.
Click to expand...
Thank you. I was under the impression that I had to do port forwarding IF I wanted to use the BI app on my iPhone
 
Swampledge said:
Google Nest was likely assigning IP addresses in the 192.168.1.xxx range and your EERO is using a different range. All your other devices don’t care what IP address is assigned to them, but the BI pc and cams do. If my guess is right, you need to reset the DHCP settings in your EERO to the range you were previously using.
Click to expand...
Thank you ! Are you referring to this option ? (Please see attachment )
Now , hopefully this doesn’t sound dumb, but how do I find out what my previous dhcp was ?
 

Attachments

  • C39E085F-6690-4197-B180-6097E9E3831E.jpeg
    C39E085F-6690-4197-B180-6097E9E3831E.jpeg
    193.1 KB · Views: 8
TonyR said:
+1 to both the above ^^^.
Also, insure that NETWORK 3 (the new eero network ?) didn't receive a change from "private" as in the old network properties to "public" in the new network properties.
Click to expand...
Thank you . Both were on private
 
TonyR said:
We all know that hindsight is 20-20 and it's easy to sit back and advise, but should you face a similar thing in the future I suggest this:
  • Find out what subnet you're on (the router's gateway) of the existing equipment BEFORE you replace it.
  • When you've installed the NEW router, if it's on a completely different subnet from the old, considering logging into the NEW router and changing it's LAN IP to the same subnet as the OLD router. You likely will have to give your PC being used for these configurations a temporary static IP in the new router's subnet so you can log into it; once you've set it to the desired subnet you may have to adjust the DHCP pool as well.
IMO, it's easier to change one device (the new router) than several devices (BI server and IP cameras). :cool:
Click to expand...


thank you
1- funny enough , I tried plugging back the original google nest router and it’s not working either . I am assuming I can go to the google app and find out what the previous SUBNET was ?
2-might be a dumb question , but where do I see my LAN #? All I see is my WAN # on eero
 
Personally, I use a genuine PC to log into the router, no app on a tablet or smartphone. I know I'm an old fart but it seems that way I see a lot more than I would otherwise....I admit, it could be just me...my 2 cents.:cool:
 
  • Like
Reactions: looney2ns and Starglow
  • Like
Reactions: looney2ns
TonyR said:
Personally, I use a genuine PC to log into the router, no app on a tablet or smartphone. I know I'm an old fart but it seems that way I see a lot more than I would otherwise....I admit, it could be just me...my 2 cents.:cool:
Click to expand...

The newer products are geared towards the average home user so manufacturers want them to be easy to set up and use right out of the box, plus it saves cost not having to develop and maintain an onboard webpage interface. Everything is going that way now but I'm old school too so I hear ya.... :lmao::lmao:
 
  • Like
Reactions: TonyR
You must log in or register to reply here.
Top Bottom