BI with Swann 815 cameras, cameras worked before firmware update

toner

n3wb
Joined
May 7, 2019
Messages
4
Reaction score
0
Location
Arizona
Hello everybody, I've spend the better part of 3 days trying to figure this out and lots of thread reading trying to avoid a "use google" response ;)

I want to get away from the all-in-one DVR units as they always crap out, power supplies die etc, plus they aren't well suited for higher AZ summer temp commercial usage. My shop has 8 cameras now I want to expand to 16-20, my home has 4 I want to expand to 10.

Anyways, I have the 3MP Swann cameras as home and my shop (I plan to buy others to supplement these).

I connected them to my POE switch (Cisco SG-500 52P), Opened the cameras using the free Reolink software as suggested elsewhere and assigned Static IP addresses to them, and added them successfully in BI by selecting Add Camera, Network IP, Direct Disc recording, entering the IP address, then selecting the SWANN NHD-810RTSP profile (prior forum post I researched initially) and these 815 cameras worked.

I decided, since I bought them 3-4 years ago that there was probably a firmware update and there was. The cameras were at FW 227_15073000, I updated two of them to FW 541_16081000 and those two now pull the "No Signal Error: 8000274d (refused; check IP address and port)0" message.

I have tried the "Generic" camera setting as well to no avail.

All cameras, new and old firmware, all work and show up in the REOLINK Client software.

Any suggestions? Not sure why it's pulling a check IP address and port message, unless the new firmware changed the default ports, but they all show the same port settings (new and old firmware) in the REOLINK software. Thanks!
 

Attachments

toner

n3wb
Joined
May 7, 2019
Messages
4
Reaction score
0
Location
Arizona
have you tried clicking the find inspect button. Post the output
Thanks for the response SouthernYAnkee, From camera 192.168.1.201 (and .200) that have the updated firmware and are now NOT working, both have the same result when using the find/inspect button:

Opening 192.168.1.201 port 80...
HTTP Get / request...
Failed with HTTP 12029
Opening 192.168.1.201 port 8999...
ONVIF GetSystemDateAndTime
HTTP 12029
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
RTSP port open?
No automatic configuration made
Done



From Camera 192.168.1.202 with the old original firmware that is working, find/inspect result:

Opening 192.168.1.202 port 80...
HTTP Get / request...
Failed with HTTP 12029
Opening 192.168.1.202 port 8999...
ONVIF GetSystemDateAndTime
HTTP 12029
Checking for common cameras...
Foscam FI86xx/98xx compatible?
Foscam FI89xx compatible?
Foscam FI9821 V2 compatible?
Foscam FI9821 media port compatible?
RTSP port open?
RTSP port detected!
Done
 

toner

n3wb
Joined
May 7, 2019
Messages
4
Reaction score
0
Location
Arizona
ip Address change from 202 to 200 Change it back
Thanks for the reply Nelson Maldonado!

I right clicked the working camera and just changed the IP address to either of the cameras that were not working (.200 and .201) to see if it was some setting under the working camera, .200 and .201 each give the NO SIGNAL Error:8000274d (refused, check IP address and port) 0.
 

toner

n3wb
Joined
May 7, 2019
Messages
4
Reaction score
0
Location
Arizona
I've tried searching for the old firmware IPC_388M.227_15073000 but the only one available is the current one IPC_388M.541_16081000 unless there is an easy way to extract the firmware from the working camera that I didn't update to re-apply to these 2 that are not working now?
 

SouthernYankee

IPCT Contributor
Joined
Feb 15, 2018
Messages
5,170
Reaction score
5,320
Location
Houston Tx
Look up the error http 12029.
You may have IP conflicts for the cameras.
Are these IP address blocked off in your router.
If you camera is wired and has wifi enabled you may need to block off two addresses.
If you have a good router look at what devices have the addresses.

Can you log into each camera with a web server.
Disconnect all cameras from the switch except the one you are have problems with and see it you can connect.

This more than likely is caused by a virus, or malware. Or firewall or antivirus software. I doubt it is caused by BI.
 
Last edited:
Top