**UPDATED**SUCCESS**CRACKED*Swann PROPRIETARY camera-can't see it on the network-Swann SWNHD-865MSB

Discussion in 'IP Cameras' started by thejaybo, Jun 23, 2018.

Share This Page

  1. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    Long time user of Swann SWNDH-880 (4k rebranded hikvision) and SWNHD-825 (3mp rebranded hikvision) cameras from costco. These have been great with my linux NVR bluecherry. They even took the hikvision firmware update.


    I've recently purchased a new Swann PIR IP camera from https://www.walmart.com/ip/Swann-SW...rue-Detect-Camera-with-Audio-Bullet/493853045.

    I was hoping it could see it on my network and somehow log in and recombobulate it to work on my system. So far no luck. Obviously the camera isn't automatically pulling an ip from the DHCP.

    I did speak with Swann before ordering to confirm the camera was onvif compatible and that I was using it with a non swann system.

    I know that some hikvision cameras and other sometimes have a different default IP or subnet and you must configure your computer to that ip range and subnet, but I don't even see it using any ipcam scanners, onvif discovery programs or anything. My POE switch does light up and when the ethernet port is occupied by the camera and the IR lights come on in low light.

    Any ideas how I could confirm if I can communicate with this camera without a swann NVR?

    Thanks guys
     
    mat200 likes this.
  2. fenderman

    fenderman Staff Member

    Joined:
    Mar 9, 2014
    Messages:
    27,897
    Likes Received:
    7,727
    have you tried using hikvision sadp?
     
    mat200 likes this.
  3. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    ya, these dont seem to be rebranded hiks
     
  4. fenderman

    fenderman Staff Member

    Joined:
    Mar 9, 2014
    Messages:
    27,897
    Likes Received:
    7,727
    they are likely no onvif compatible despite swann telling you that they are.
    also your ip scanners or onvif device manager will not find something on a different subnet..you need to manually change the subnet of the pc.
     
  5. mat200

    mat200 IPCT Contributor

    Joined:
    Jan 17, 2017
    Messages:
    3,543
    Likes Received:
    1,780
  6. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    Good catch, that PIR camera from Hik does infact look very very similar. I may try harder to get this to work if it in fact an unreleased hik rebrand.
     
    mat200 likes this.
  7. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    Update. I bought the swann nvr and 4k cameras for my inlaws, its actually very good.

    The cameras register on the swann nvr as ip addresses 172.10.1.151, 152, 153 etc.. on port 9988.

    Hikvision sadp shows nothing.

    Any way to link it to my pc and set the ip to its ip and try and connect to it?
     
  8. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    I should say that the cameras subnet is 255.255.255.000 as well
     
  9. Frankenscript

    Frankenscript Getting the hang of it

    Joined:
    Dec 21, 2017
    Messages:
    166
    Likes Received:
    83
    Find a PC with a physical ethernet port, set its ipv4 address to 172.10.1.something, and connect the camera directly to the PC with an ethernet cable (no router in between). Power the camera via the power adaptor or get an ethernet power injector to provide PoE (or use a PoE switch). With the direct connection, and the PC and camera sharing the same subnet, you will be able to access the camera directly via a browser using the 172.10.1.151 type address. Change the address of the camera to something compatible with your setup and reboot. Then connect it to your system. It should now be on the right subnet to be found/configured. I used this process to move cameras from an NVR over to my Blue Iris system, where the NVR and BI system were using different subnets for the cams. Easy peasy. I actually used a cheap Windows tablet with a USB ethernet connector, but it worked fine.
     
  10. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    172.10.1.xxx can't be assigned to a private lab ip
    My windows machine and Mac machine give an error saying so. Even my isp cable modem says you ca t assign 172.10.x.x to a private lan
     
  11. concord

    concord Young grasshopper

    Joined:
    Oct 24, 2017
    Messages:
    95
    Likes Received:
    21
    mat200 likes this.
  12. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    Yah I think they did that so no one can access them with out a proprietary nvr.

    I'll have to find a way to set a computer or router to 172.10.1.1

    Interesting the Swann nvr uses 192.168.0.1 as it's address
     
  13. concord

    concord Young grasshopper

    Joined:
    Oct 24, 2017
    Messages:
    95
    Likes Received:
    21
    Try installing Linux on a computer instead and assign a static IP address in that range, then connect the cam directly to the computer..., I don't think it will complain.
     
  14. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    Ive got ubuntu on a few machnes, and my cam server is ubuntu, ill try that thanks!
     
  15. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    I fucking did it! I was able to crack the new swann true detect ip camera.

    Swann NHD-865 and NHD-885 true detect cameras - supposedly proprietary

    Steps

    1. installed a new swann true detect nvr camera system for a client
    2. in the menu system, noted how the cameras were assigned ip addresses
    -the nvr used 192.168.0.1 as its own IP and subnet 255.255.255.0 but gave the cameras an ip range of 172.16.1.15x - port 9988 - interesting
    3. initially wrote the ip down wrong as 172.10.1.15x, no router or computer would allow you to make it a static ip as its reserved for public - pull hair out and start this thread
    4. finally realized that the ip range was 172.16.1.15x, changed my router to an ip of 172.16.1.149
    5. configured allowed ips of 172.16.1.150 to 172.16.1.190
    6. plugged camera into poe switch and rebooted router
    7. watched as clients came online as the router initalized
    8. noticed an unknown ip that got a new DHCP adderss of 172.16.1.157
    9. tried ssh and telnet - no worky
    10. ping - 3ms response
    11. try https://172.16.1.157 no result
    12. try http://172.16.1.157 - swann camera page saying to download plugin
    13. start foaming at the mouth
    14. username : admin password: left blank - login failed
    15. username : admin password: 12345 - login failed
    16. contemplate getting on live chat with swann
    17. try one more combo admin:password !!!!!WHAMMY!!!!
    18. jizz pants


    holy crap wtfbbbq!

    PIR, motion, audio, 4K@15fps, 4MP@30fps, 16000kbs data rate, analytics, everything seems to work

    This offers a cheap alternative to buying Chinese cameras from shady online vendors.
     

    Attached Files:

    Last edited: Jul 13, 2018
    Mike, 58chev, concord and 1 other person like this.
  16. mat200

    mat200 IPCT Contributor

    Joined:
    Jan 17, 2017
    Messages:
    3,543
    Likes Received:
    1,780
    Congratulations thejaybo.

    Note 172.16.0.0 to 172.31.255.255 are private IPS ( like 10.0.0.0 to 10.255.255.255 and 192.168.0.0 to 192.168.255.255 )

    Is there a ONVIF setting on the camera?
     
  17. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    apparently yes
     

    Attached Files:

    mat200 likes this.
  18. concord

    concord Young grasshopper

    Joined:
    Oct 24, 2017
    Messages:
    95
    Likes Received:
    21
    Good to here, I thought it was strange that it had a public IP address.

    I had bluecherrydvr for a while, before getting the doorbell cam...it wouldn't work with bluecherrydvr. I volunteered to give their tech support access to the cam, but after waiting 6 months , I gave up and switched to Blue Iris. Most of my computers are Linux based, good thing the Win 10 license sticker was still on my HP computer so I didn't have to buy a license or another refirb computer with one.
     
    thejaybo likes this.
  19. thejaybo

    thejaybo n3wb

    Joined:
    Jun 17, 2018
    Messages:
    15
    Likes Received:
    9
    Location:
    Canada
    Good to hear. I really like blueiris, I've played with the demo alot. But I run a powerful pc headless, running a Nas, 20 drive raid,. Plex media server webmin and the bluecherrydvr. Something about a headless non Gui server runs me the right way

    I have read that personal support is lackluster with bluecherry, and I may switch to blueiris in the future.


    I've been experimenting with unraid for a while and vm'. I think I would need to move to more server hardware. Based on my usage/performance requirements which is fine, but my current setup costs me zero.
     
  20. madnut

    madnut n3wb

    Joined:
    Aug 2, 2018
    Messages:
    4
    Likes Received:
    6
    Location:
    Redmond
    First of all huge thanks to thejaybo, great work on making these cams usable.

    I was able to open up a SWNHD-886MSD in a similar manner.
    It is currently $119 at frys which I think is a good deal. Its a 4k cam. It does 4k at 15fps
    Fry's Electronics |

    The firmware version was identical V4.1.3.6_171220

    I Started with the above procedure but the password did not work.
    So the one that did work was
    user:admin
    password:*MAC ADDRESS IN ALL CAPS NO SPACES"
    But in the state it was I could not get the RTSP stream working. The user/password combination lets you into the router but doesn't work for the stream.
    The web access portal doesn't let you change the password for some reason.

    Finally I found this page and tool:
    7450/8580 Camera Configuration
    https://www.dropbox.com/sh/uvlxhtc4x2hj5wt/AABRV6cRep0CLiug90qa0DvOa/HomeSafe View/HomeSafeView_Device_Config_Tool_1.0.0.10_2016_05_20_147.exe?dl=1

    The tool allows you change the admin password to something normal, after that the new password works for the stream as well.
    So not sure you need the mac address at all.

    I think the procedure can be as follows below, Unfortunately i was fighting the cam for a while so I did a bunch of extra stuff like resetting it to factory defaults, but i have a second one to verify this procedure with.
    Here it is for now, I will verify and update as needed.

    1. Get a windows pc with an ethernet port.
    2. Disconnect it from the network and set the IP v4 settings for your network adapter to "Use the following IP address", IP address 172.16.1.149 Subnet mask: 255.255.255.0
    3. Next connect the camera and the PC into a POE switch (make sure nothing else is connected to it). Can be regular switch if camera gets power another way.
    4. Use the HomeSafeView_Device_Config to set the password.
    5. Using the IP you see in HomeSafeView_Device_Config, from the pc connect to the camera VIA Internet Explorer (Not Edge), it will ask for a plugin install. So if the ip is 172.16.1.154 go to http://172.16.1.154 and log into the camera.
    6. Once in you can modify the ip setting to work with your router.

    HomeSafeView works for viewing the camera from PC or iPhone directly, but i think this camera is best if used with blue iris or some other NVR software, this way you are not locked into Swann NVR. I am going to try to use it with Synology surveillance center.
     
    Last edited: Aug 3, 2018
    KB18 and mat200 like this.