Sannce i41cc sPoE (12v), no NVR... why does it not show up on the network?

MyGive

n3wb
May 11, 2023
15
4
London
Sannce i41cc sPoE (12v), no NVR... why does it not show up on the network?

I've been giving this ip cam and silly me thought, sure what could be simpler, I'll just power it up and connect it to the LAN port on my home router and bang... Job done....log into its web interface (like I do with the router).... but Oooooo no boyo, your not getting off that easy my lad.

Someone please tell me, whilst I still have some hair leg to scratch out..... Why does it not seen on the network?

Setup is:
1. Camera powers up via separate 12v DC plug = check
2. Camera connected to LAN port 1 on router = check
3. Laptop connected to same router LAN port 2 = check
4. Laptop received DHCP ip address from router = check
5. Log into router to view network connections, see laptop but nothing else, where's the ip cam?
6. Run network ip scanner on the network 192.168.254.0-254 and 192.168.254.1-254 and even 169.254.254.0-254 = nothing, dead as a door nail..!

I'm upset now,,,,,,and feel I need to swear to get it out.... prepare yourselves like like ...cover your ears...
#####@£&&### for the love of money ¥€$###... there I said it, hmmmmm oddly enough, feels better?
 

Attachments

  • IMG_20230505_234121.jpg
    IMG_20230505_234121.jpg
    541.5 KB · Views: 14
  • IMG_20230512_120345.jpg
    IMG_20230512_120345.jpg
    554.2 KB · Views: 14
  • IMG_20230512_120323.jpg
    IMG_20230512_120323.jpg
    536.4 KB · Views: 11
  • Like
Reactions: mat200
Thanks wittaj

I'm pretty sure I did set the router to 192.168.1.1 with dhcp to give out 192.168.1.2-254.
My laptop received the IP 192.168.1.2. The router didn't list any other ip given out and I scanned the LAN but nothing from the camera, just the laptop and router was found.

I could repeat the bench test ?
 
When the camera is powered so you hear the infrared filter click or in a dark room can you see the glow of the infrared? If not then the camera is dead.

If you see/hear the infrared then it is more troubleshooting.

Either the camera is on a different IP address or it is a cloud based you can only access via their app.
 
Yes, camera clicks when first powered on. Then clicks when covering the ir photo sensor that enables the infrared LEDs.

I seen it working a few days ago when it was connected to the (sPoE) NVR recorder.
 
Oh so in that case the NVR probably assigned it an IP address.

Do you still have access to the NVR that you can see what IP subnet the NVR dished out- most NVRs put the camera on a 10.x.x.x subnet.
 
  • Like
Reactions: alastairstevenson
hmmmm ..

Try setting up a netmask that gives you the entire 192.168.x.x network .. restart camera, see if it gets a DHCP ip address .. if not assume already has an IP ..

then scan ..

6. Run network ip scanner on the network 192.168.254.0-254 and 192.168.254.1-254 and even 169.254.254.0-254 = nothing, dead as a door nail..!
 
hmmmm ..

Try setting up a netmask that gives you the entire 192.168.x.x network .. restart camera, see if it gets a DHCP ip address .. if not assume already has an IP ..

then scan ..

6. Run network ip scanner on the network 192.168.254.0-254 and 192.168.254.1-254 and even 169.254.254.0-254 = nothing, dead as a door nail..!
Do you mean set the router to dhcp range 192.168.254.2 up to 192.168.254.254 and with a subnet mask of 255.255.0.0
 
Do you mean set the router to dhcp range 192.168.254.2 up to 192.168.254.254 and with a subnet mask of 255.255.0.0

and also check the laptop settings you will scan with ..

Idea is to allow a full scan as some cameras use IPs out of the range many of us normally use on our routers ..
 
Here's were I got to before throwing in the towel.
Changed the router to provide dhcp range 192.168.254.2 with a subnet of 255.255.0.0.
Picked up an IP in this range from the router on my laptop and then ran a network scan.
Network scan found only one 'unknown' on 192.168.254.254 with no other information.
Tried SADP and Hikvision software but nothing found.
Tried brower to 192.168.254.254:80 and 8080 but timed out.

Is it possible that this ip cam has a static ip address, is set to not respond to ping etc, has virtual host disabled
 
Here's were I got to before throwing in the towel.
Changed the router to provide dhcp range 192.168.254.2 with a subnet of 255.255.0.0.
Picked up an IP in this range from the router on my laptop and then ran a network scan.
Network scan found only one 'unknown' on 192.168.254.254 with no other information.
Tried SADP and Hikvision software but nothing found.
Tried brower to 192.168.254.254:80 and 8080 but timed out.

Is it possible that this ip cam has a static ip address, is set to not respond to ping etc, has virtual host disabled

perhaps a dead camera ?
 
Changed the router to provide dhcp range 192.168.254.2 with a subnet of 255.255.0.0.
Is that a typo? The subnet mask on the router, cam, PC (all devices on that LAN) should be the same, as in 255.255.255.0 .
 
Is that a typo? The subnet mask on the router, cam, PC (all devices on that LAN) should be the same, as in 255.255.255.0 .

Normally if you know the camera would be 192.168.nnn.x .. then yes ..

for a larger scan: 255.255.0.0 would allow the PC to scan the entire 192.168.x.x range ..
 
When I am trying to get any new device working and have no idea what the IP settings of the device is, I use both Wireshark and tftpd64 from Tftpd32: an opensource free firewall friendly dhcp, syslog sntp and tftp server/service for windows, tftp client Connect the camera or whatever, while it is powered off, directly to your laptop network port. Run wireshark and make a filter to not capture any of your network cards traffic so you will only see traffic from the camera. Run tftpd64 and turn on the DHCP server in that and watch the log. Power on the camera and wireguard will capture anything that the camera spits out, if you are lucky and it is looking for a DHCP address, the tftpd log will also show that. You will probably be surprised how much traffic a camera generates when it boots up and what it is looking for.
 
  • Like
Reactions: MyGive and mat200
Normally if you know the camera would be 192.168.nnn.x .. then yes ..

for a larger scan: 255.255.0.0 would allow the PC to scan the entire 192.168.x.x range ..

After much crying and sleepless nights, I decided to have another go.
Following above advice, a scan popped up with ip address 192.168.68.108

I set my bench test router that range and was able to log into the camera' system.
It was set to a static ip, dhcp turned off.

I've since turned on dhcp.

Now, the battle begins with how to get live view to function?
Tried browsers on Win10 and linux : ie, opera and palemoon but no luck.
Is this an ActiveX plugin problem..? and it's no longer supported..?
 

Attachments

  • Sc15.png
    Sc15.png
    41.6 KB · Views: 7
  • IM02.jpg
    IM02.jpg
    43.3 KB · Views: 8
  • Sc7.png
    Sc7.png
    83.6 KB · Views: 8
  • Love
Reactions: mat200