Please help me to install a Hikvision 2032-I under Ubuntu

[empedokles 0]

Keep an eye on Adblock Plus, it's been known to block scripts and xml rquests in the Hik browser gui.

 

Deactivated Adblock Plus now, still receive "network unormal". More and more I believe it must be the router.

[mkkoskin 0]

Ok next thing to try is factory reset once more, assign ip 192.168.1.100 to camera and 192.168.1.101 to nuc, then disconnect your nuc and the camera from the network and connect the camera straight to the nuc. See if it works then. That eliminates the router from between atleast.

[empedokles 0]

Ok next thing to try is factory reset once more, assign ip 192.168.1.100 to camera and 192.168.1.101 to nuc, then disconnect your nuc and the camera from the network and connect the camera straight to the nuc. See if it works then. That eliminates the router from between atleast.

 

Where do I change the NUCs IP? And how to change it back?

No Gateway-Address for the cam, right?

[empedokles 0]

I tried to change it with "sudo ifconfig eth0 192.168.1.101" and back with 192.168.1.41. I couldn't access the camera either.

 

Here is my protocol:

nuc@nuc:~$ sudo arp-scan --localnet
[sudo] password for nuc: 
ioctl: Cannot assign requested address
WARNING: Could not obtain IP address for interface eth0. Using 0.0.0.0 for
the source address, which is probably not what you want.
Either configure eth0 with an IP address, or manually specify the address
with the --arpspa option.
Interface: eth0, datalink type: EN10MB (Ethernet)
ERROR: Could not obtain interface IP address and netmask
ERROR: pcap_lookupnet: eth0: no IPv4 address assigned
nuc@nuc:~$ 
nuc@nuc:~$ sudo ifconfig eth0 192.168.1.41
nuc@nuc:~$ sudo arp-scan --localnet
Interface: eth0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.8.1 with 256 hosts (http://www.nta-monitor.com/tools/arp-scan/)
192.168.1.100	44:19:b6:2d:13:a8	(Unknown)

1 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.8.1: 256 hosts scanned in 1.486 seconds (172.27 hosts/sec). 1 responded
nuc@nuc:~$ sudo arp-scan --localnet
ioctl: Cannot assign requested address
WARNING: Could not obtain IP address for interface eth0. Using 0.0.0.0 for
the source address, which is probably not what you want.
Either configure eth0 with an IP address, or manually specify the address
with the --arpspa option.
Interface: eth0, datalink type: EN10MB (Ethernet)
ERROR: Could not obtain interface IP address and netmask
ERROR: pcap_lookupnet: eth0: no IPv4 address assigned
nuc@nuc:~$ 

[empedokles 0]

On request of a member from another forum I switched the IP of my router to 192.0.0.1 and the DHCP-Range from 192.0.0.101 to 192.0.0.199.

 

 

 

The camera still gets fround an arp-scan, when I reconnect it, but disappears soon after and I receive the Network unormal error. Once I even catched the liveview for about a second (what is the router doing?).

 

Here is what a ping yields (mind how it switches to .102):

nuc@nuc:~$ sudo arp-scan --localnet
[sudo] password for nuc: 
Interface: eth0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.8.1 with 256 hosts (http://www.nta-monitor.com/tools/arp-scan/)
192.0.0.1	00:22:10:82:61:40	Motorola Mobility, Inc.
192.0.0.64	44:19:b6:2d:13:a8	(Unknown)
192.0.0.101	00:80:3f:3a:d6:79	TATUNG COMPANY

3 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.8.1: 256 hosts scanned in 1.519 seconds (168.53 hosts/sec). 3 responded
nuc@nuc:~$ ping 192.0.0.64
PING 192.0.0.64 (192.0.0.64) 56(84) bytes of data.
From 192.0.0.102 icmp_seq=10 Destination Host Unreachable
From 192.0.0.102 icmp_seq=11 Destination Host Unreachable
From 192.0.0.102 icmp_seq=12 Destination Host Unreachable
From 192.0.0.102 icmp_seq=13 Destination Host Unreachable
From 192.0.0.102 icmp_seq=14 Destination Host Unreachable
From 192.0.0.102 icmp_seq=15 Destination Host Unreachable
From 192.0.0.102 icmp_seq=16 Destination Host Unreachable
From 192.0.0.102 icmp_seq=17 Destination Host Unreachable
From 192.0.0.102 icmp_seq=18 Destination Host Unreachable
From 192.0.0.102 icmp_seq=19 Destination Host Unreachable
From 192.0.0.102 icmp_seq=20 Destination Host Unreachable
From 192.0.0.102 icmp_seq=21 Destination Host Unreachable
From 192.0.0.102 icmp_seq=22 Destination Host Unreachable
From 192.0.0.102 icmp_seq=23 Destination Host Unreachable
From 192.0.0.102 icmp_seq=24 Destination Host Unreachable
From 192.0.0.102 icmp_seq=25 Destination Host Unreachable
From 192.0.0.102 icmp_seq=26 Destination Host Unreachable
From 192.0.0.102 icmp_seq=27 Destination Host Unreachable
From 192.0.0.102 icmp_seq=28 Destination Host Unreachable
From 192.0.0.102 icmp_seq=29 Destination Host Unreachable
From 192.0.0.102 icmp_seq=30 Destination Host Unreachable
64 bytes from 192.0.0.102: icmp_seq=31 ttl=64 time=2383 ms
64 bytes from 192.0.0.102: icmp_seq=32 ttl=64 time=1374 ms
64 bytes from 192.0.0.102: icmp_seq=33 ttl=64 time=367 ms
64 bytes from 192.0.0.102: icmp_seq=34 ttl=64 time=0.890 ms
64 bytes from 192.0.0.102: icmp_seq=35 ttl=64 time=0.808 ms
64 bytes from 192.0.0.102: icmp_seq=36 ttl=64 time=0.837 ms
64 bytes from 192.0.0.102: icmp_seq=37 ttl=64 time=0.812 ms
64 bytes from 192.0.0.102: icmp_seq=38 ttl=64 time=0.808 ms
64 bytes from 192.0.0.102: icmp_seq=39 ttl=64 time=1.05 ms
64 bytes from 192.0.0.102: icmp_seq=40 ttl=64 time=0.888 ms
64 bytes from 192.0.0.102: icmp_seq=41 ttl=64 time=0.873 ms
64 bytes from 192.0.0.102: icmp_seq=42 ttl=64 time=0.914 ms
64 bytes from 192.0.0.102: icmp_seq=43 ttl=64 time=0.817 ms
64 bytes from 192.0.0.102: icmp_seq=44 ttl=64 time=0.806 ms
64 bytes from 192.0.0.102: icmp_seq=45 ttl=64 time=0.821 ms
64 bytes from 192.0.0.102: icmp_seq=46 ttl=64 time=0.858 ms
64 bytes from 192.0.0.102: icmp_seq=47 ttl=64 time=0.814 ms
64 bytes from 192.0.0.102: icmp_seq=48 ttl=64 time=0.902 ms
64 bytes from 192.0.0.102: icmp_seq=49 ttl=64 time=0.863 ms
64 bytes from 192.0.0.102: icmp_seq=50 ttl=64 time=0.951 ms
64 bytes from 192.0.0.102: icmp_seq=51 ttl=64 time=0.919 ms
64 bytes from 192.0.0.102: icmp_seq=52 ttl=64 time=0.879 ms
64 bytes from 192.0.0.102: icmp_seq=53 ttl=64 time=0.815 ms
64 bytes from 192.0.0.102: icmp_seq=54 ttl=64 time=0.815 ms
64 bytes from 192.0.0.102: icmp_seq=55 ttl=64 time=0.813 ms
64 bytes from 192.0.0.102: icmp_seq=56 ttl=64 time=0.929 ms
64 bytes from 192.0.0.102: icmp_seq=57 ttl=64 time=0.809 ms
64 bytes from 192.0.0.102: icmp_seq=58 ttl=64 time=1.03 ms
64 bytes from 192.0.0.102: icmp_seq=59 ttl=64 time=0.919 ms
64 bytes from 192.0.0.102: icmp_seq=60 ttl=64 time=0.815 ms
64 bytes from 192.0.0.102: icmp_seq=61 ttl=64 time=0.810 ms
64 bytes from 192.0.0.102: icmp_seq=62 ttl=64 time=0.824 ms
64 bytes from 192.0.0.102: icmp_seq=63 ttl=64 time=0.814 ms
64 bytes from 192.0.0.102: icmp_seq=64 ttl=64 time=0.791 ms
64 bytes from 192.0.0.102: icmp_seq=65 ttl=64 time=0.805 ms
64 bytes from 192.0.0.102: icmp_seq=66 ttl=64 time=0.836 ms
64 bytes from 192.0.0.102: icmp_seq=67 ttl=64 time=0.869 ms
64 bytes from 192.0.0.102: icmp_seq=68 ttl=64 time=0.823 ms
64 bytes from 192.0.0.102: icmp_seq=69 ttl=64 time=0.827 ms
64 bytes from 192.0.0.102: icmp_seq=70 ttl=64 time=0.831 ms
64 bytes from 192.0.0.102: icmp_seq=71 ttl=64 time=0.812 ms
64 bytes from 192.0.0.102: icmp_seq=72 ttl=64 time=0.805 ms
64 bytes from 192.0.0.102: icmp_seq=73 ttl=64 time=0.887 ms
64 bytes from 192.0.0.102: icmp_seq=74 ttl=64 time=0.919 ms
64 bytes from 192.0.0.102: icmp_seq=75 ttl=64 time=0.836 ms
64 bytes from 192.0.0.102: icmp_seq=76 ttl=64 time=0.798 ms
64 bytes from 192.0.0.102: icmp_seq=77 ttl=64 time=0.803 ms
64 bytes from 192.0.0.102: icmp_seq=78 ttl=64 time=0.808 ms
64 bytes from 192.0.0.102: icmp_seq=79 ttl=64 time=0.875 ms
64 bytes from 192.0.0.102: icmp_seq=80 ttl=64 time=0.985 ms
64 bytes from 192.0.0.102: icmp_seq=83 ttl=255 time=0.765 ms
64 bytes from 192.0.0.102: icmp_seq=84 ttl=255 time=0.785 ms
From 192.0.0.102 icmp_seq=112 Destination Host Unreachable
From 192.0.0.102 icmp_seq=113 Destination Host Unreachable
From 192.0.0.102 icmp_seq=114 Destination Host Unreachable
From 192.0.0.102 icmp_seq=115 Destination Host Unreachable
From 192.0.0.102 icmp_seq=116 Destination Host Unreachable
From 192.0.0.102 icmp_seq=117 Destination Host Unreachable
From 192.0.0.102 icmp_seq=118 Destination Host Unreachable
From 192.0.0.102 icmp_seq=119 Destination Host Unreachable
64 bytes from 192.0.0.102: icmp_seq=122 ttl=64 time=7.23 ms
64 bytes from 192.0.0.102: icmp_seq=123 ttl=64 time=0.812 ms
64 bytes from 192.0.0.102: icmp_seq=124 ttl=64 time=0.809 ms
64 bytes from 192.0.0.102: icmp_seq=125 ttl=64 time=0.812 ms
64 bytes from 192.0.0.102: icmp_seq=126 ttl=64 time=0.814 ms
64 bytes from 192.0.0.102: icmp_seq=127 ttl=64 time=0.826 ms
64 bytes from 192.0.0.102: icmp_seq=128 ttl=64 time=0.814 ms
64 bytes from 192.0.0.102: icmp_seq=129 ttl=64 time=1.05 ms
64 bytes from 192.0.0.102: icmp_seq=130 ttl=64 time=0.821 ms
64 bytes from 192.0.0.102: icmp_seq=131 ttl=64 time=0.826 ms
64 bytes from 192.0.0.102: icmp_seq=132 ttl=64 time=0.871 ms
64 bytes from 192.0.0.102: icmp_seq=133 ttl=64 time=0.941 ms
64 bytes from 192.0.0.102: icmp_seq=134 ttl=64 time=0.822 ms
64 bytes from 192.0.0.102: icmp_seq=135 ttl=64 time=0.837 ms
64 bytes from 192.0.0.102: icmp_seq=136 ttl=64 time=0.820 ms
64 bytes from 192.0.0.102: icmp_seq=137 ttl=64 time=0.812 ms
64 bytes from 192.0.0.102: icmp_seq=138 ttl=64 time=0.854 ms
64 bytes from 192.0.0.102: icmp_seq=139 ttl=64 time=0.833 ms
64 bytes from 192.0.0.102: icmp_seq=140 ttl=64 time=0.827 ms
64 bytes from 192.0.0.102: icmp_seq=141 ttl=64 time=0.797 ms
64 bytes from 192.0.0.102: icmp_seq=142 ttl=64 time=0.878 ms
64 bytes from 192.0.0.102: icmp_seq=143 ttl=64 time=0.869 ms
64 bytes from 192.0.0.102: icmp_seq=144 ttl=64 time=0.828 ms
64 bytes from 192.0.0.102: icmp_seq=145 ttl=64 time=0.823 ms
64 bytes from 192.0.0.102: icmp_seq=146 ttl=64 time=0.798 ms
64 bytes from 192.0.0.102: icmp_seq=147 ttl=64 time=0.812 ms
64 bytes from 192.0.0.102: icmp_seq=148 ttl=64 time=0.829 ms
64 bytes from 192.0.0.102: icmp_seq=149 ttl=64 time=0.940 ms
64 bytes from 192.0.0.102: icmp_seq=150 ttl=64 time=1009 ms
64 bytes from 192.0.0.102: icmp_seq=151 ttl=64 time=1.08 ms
64 bytes from 192.0.0.102: icmp_seq=152 ttl=64 time=1.12 ms
64 bytes from 192.0.0.102: icmp_seq=153 ttl=64 time=1.07 ms
64 bytes from 192.0.0.102: icmp_seq=154 ttl=64 time=1.08 ms
64 bytes from 192.0.0.102: icmp_seq=155 ttl=64 time=1.10 ms
64 bytes from 192.0.0.102: icmp_seq=156 ttl=64 time=1.08 ms
64 bytes from 192.0.0.102: icmp_seq=157 ttl=64 time=1.05 ms
64 bytes from 192.0.0.102: icmp_seq=158 ttl=64 time=1.10 ms
64 bytes from 192.0.0.102: icmp_seq=159 ttl=64 time=1.09 ms
64 bytes from 192.0.0.102: icmp_seq=160 ttl=64 time=1.09 ms
64 bytes from 192.0.0.102: icmp_seq=161 ttl=64 time=1.12 ms
64 bytes from 192.0.0.102: icmp_seq=162 ttl=64 time=1.08 ms
64 bytes from 192.0.0.102: icmp_seq=163 ttl=64 time=0.887 ms
64 bytes from 192.0.0.102: icmp_seq=164 ttl=64 time=0.891 ms
64 bytes from 192.0.0.102: icmp_seq=165 ttl=64 time=1.21 ms
64 bytes from 192.0.0.102: icmp_seq=166 ttl=64 time=0.881 ms
64 bytes from 192.0.0.102: icmp_seq=167 ttl=64 time=0.884 ms
64 bytes from 192.0.0.102: icmp_seq=168 ttl=64 time=1.12 ms
64 bytes from 192.0.0.102: icmp_seq=169 ttl=64 time=0.905 ms
64 bytes from 192.0.0.102: icmp_seq=172 ttl=255 time=0.857 ms
64 bytes from 192.0.0.102: icmp_seq=173 ttl=255 time=0.649 ms
64 bytes from 192.0.0.102: icmp_seq=174 ttl=255 time=0.669 ms
From 192.0.0.102 icmp_seq=202 Destination Host Unreachable
From 192.0.0.102 icmp_seq=203 Destination Host Unreachable
From 192.0.0.102 icmp_seq=204 Destination Host Unreachable
From 192.0.0.102 icmp_seq=205 Destination Host Unreachable
From 192.0.0.102 icmp_seq=206 Destination Host Unreachable
From 192.0.0.102 icmp_seq=207 Destination Host Unreachable
64 bytes from 192.0.0.102: icmp_seq=209 ttl=64 time=1557 ms
64 bytes from 192.0.0.102: icmp_seq=210 ttl=64 time=557 ms
64 bytes from 192.0.0.102: icmp_seq=211 ttl=64 time=0.798 ms
64 bytes from 192.0.0.102: icmp_seq=212 ttl=64 time=0.972 ms
64 bytes from 192.0.0.102: icmp_seq=213 ttl=64 time=1.13 ms
64 bytes from 192.0.0.102: icmp_seq=214 ttl=64 time=0.882 ms
64 bytes from 192.0.0.102: icmp_seq=215 ttl=64 time=0.899 ms
64 bytes from 192.0.0.102: icmp_seq=216 ttl=64 time=0.912 ms
64 bytes from 192.0.0.102: icmp_seq=217 ttl=64 time=0.906 ms
64 bytes from 192.0.0.102: icmp_seq=218 ttl=64 time=1.15 ms
64 bytes from 192.0.0.102: icmp_seq=219 ttl=64 time=1.27 ms
64 bytes from 192.0.0.102: icmp_seq=220 ttl=64 time=0.887 ms
64 bytes from 192.0.0.102: icmp_seq=221 ttl=64 time=0.883 ms
64 bytes from 192.0.0.102: icmp_seq=222 ttl=64 time=1.10 ms
64 bytes from 192.0.0.102: icmp_seq=223 ttl=64 time=0.887 ms
64 bytes from 192.0.0.102: icmp_seq=224 ttl=64 time=0.879 ms
64 bytes from 192.0.0.102: icmp_seq=225 ttl=64 time=1.07 ms
64 bytes from 192.0.0.102: icmp_seq=226 ttl=64 time=0.870 ms
64 bytes from 192.0.0.102: icmp_seq=227 ttl=64 time=0.880 ms
64 bytes from 192.0.0.102: icmp_seq=228 ttl=64 time=0.897 ms
64 bytes from 192.0.0.102: icmp_seq=229 ttl=64 time=0.891 ms
64 bytes from 192.0.0.102: icmp_seq=230 ttl=64 time=0.909 ms
64 bytes from 192.0.0.102: icmp_seq=231 ttl=64 time=0.917 ms
64 bytes from 192.0.0.102: icmp_seq=232 ttl=64 time=0.977 ms
64 bytes from 192.0.0.102: icmp_seq=233 ttl=64 time=1.11 ms
64 bytes from 192.0.0.102: icmp_seq=234 ttl=64 time=1.08 ms
64 bytes from 192.0.0.102: icmp_seq=235 ttl=64 time=1.11 ms
64 bytes from 192.0.0.102: icmp_seq=236 ttl=64 time=1.06 ms
64 bytes from 192.0.0.102: icmp_seq=237 ttl=64 time=1.08 ms
64 bytes from 192.0.0.102: icmp_seq=238 ttl=64 time=1.11 ms
64 bytes from 192.0.0.102: icmp_seq=239 ttl=64 time=1.06 ms
64 bytes from 192.0.0.102: icmp_seq=240 ttl=64 time=1.09 ms
64 bytes from 192.0.0.102: icmp_seq=241 ttl=64 time=1.08 ms
64 bytes from 192.0.0.102: icmp_seq=242 ttl=64 time=1.09 ms
64 bytes from 192.0.0.102: icmp_seq=243 ttl=64 time=1.07 ms
64 bytes from 192.0.0.102: icmp_seq=244 ttl=64 time=1.07 ms
64 bytes from 192.0.0.102: icmp_seq=245 ttl=64 time=1.09 ms
64 bytes from 192.0.0.102: icmp_seq=246 ttl=64 time=1.09 ms
64 bytes from 192.0.0.102: icmp_seq=247 ttl=64 time=1.06 ms
64 bytes from 192.0.0.102: icmp_seq=248 ttl=64 time=0.907 ms
64 bytes from 192.0.0.102: icmp_seq=249 ttl=64 time=0.924 ms
64 bytes from 192.0.0.102: icmp_seq=252 ttl=255 time=0.686 ms
64 bytes from 192.0.0.102: icmp_seq=253 ttl=255 time=0.646 ms
64 bytes from 192.0.0.102: icmp_seq=254 ttl=255 time=0.650 ms
From 192.0.0.102 icmp_seq=282 Destination Host Unreachable
From 192.0.0.102 icmp_seq=283 Destination Host Unreachable
From 192.0.0.102 icmp_seq=284 Destination Host Unreachable
From 192.0.0.102 icmp_seq=285 Destination Host Unreachable
From 192.0.0.102 icmp_seq=286 Destination Host Unreachable
From 192.0.0.102 icmp_seq=287 Destination Host Unreachable
64 bytes from 192.0.0.102: icmp_seq=289 ttl=64 time=1311 ms
64 bytes from 192.0.0.102: icmp_seq=290 ttl=64 time=303 ms
64 bytes from 192.0.0.102: icmp_seq=291 ttl=64 time=1.01 ms
64 bytes from 192.0.0.102: icmp_seq=292 ttl=64 time=0.932 ms
64 bytes from 192.0.0.102: icmp_seq=293 ttl=64 time=0.902 ms
64 bytes from 192.0.0.102: icmp_seq=294 ttl=64 time=0.851 ms
64 bytes from 192.0.0.102: icmp_seq=295 ttl=64 time=0.927 ms
64 bytes from 192.0.0.102: icmp_seq=296 ttl=64 time=1.01 ms
64 bytes from 192.0.0.102: icmp_seq=297 ttl=64 time=1.22 ms
64 bytes from 192.0.0.102: icmp_seq=298 ttl=64 time=1.15 ms
64 bytes from 192.0.0.102: icmp_seq=299 ttl=64 time=0.957 ms
64 bytes from 192.0.0.102: icmp_seq=300 ttl=64 time=0.868 ms
64 bytes from 192.0.0.102: icmp_seq=301 ttl=64 time=0.897 ms
64 bytes from 192.0.0.102: icmp_seq=302 ttl=64 time=0.911 ms
64 bytes from 192.0.0.102: icmp_seq=303 ttl=64 time=0.902 ms
64 bytes from 192.0.0.102: icmp_seq=304 ttl=64 time=0.839 ms
64 bytes from 192.0.0.102: icmp_seq=305 ttl=64 time=1.00 ms
64 bytes from 192.0.0.102: icmp_seq=306 ttl=64 time=1.00 ms
64 bytes from 192.0.0.102: icmp_seq=307 ttl=64 time=1.30 ms
64 bytes from 192.0.0.102: icmp_seq=308 ttl=64 time=1.02 ms
64 bytes from 192.0.0.102: icmp_seq=309 ttl=64 time=0.816 ms
64 bytes from 192.0.0.102: icmp_seq=310 ttl=64 time=1.27 ms
64 bytes from 192.0.0.102: icmp_seq=311 ttl=64 time=0.834 ms
64 bytes from 192.0.0.102: icmp_seq=312 ttl=64 time=0.928 ms
64 bytes from 192.0.0.102: icmp_seq=313 ttl=64 time=0.994 ms
64 bytes from 192.0.0.102: icmp_seq=314 ttl=64 time=0.820 ms
64 bytes from 192.0.0.102: icmp_seq=315 ttl=64 time=0.818 ms
64 bytes from 192.0.0.102: icmp_seq=316 ttl=64 time=0.825 ms
64 bytes from 192.0.0.102: icmp_seq=317 ttl=64 time=0.976 ms
64 bytes from 192.0.0.102: icmp_seq=318 ttl=64 time=0.831 ms
64 bytes from 192.0.0.102: icmp_seq=319 ttl=64 time=0.990 ms
64 bytes from 192.0.0.102: icmp_seq=320 ttl=64 time=0.798 ms
64 bytes from 192.0.0.102: icmp_seq=321 ttl=64 time=0.832 ms
64 bytes from 192.0.0.102: icmp_seq=322 ttl=64 time=0.815 ms
64 bytes from 192.0.0.102: icmp_seq=323 ttl=64 time=0.815 ms

[buellwinkle 0]

Maybe something wrong with your browser. Try doing a curl command, see what happens as in

 

curl http://192.168.1.100/onvif/snapshot > snap.jpg 

and see if it create a pictures in the current directory. Or do a

 

curl http://admin:12345@192.168.1.100/Video/inputs/channels/1 > video.xml 

and it should create an XML document with the image parameters of the camera.

[empedokles 0]

Currently the camera is back to factory defaults (192.0.0.64). I'd rather not try risky stuff with it.

[buellwinkle 0]

Curl is sort of a command line browser, no riskier than running Firefox.

[empedokles 0]

So I would do:

curl http://192.0.0.64/onvif/snapshot > snap.jpg

 

But where does the snapshot end up? What's onvif?

[empedokles 0]

nuc@nuc:~$ curl http://192.0.0.64
curl: (7) Failed to connect to 192.0.0.64 port 80: Establishment of connection refused

[empedokles 0]

BTW: Gateway seems a must as it reads in the manual: "For accessing the network camera from different subnets, please set the gateway for the network camera after you logged in. For detailed information, please refer to Section 5.3.1 Configuring TCP/IP Settings."

[buellwinkle 0]

See, now you know that the camera refused that connection on port 80, why is another story.

 

If you installed NMAP as mentioned earlier, run nmap 192.0.0.64 and it will do a port scan, return something like this and tell you which ports are open on the camera that nmap can connect to -

 

PORT STATE SERVICE

21/tcp filtered ftp

23/tcp open telnet

80/tcp open http

443/tcp open https

554/tcp open rtsp

7001/tcp open afs3-callback

8000/tcp open http-alt

8200/tcp open trivnet1

49152/tcp open unknown

 

Gateway is optional inside the same subnet, but I always put it in the camera to make sure. BUT, in your case you have no gateway as you are using addresses in a different subnet than your router anyway.

[empedokles 0]

nuc@nuc:~$ nmap 192.0.0.64
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-13 17:22 CEST
Nmap scan report for 192.0.0.64
Host is up (0.0012s latency).
Not shown: 998 closed ports
PORT   STATE    SERVICE
21/tcp filtered ftp
23/tcp filtered telnet

 

Hence my router is closing some ports it shouldn't?

[empedokles 0]

BUT, in your case you have no gateway as you are using addresses in a different subnet than your router anyway.

 

No, the router's IP is still 192.0.0.1 now. With a DHCP range from 192.0.0.101 to .199.

 

Here an overview:

NUC (PC) on .102

TV-Box on .101

Cam on .64

 

[buellwinkle 0]

Don't know what causing it, but only two ports are responding and not the ones you want. The router's firewall would only block ports coming in from the outside the router, like from the internet.

 

What's your network setup like. What's the NUC plugged into, what's the camera plugged into, is there a PoE switch or just a PoE injector.

[empedokles 0]

My Motorola-Router has 4 ethernet-ports.

The NUC is occuyping the first one.

The IP-Cam conntects over a cat 5 ethernet-cable to a TP-Link PoE injector (no switch) and the injector to the second port of the router.

Then there is a free port.

And in the last port is occupied by the TV-Box.

 

Maybe the DHCP of the router is causing it? When we gave a virtual IP under the original DCHP 192.168.33 to .something-range it at least worked with the factory 192.0.0.64 IP. Hence it can't be the injector.

 

Funilly enough now it says:

nuc@nuc:~$ nmap 192.0.0.64

Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-13 18:44 CEST
Nmap scan report for 192.0.0.64
Host is up (0.0012s latency).
Not shown: 991 closed ports
PORT      STATE    SERVICE
21/tcp    filtered ftp
23/tcp    filtered telnet
80/tcp    open     http
443/tcp   open     https
554/tcp   open     rtsp
7001/tcp  open     afs3-callback
8000/tcp  open     http-alt
8200/tcp  open     trivnet1
49152/tcp open     unknown

 

Still can't access it on my webbrowser though.

[buellwinkle 0]

Here's what may be the problem, 192.0.0.64 or 100 are internet address and should not be used in a local area network (LAN). The valid LAN addresses either start with 10... or 192.168... or 172.16... It could be router is directing the traffic for that port number on that IP address outside the network trying to find a valid internet site at 192.0.0.64.

 

Do you have a hub or switch you can use without the router? Or do you have a crossover network cable so you can connect the NUC directly to the PC? Or try a valid LAN IP address for the NUC, router and camera and run nmap again and see if port 80 shows up.

[empedokles 0]

Here's what may be the problem, 192.0.0.64 or 100 are internet address and should not be used in a local area network (LAN). The valid LAN addresses either start with 10... or 192.168... or 172.16... It could be router is directing the traffic for that port number on that IP address outside the network trying to find a valid internet site at 192.0.0.64.

 

I don't understand. But strangely enough I now can access my cam under 192.0.0.64. My router settings are IP 192.0.0.1 still. With a DHCP range from 192.0.0.101 to .199.

 

Do you have a hub or switch you can use without the router?

 

Not really. There is one in my drawer, but I guess I don't have its 5V-power-adapter anymore.

 

Or do you have a crossover network cable so you can connect the NUC directly to the PC?

 

The NUC is my PC.

 

Or try a valid LAN IP address for the NUC, router and camera and run nmap again and see if port 80 shows up.

 

That's what we had at the start, but I didn't try nmap then. I remember that I couldn't access the cam over the browser.

 

What doesn't work is the second page used for recording (no plugin detected?):

 

Edited August 13, 2014 by Guest

[empedokles 0]

I successfully could change the IP of my cam to 192.0.0.65 now and access it over this very same IP. (Maybe my internet provider changed something in the meantime, is this possible? - Cause I also made quite a bit upheal in their forum and couldn't why it now works otherwise. I didn't do anything..)

[buellwinkle 0]

It's possible that someone on the internet has that ip address assigned to them, but not 65. Like I said, it's a router thing, directing external traffic and managing internal traffic it thinking that your camera is on the internet even though logic would dictate it's in the same subnet as the camera and NUC so it's local.

 

Yes, I meant direct connect the NUC to camera bypassing the switch.

[empedokles 0]

I used the access to set the Cam to IP 192.168.1.100 and then the router to IP 192.168.1.1 and its DHCP-range from 192.168.1.10 to 192.168.1.64 again.

 

I keep getting changing nmap callbacks and hear the infrared lights of the cam switching on and off (it's night here):

 

nuc@nuc:~$ nmap 192.168.1.100

Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 00:01 CEST
Nmap scan report for 192.168.1.100
Host is up (0.0012s latency).
Not shown: 991 closed ports
PORT      STATE    SERVICE
21/tcp    filtered ftp
23/tcp    filtered telnet
80/tcp    open     http
443/tcp   open     https
554/tcp   open     rtsp
7001/tcp  open     afs3-callback
8000/tcp  open     http-alt
8200/tcp  open     trivnet1
49152/tcp open     unknown

Nmap done: 1 IP address (1 host up) scanned in 16.66 seconds
nuc@nuc:~$ nmap 192.168.1.100

Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 00:03 CEST
Nmap scan report for 192.168.1.100
Host is up (0.0016s latency).
Not shown: 998 closed ports
PORT   STATE    SERVICE
21/tcp filtered ftp
23/tcp filtered telnet

 

nuc@nuc:~$ nmap 192.168.1.100

Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 00:16 CEST
Nmap scan report for 192.168.1.100
Host is up (0.00084s latency).
Not shown: 989 closed ports
PORT      STATE    SERVICE
21/tcp    filtered ftp
23/tcp    filtered telnet
2399/tcp  filtered fmpro-fdal
3971/tcp  filtered lanrevserver
4006/tcp  filtered pxc-spvr
7001/tcp  open     afs3-callback
8083/tcp  filtered us-srv
9917/tcp  filtered unknown
18101/tcp filtered unknown
27352/tcp filtered unknown
49160/tcp filtered unknown

Edited August 13, 2014 by Guest

[empedokles 0]

It's possible that someone on the internet has that ip address assigned to them, but not 65

 

? - I did assign it 192.0.0.65 before. But now it's IP is 192.168.1.100 and I can't access it anymore. It's switching on and of an nmap strangely produces alternating results.

 

Like I said, it's a router thing, directing external traffic and managing internal traffic it thinking that your camera is on the internet even though logic would dictate it's in the same subnet as the camera and NUC so it's local.

 

What can I do about that?

 

Yes, I meant direct connect the NUC to camera bypassing the switch.

 

We tried this as well a few pages back. It didn't work out then. Plus, it won't help me, as I need Internet and this router is from my Internetprovider.

[empedokles 0]

What I maybe could try is setting the IP of the cam below the DHCP range but above the routers IP. Say 192.168.1.5.

[buellwinkle 0]

Could be the camera is bad, has issues, don't know, but it's behaving weirdly. How can it return that it's connecting to port 80 and then a minute later it says it's not and you are saying it's going on/off, weird. If you were near me in So Call I can test it for you or try one of my cameras on your PC, if not maybe someone else here is local to you. Maybe the injector is having issues. Do you have a 12V adapter from something else that plugs in? Then you can bypass the injector.

 

You are ok with the IP you chose, it's in a valid LAN range. What I do before I assign an IP to a camera is do a ping first to see if anything is using it, then I assign it.

 

For fun, I tried to access Hikvision cameras from Puppy Linux and I can certainly connect to any of the Hikvision cameras using firefox, but does not display the live image. I tried the different choices from the drop down like MJPEG, VLC, Quicktime but nothing displays, but no errors either but I can see all the menus and works fine other than displaying the image. Ubuntu probably has more drivers and apps for this to work as Puppy Linux is a purposely small.

[catseyenu 0]

Have you tried a different router?

Something not controlled by your ISP preferably...