Camera System - Multiple camera randomly failed to connect

RWDM3

Getting the hang of it
Nov 28, 2017
160
17
Wanted to run through this for my ref and anyone elses in future
I have a system with multiple cameras, was functioning fine for long time.
Now randomly at ~ 9pm (no internet down, no power down, no updates, nothing changed)
2 cameras went "no signal - failed to connect"

i tried

  • reset switch
  • reset blue iris
  • reset entire network (router, modem etc)
  • right click - camera setting - video - configure - find/inspect ---> result = Timed Out
  • on back of switch both yellow/green lights are lit up just like all the other cameras
  • i cannot connect to camera by typing it into web browser (by typing Ip address) --- other activate cameras are able to connect using this method
    added
  • reset computer
  • try different port in back of switch
  • tried address " 192.168.1.108 "
    camera not showing on confing tool
Did i miss anything that can help resolve this ?
 
Last edited:
Are cameras connected to the internet? If so maybe it is hacked.

Did you try the default IP address - maybe the cameras somehow lost their configuration.
 
What was the solution back in September with a camera or more?

 
Are cameras connected to the internet? If so maybe it is hacked.

Did you try the default IP address - maybe the cameras somehow lost their configuration.
all the other cameras work
the 2 that failed i cant find even on config tool
these 2 still show 2 lights lit up on the switch, but they are no existent otherwise
how can i try the default IP address ?
 
RWDM3 - You said

1 initialized at home that i brought here and hooked up to switch
1 initialized
1 uninitialized (showing same IP as one of the initialized ones)


Then you have two cameras on the same IP address - YOU can not have this it will cause no end of problems trying to access the two cameras irregardless of initialized or not!

disconnect the uninitialized camera and change the IP of the one that is a duplicate! You can only initialized one camera at a time to the best of my knowledge so that you don't have duplicate IP's

If the ones that you can not find also have duplicate IP, then you have a bit of cleanup to do!
 
RWDM3 - You said

1 initialized at home that i brought here and hooked up to switch
1 initialized
1 uninitialized (showing same IP as one of the initialized ones)


Then you have two cameras on the same IP address - YOU can not have this it will cause no end of problems trying to access the two cameras irregardless of initialized or not!

disconnect the uninitialized camera and change the IP of the one that is a duplicate! You can only initialized one camera at a time to the best of my knowledge so that you don't have duplicate IP's

If the ones that you can not find also have duplicate IP, then you have a bit of cleanup to do!
this is completely separate thread, at a different location, i am still troubleshooting that one
 
so this is a little weird not sure if it would relate and solve my issue
i was looking through other threads and one person mentioned to "ping" the camera, when i ping the working ones, i get reply that shows bytes, time ttl, i.e. if I ping .200 it shows me its pinging .200
however, when i ping the cameras that are not working, it states destination host is unreachable, but the weird part is
if i ping camera .211, it shows me reply from .240 for some reason
 
Sounds like you might possibly have a duplicate IP address, would suggest you disconnect all the cameras and test the communications with each one individually! Make sure that you record the IP that each camera is assigned to, you might also want to download an IP scan program, I have used the "Angry IP Scanner" and it does the job, also perhaps note the MAC address of each camera while you are testing them, it will always identify a the particular hardware device, even if the assigned IP changes.
 
so... still havent figured this out but wanted to provide more information as i have a little bit of spare time and was doing some more digging
was checking footage history (clips),

prior to the failure, there is no clips showing, i ran through my footage with all cameras showing

3 cameras showing working, then randomly, at 311, the other 2 (that are not not working, come back on , they work for 60 seconds, and disappear again
i tried checking log but it doesnt go back that far (just set it to save to file and retail for longer)

i do see some messages on status
events: subscription 0002ee2
FORCE quitting pXServer Thread

Edit:
i still dont understand, even if the camera was having issues with lets say.. BI, why would i not be able to detect camera directly through IP, or see camera in configtool
 
had time today to even try to reset entire camera, still nothing, i am confused at this point, i figured that would fix it for sure

i tried #1 holding reset button for 20-30 seconds - no go, nothing showing up in config tool
i tried unplugging camera ethernet cord at camera - no go, nothing showing up in config tool
 
Have you tried connecting one camera at a time as I suggested in an earlier reply!. Do the bad cameras show a link light on the POE switch? Not sure if your comment "i tried unplugging camera ethernet cord at camera - no go, nothing showing up in config tool" is as I read it, I would not expect the camera to show up if the ethernet was unplugged from the camera!!!
 
at switch
when camera is plugged in - both lights light up on left and right (green and yellow) - same as the working camera

at camera
when i go out right now at night i see the red ring around camera (IR), when i reset it manually at camera i can see the lights turn off

"i tried unplugging camera ethernet cord at camera - no go, nothing showing up in config tool"
i mean i reset camera by unplugging ethernet at camera (unplugged, waiting 15 seconds, plugged back in)
still nothing showing in IP CONFIG

yes tried disconnecting all camera

if i disconnect all camera
and connect one camera (working camera) it comes up in IPCONFIG

if i disconnect all camera
and connect one camera (the ones that dont work) it does not come up in IPCONFIG
 
Not quite sure what you mean by shows up in IPCONFIG, this is a command that runs on a windows PC in a terminal window that shows the network configuration of a windows PC, it should have nothing to do with showing if a camera is present or not. Are you perhaps referring to the DAHUA "ConfigTool" that detects their brand of cameras on a network segment.

From what you describe, it is clear that the camera is connecting to the POE switch and is drawing power if the Infrared LED's are lighting up.

Just as an FYI, I just pulled a camera from one of my systems that was doing the same thing as you describe, no ping and no sign of being connected to the network, but it did draw power and have link lights on the POE switch, I replaced it with a new camera and tossed it in the garbage since it was a really old and crummy camera and not worth wasting time on (I am not saying that yours are dead but at some point you may have to consider the possibility)!

I am curious about you earlier comment that the cameras sometimes show up for a few minutes, have you tried to run a program similar to "Angry IP scanner" to see what IP address show up on your network. You also said that earlier you tried the default IP address of " 192.168.1.108 ", is your subnet of your network 192.168.1.x or is it different, if it is different you can not reach the default address without have a network card configured with an address of 192.168.1.x, also the IP scanner will not detect any IP address that are not on the current subnet that you use on your LAN!
 
Based on what you described, these two cameras could be broken. You'll need to send them to a repair shop. If the camera's board is damaged, you may need to buy new cameras.