Hikvision strange behaviour

Additional info: Wireshark detects no traffic on the network from this device.
 
ichus said:
Nmap done: 1 IP address (0 hosts up) scanned in 5.12 seconds
Click to expand...
That is very odd. From your PC, the camera is not visible on the network.
With SS working normally, it's obviously communicating, we must be missing something.

Dumb question - have you ever experimented with the IP address blocking in the camera web GUI? Presumably not or you would have said.

With the NAS working, you should be able to try the equivalent of this done via a QNAP NAS (assuming you have telnet or SSH enabled for access to the NAS) and that your Synology NAS has a built-in telnet client :
Ping the camera IP address.
And -

Code: 
[~] # telnet 192.168.1.101 80
GET / HTTP/1.1

HTTP/1.1 200 OK
Date: Tue, 15 Jan 2019 17:22:54 GMT
Server: App-webs/
ETag: "383-1e0-5784b16e"
Content-Length: 480
Content-Type: text/html
Connection: close
Last-Modified: Tue, 12 Jul 2016 08:59:26 GMT

<!doctype html>
<html>
<head>
    <title></title>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="X-UA-Compatible" content="IE=edge" >
    <meta http-equiv="Pragma" content="no-cache" />
    <meta http-equiv="Cache-Control" content="no-cache, must-revalidate" />
    <meta http-equiv="Expires" content="0" />
</head>
<body>
</body>
<script>
    window.location.href = "/doc/page/login.asp?_" + (new Date()).getTime();
</script>
</html>Connection closed by foreign host
[~] # logout
Connection to 192.168.1.202 closed.
alastair@PC-I5 ~ $
 
ichus said:
Additional info: Wireshark detects no traffic on the network from this device.
Click to expand...
Even in promiscuous mode, this will only see traffic between the PC and camera, plus broadcasts.
It won't see the SS video traffic, unless you have an active 'port mirroring' facility on the switch.
 
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 for your help. Hope this is interesting to you.
 
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.
 
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 party package called inetutils, bit if I understand correctly I have to install a new package installer first, as it's not available on any Synology repositories.
 
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.
 
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.

alastairstevenson said:
That's a bit surprising for such a NAS, but you've clearly confirmed it.
Click to expand...

According to the Synology forums alot of Synology owners agree. Surprising and really annoying. From what I gather on the forums, Synology doesn't really care.
 
I've thought of another off-the-wall suggestion - but it's slightly disruptive, so you may not wish to try it.

The odd thing is that the NAS is happily connected to the camera and recording video from it.
But nothing else, especially your PC, can see any evidence that the camera exists on the network.

You have nmap, and SADP, and the browser on the PC. I'm assuming the camera has a static IP address.
My suggestion is -
Unplug the camera from the LAN, unplug the PC from the LAN, connect the 2 together. Ideally with a separate switch, but if not, directly together.
Change the PC IP address to be the same as the IP address the NAS is using.
Try SADP, try nmap, try the browser.
Change the PC IP address back and put the wiring back as it was.

The idea being to see if the PC having the NAS IP address changes the ability to access.
 
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 router upgrade and had to change the static IP on my PC. Shouldn't drink and compute I guess. Anyway thanks again for all your help.
 
You must log in or register to reply here.
Top Bottom