Recent content by ichus

Hello again. I've been out of town on family business for awhile but I finally got a chance to try your latest suggestion. It worked. I used an old laptop set to the NAS IP and connected through an ethernet switch. Turns out I had set IP address filtering on and then forgot about it when I did a...

Thanks again for your efforts.

Indeed! I'll keep looking for a schematic and try and make my own reset button. In the meantime it's doing half it's job. Intruder surveillance and alert. Just no time lapse. Maybe I should install a Linux dist and see what I can do. According to the Synology forums alot of Synology owners...

I've tried that (from another PC). Tried connecting directly with a laptop. Connected it to an ethernet switch which hosts 3 other cameras. No joy.

Yes, it says command not found: C:\WINDOWS\system32>ssh admin@192.168.1.20 admin@192.168.1.20's password: admin@nadine:~$ sudo -i Password: root@nadine:~# telnet 192.168.1.105 80 -ash: telnet: command not found Nadine is the name of this NAS. I'm trying to figure our how to install a 3rd...

Yes, when I finally figured out how to log in as root I was able to ping the camera from the NAS. No, can't ping from Windows.

For some reason Synology does not include a telnet client in its os or even a CLI. I can telnet from Windows and log in to the NAS but still Can't connect to the camera. Or I don't know how. The "o" command is not supported. I'll try to find a 3rd party client to install on the NAS. Thanks again...

Additional info: Wireshark detects no traffic on the network from this device.

OK, working camera showed up working fine. Here's the results for the bad cam. Microsoft Windows [Version 10.0.17134.523] (c) 2018 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>nmap 192.168.1.105 Starting Nmap 7.70 ( Nmap: the Network Mapper - Free Security Scanner ) at...

OK, tried it again on a working camera and it worked fine. The screen clearing the connect messages so fast is what threw me off. And then typing the command blind. I understand what you mean now by a low level connection. No login or anything . It's just listening. The response I got was...

I tried port 80 first and got no response at all. Then I tried it on a properly functioning cam and got a could not connect error until I explicitly enabled Telnet on the cam configuration page. Then I could connect only on port 23. I tried the GET command and got a command doesn't exist error...

Just as a long shot, can you try this experiment, using a telnet client. If using Windows and it doesn't already have one, this can be enabled in Control Panel | Windows Features Or the Synology NAS should have a telnet client if you SSH into it. At the command prompt, type : telnet...

Thanks again, but it still won't connect. I'll try to upload a screenshot. All the other Hik cameras respond and I can add to the batch list. This one throws an error every time. Yet still functions properly with the Synology NAS. Interestingly this batch program only locates my cameras on first...

Thanks so much for your help. All my cameras are on a 192.168.x.x segment. I used SADP to change this one to 192.0.0.105. I tried DHCP but it assigned a 168.x.x.x IP. Anyway after matching the segment and power cycling I still get nothing except _192.0.0.128 initialized_ message

Not sure if you received my reply on 3 Jan so copy and pasting here. Yes and yes. Have tried double clicking in SADP. Chrome, Firefox, and IE all timeout without connecting. CMS finds it as a device and adds it to the list, but receives no picture. The fact that the NAS which runs Linux can...