Is A GeoVision Camera and A Hikvision NVR Compatible?

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Does anyone have any experience with using a GeoVision camera with a Hikvision NVR?

My setup is an 8-port Hikvision NVR with 5 Hikvision cameras and 1 Dahua camera directly plugged into it. That's it. None of the cameras or the NVR go through any switch or router or anything.

I am now trying to link a GeoVision camera with the Hikvision NVR.

So I loaded the latest GV IP Device Utility (GV DU) program onto my laptop, plugged my GV camera into my Hikvision NVR and then connected my laptop into an empty port on the NVR. Then I ran the GV DU program to find the GV camera but it never did, even after 5 tries.

However, when I installed the Dahua camera, I used a Dahua config tool program and it found the camera instantly but the GV DU program is not finding the GV camera for some reason.

Would anyone know why not? Is there something "special" I need to do first?

If I can just find the GV camera, then I think I can modify it's settings and get it working. Thanks!
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,963
Reaction score
6,794
Location
Scotland
If I can just find the GV camera, then I think I can modify it's settings and get it working. Thanks!
Does the documentation say what the default IP address is?
Did the camera look like it powered on?
Does it claim to be a PoE camera?
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Does the documentation say what the default IP address is?
Did the camera look like it powered on?
Does it claim to be a PoE camera?
I can't find the documentation (it is about 4 years old) and the camera is already mounted. And of course I didn't think to write the IP address down first. Dummy! :/ So I'll have to take it down and find out. But if the GV DU program still can't find it, I'm not sure how I will be able to change any settings.
Yes, the camera appears to have power to it.
Yes, it claims to be a PoE camera.
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,963
Reaction score
6,794
Location
Scotland
And of course I didn't think to write the IP address down first.
Would this have been an IP address that was valid on your LAN? And is your LAN address range the same as it was 4 years ago?
In which case, if the camera really is powered up and working, an IP address scan from the PC that has a static address from your LAN address range, when plugged in to a spare NVR PoE port, may find it.
If the camera is ONVIF compliant, ONVIF Device Manager (sourceforge.net, Onvif Device Manager v2.2.250) would find it automatically.
If not, a popular scan tool for the PC would be nmap.
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Would this have been an IP address that was valid on your LAN? And is your LAN address range the same as it was 4 years ago?
In which case, if the camera really is powered up and working, an IP address scan from the PC that has a static address from your LAN address range, when plugged in to a spare NVR PoE port, may find it.
If the camera is ONVIF compliant, ONVIF Device Manager (sourceforge.net, Onvif Device Manager v2.2.250) would find it automatically.
If not, a popular scan tool for the PC would be nmap.
It's not on a LAN. The cameras have E-cords plugged into them and then the cords run straight to the NVR and plug into it.

It's a GeoVision camera and it says it's ONVIF compliant so great, I'll download that Device Manager and/or the nmap scan tool and try again. Thanks!
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,963
Reaction score
6,794
Location
Scotland
Yes, I was thinking that if the camera used to have a fixed address on the LAN some years ago, the forgotten IP address would be in the same range as the PC is still on.
If it is, ONVIF Device Manager should just find it.
 
Joined
Feb 19, 2017
Messages
5
Reaction score
0
It's not on a LAN. The cameras have E-cords plugged into them and then the cords run straight to the NVR and plug into it.
It is on a LAN, a LAN (Local Area Network) is a group of network devices sharing a common IP range and Subnet.
The NVR and IP Cameras are on their own LAN, they're just not the same LAN as your other computers.
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Would this have been an IP address that was valid on your LAN? And is your LAN address range the same as it was 4 years ago?
In which case, if the camera really is powered up and working, an IP address scan from the PC that has a static address from your LAN address range, when plugged in to a spare NVR PoE port, may find it.
If the camera is ONVIF compliant, ONVIF Device Manager (sourceforge.net, Onvif Device Manager v2.2.250) would find it automatically.
If not, a popular scan tool for the PC would be nmap.
It's not on a LAN. The cameras have E-cords plugged into them and then the cords run straight to the NVR and plug into it.

It's a GeoVision camera and it says it's ONVIF compliant so great, I'll download that Device Manager and/or the nmap scan tool and try again. Thanks!

It is on a LAN, a LAN (Local Area Network) is a group of network devices sharing a common IP range and Subnet.
The NVR and IP Cameras are on their own LAN, they're just not the same LAN as your other computers.
Oh ok. I see. Thanks.
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Yes, I was thinking that if the camera used to have a fixed address on the LAN some years ago, the forgotten IP address would be in the same range as the PC is still on.
If it is, ONVIF Device Manager should just find it.
upload_2017-2-20_9-17-30.png

This is my screenshot from the ONVIF program. This is the error message for the 3rd firmware address location.

I found documentation so I'm trying to figure out how to use it.

Does this mean the program has found the camera? If so, what do the error messages mean?
 
Last edited:

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Yes, I was thinking that if the camera used to have a fixed address on the LAN some years ago, the forgotten IP address would be in the same range as the PC is still on.
If it is, ONVIF Device Manager should just find it.
upload_2017-2-20_9-25-43.png

This is the screenshot for the 2nd firmware address location which is also the same as the 1st camera error message.
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Yes, I was thinking that if the camera used to have a fixed address on the LAN some years ago, the forgotten IP address would be in the same range as the PC is still on.
If it is, ONVIF Device Manager should just find it.
upload_2017-2-20_9-41-7.png

Here is the screenshot for the settings. Do I need to change anything?
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Yes, I was thinking that if the camera used to have a fixed address on the LAN some years ago, the forgotten IP address would be in the same range as the PC is still on.
If it is, ONVIF Device Manager should just find it.
I downloaded the nmap program but it won't execute. All it does is rapidly open and close a command prompt with lots of lines of messages in it.

Maybe I'm trying to open the wrong program - I was trying to open the nmap application file.

What is the correct program file to execute nmap?
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,963
Reaction score
6,794
Location
Scotland
I downloaded the nmap program but it won't execute. All it does is rapidly open and close a command prompt with lots of lines of messages in it.
It's a command-line program. You need to run cmd (Start | Run | Cmd) to get a command window then run nmap.
If you just double-click on it in Windows it will do as you describe.

On nmap - assuming that 192.168.44.x is the normal address range that your LAN uses (it's a bit unusual), and the PC is still using an address in that range, at the command line a simple scan to use would be:
nmap 192.168.44.1-254

I don't understand your ONVIF Device Manager screenshots.
Finding an ONVIF device on the same LAN address range as the PC is on is generally automatic.
The devices found would be automatically listed, if they respond to the ONVIF dialogues.
It looks like you have manually added some IP addresses - is that correct?
And the addresses shown are on different address ranges. The 192.168.0.1 looks more like a gateway/router address.
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Oh ok. I'll use the cmd prompt and see what happens. Thanks.

Yeah, you would think the ONVIF program would automatically find it.
I did manually add the 3rd IP address. Just trying to manually add the IP address for the GeoVision camera since 192.168.0.1 is supposedly the default IP address for the GeoVision camera but it didn't work.
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
Oh ok. I'll use the cmd prompt and see what happens. Thanks.

Yeah, you would think the ONVIF program would automatically find it.
I did manually add the 3rd IP address. Just trying to manually add the IP address for the GeoVision camera since 192.168.0.1 is supposedly the default IP address for the GeoVision camera but it didn't work.
UPDATE: I used the nmap but wow, I couldn't tell what it all meant. I'll need to read up on how to use nmap I guess. Sheesh.
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,963
Reaction score
6,794
Location
Scotland
I couldn't tell what it all meant.
With that simple scan, it's simply listing all the host IP addresses on that subnet, and the ports that are listening on them.
If it's the NVR PoE port the PC was connected to, there should be almost no results.
And the idea was to eliminate those addresses you know about and spot the one you are searching for.
Post the result on here, in code tags.

the IP address for the GeoVision camera since 192.168.0.1 is supposedly the default IP address for the GeoVision camera but it didn't work.
To me that seems an unlikely address - the first address in a segment is by convention commonly allocated to network equipment such as a gateway.
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
UPDATE - I finally took down the GeoVision camera to find out what IP address was printed on it and it does not have one. However, it does have a MAC address printed on it. Is that helpful in any way?
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
With that simple scan, it's simply listing all the host IP addresses on that subnet, and the ports that are listening on them.
If it's the NVR PoE port the PC was connected to, there should be almost no results.
And the idea was to eliminate those addresses you know about and spot the one you are searching for.
Post the result on here, in code tags.

To me that seems an unlikely address - the first address in a segment is by convention commonly allocated to network equipment such as a gateway.

Here is the screenshot since I don't know what code tags means. Sorry!


C:\>nmap
Nmap 7.40 ( Nmap: the Network Mapper - Free Security Scanner )
Usage: nmap [Scan Type(s)] [Options] {target specification}
TARGET SPECIFICATION:
Can pass hostnames, IP addresses, networks, etc.
Ex: scanme.nmap.org, microsoft.com/24, 192.168.0.1; 10.0.0-255.1-254
-iL <inputfilename>: Input from list of hosts/networks
-iR <num hosts>: Choose random targets
--exclude <host1[,host2][,host3],...>: Exclude hosts/networks
--excludefile <exclude_file>: Exclude list from file
HOST DISCOVERY:
-sL: List Scan - simply list targets to scan
-sn: Ping Scan - disable port scan
-Pn: Treat all hosts as online -- skip host discovery
-PS/PA/PU/PY[portlist]: TCP SYN/ACK, UDP or SCTP discovery to given ports
-PE/PP/PM: ICMP echo, timestamp, and netmask request discovery probes
-PO[protocol list]: IP Protocol Ping
-n/-R: Never do DNS resolution/Always resolve [default: sometimes]
--dns-servers <serv1[,serv2],...>: Specify custom DNS servers
--system-dns: Use OS's DNS resolver
--traceroute: Trace hop path to each host
SCAN TECHNIQUES:
-sS/sT/sA/sW/sM: TCP SYN/Connect()/ACK/Window/Maimon scans
-sU: UDP Scan
-sN/sF/sX: TCP Null, FIN, and Xmas scans
--scanflags <flags>: Customize TCP scan flags
-sI <zombie host[:probeport]>: Idle scan
-sY/sZ: SCTP INIT/COOKIE-ECHO scans
-sO: IP protocol scan
-b <FTP relay host>: FTP bounce scan
PORT SPECIFICATION AND SCAN ORDER:
-p <port ranges>: Only scan specified ports
Ex: -p22; -p1-65535; -p U:53,111,137,T:21-25,80,139,8080,S:9
--exclude-ports <port ranges>: Exclude the specified ports from scanning
-F: Fast mode - Scan fewer ports than the default scan
-r: Scan ports consecutively - don't randomize
--top-ports <number>: Scan <number> most common ports
--port-ratio <ratio>: Scan ports more common than <ratio>
SERVICE/VERSION DETECTION:
-sV: Probe open ports to determine service/version info
--version-intensity <level>: Set from 0 (light) to 9 (try all probes)
--version-light: Limit to most likely probes (intensity 2)
--version-all: Try every single probe (intensity 9)
--version-trace: Show detailed version scan activity (for debugging)
SCRIPT SCAN:
-sC: equivalent to --script=default
--script=<Lua scripts>: <Lua scripts> is a comma separated list of
directories, script-files or script-categories
--script-args=<n1=v1,[n2=v2,...]>: provide arguments to scripts
--script-args-file=filename: provide NSE script args in a file
--script-trace: Show all data sent and received
--script-updatedb: Update the script database.
--script-help=<Lua scripts>: Show help about scripts.
<Lua scripts> is a comma-separated list of script-files or
script-categories.
OS DETECTION:
-O: Enable OS detection
--osscan-limit: Limit OS detection to promising targets
--osscan-guess: Guess OS more aggressively
TIMING AND PERFORMANCE:
Options which take <time> are in seconds, or append 'ms' (milliseconds),
's' (seconds), 'm' (minutes), or 'h' (hours) to the value (e.g. 30m).
-T<0-5>: Set timing template (higher is faster)
--min-hostgroup/max-hostgroup <size>: Parallel host scan group sizes
--min-parallelism/max-parallelism <numprobes>: Probe parallelization
--min-rtt-timeout/max-rtt-timeout/initial-rtt-timeout <time>: Specifies
probe round trip time.
--max-retries <tries>: Caps number of port scan probe retransmissions.
--host-timeout <time>: Give up on target after this long
--scan-delay/--max-scan-delay <time>: Adjust delay between probes
--min-rate <number>: Send packets no slower than <number> per second
--max-rate <number>: Send packets no faster than <number> per second
FIREWALL/IDS EVASION AND SPOOFING:
-f; --mtu <val>: fragment packets (optionally w/given MTU)
-D <decoy1,decoy2[,ME],...>: Cloak a scan with decoys
-S <IP_Address>: Spoof source address
-e <iface>: Use specified interface
-g/--source-port <portnum>: Use given port number
--proxies <url1,[url2],...>: Relay connections through HTTP/SOCKS4 proxies
--data <hex string>: Append a custom payload to sent packets
--data-string <string>: Append a custom ASCII string to sent packets
--data-length <num>: Append random data to sent packets
--ip-options <options>: Send packets with specified ip options
--ttl <val>: Set IP time-to-live field
--spoof-mac <mac address/prefix/vendor name>: Spoof your MAC address
--badsum: Send packets with a bogus TCP/UDP/SCTP checksum
OUTPUT:
-oN/-oX/-oS/-oG <file>: Output scan in normal, XML, s|<rIpt kIddi3,
and Grepable format, respectively, to the given filename.
-oA <basename>: Output in the three major formats at once
-v: Increase verbosity level (use -vv or more for greater effect)
-d: Increase debugging level (use -dd or more for greater effect)
--reason: Display the reason a port is in a particular state
--open: Only show open (or possibly open) ports
--packet-trace: Show all packets sent and received
--iflist: Print host interfaces and routes (for debugging)
--append-output: Append to rather than clobber specified output files
--resume <filename>: Resume an aborted scan
--stylesheet <path/URL>: XSL stylesheet to transform XML output to HTML
--webxml: Reference stylesheet from Nmap.Org for more portable XML
--no-stylesheet: Prevent associating of XSL stylesheet w/XML output
MISC:
-6: Enable IPv6 scanning
-A: Enable OS detection, version detection, script scanning, and traceroute
--datadir <dirname>: Specify custom Nmap data file location
--send-eth/--send-ip: Send using raw ethernet frames or IP packets
--privileged: Assume that the user is fully privileged
--unprivileged: Assume the user lacks raw socket privileges
-V: Print version number
-h: Print this help summary page.
EXAMPLES:
nmap -v -A scanme.nmap.org
nmap -v -sn 192.168.0.0/16 10.0.0.0/8
nmap -v -iR 10000 -Pn -p 80
SEE THE MAN PAGE (Chapter 15. Nmap Reference Guide) FOR MORE OPTIONS AND EXAMPLES

C:\>nmap
Nmap 7.40 ( Nmap: the Network Mapper - Free Security Scanner )
Usage: nmap [Scan Type(s)] [Options] {target specification}
TARGET SPECIFICATION:
Can pass hostnames, IP addresses, networks, etc.
Ex: scanme.nmap.org, microsoft.com/24, 192.168.0.1; 10.0.0-255.1-254
-iL <inputfilename>: Input from list of hosts/networks
-iR <num hosts>: Choose random targets
--exclude <host1[,host2][,host3],...>: Exclude hosts/networks
--excludefile <exclude_file>: Exclude list from file
HOST DISCOVERY:
-sL: List Scan - simply list targets to scan
-sn: Ping Scan - disable port scan
-Pn: Treat all hosts as online -- skip host discovery
-PS/PA/PU/PY[portlist]: TCP SYN/ACK, UDP or SCTP discovery to given ports
-PE/PP/PM: ICMP echo, timestamp, and netmask request discovery probes
-PO[protocol list]: IP Protocol Ping
-n/-R: Never do DNS resolution/Always resolve [default: sometimes]
--dns-servers <serv1[,serv2],...>: Specify custom DNS servers
--system-dns: Use OS's DNS resolver
--traceroute: Trace hop path to each host
SCAN TECHNIQUES:
-sS/sT/sA/sW/sM: TCP SYN/Connect()/ACK/Window/Maimon scans
-sU: UDP Scan
-sN/sF/sX: TCP Null, FIN, and Xmas scans
--scanflags <flags>: Customize TCP scan flags
-sI <zombie host[:probeport]>: Idle scan
-sY/sZ: SCTP INIT/COOKIE-ECHO scans
-sO: IP protocol scan
-b <FTP relay host>: FTP bounce scan
PORT SPECIFICATION AND SCAN ORDER:
-p <port ranges>: Only scan specified ports
Ex: -p22; -p1-65535; -p U:53,111,137,T:21-25,80,139,8080,S:9
--exclude-ports <port ranges>: Exclude the specified ports from scanning
-F: Fast mode - Scan fewer ports than the default scan
-r: Scan ports consecutively - don't randomize
--top-ports <number>: Scan <number> most common ports
--port-ratio <ratio>: Scan ports more common than <ratio>
SERVICE/VERSION DETECTION:
-sV: Probe open ports to determine service/version info
--version-intensity <level>: Set from 0 (light) to 9 (try all probes)
--version-light: Limit to most likely probes (intensity 2)
--version-all: Try every single probe (intensity 9)
--version-trace: Show detailed version scan activity (for debugging)
SCRIPT SCAN:
-sC: equivalent to --script=default
--script=<Lua scripts>: <Lua scripts> is a comma separated list of
directories, script-files or script-categories
--script-args=<n1=v1,[n2=v2,...]>: provide arguments to scripts
--script-args-file=filename: provide NSE script args in a file
--script-trace: Show all data sent and received
--script-updatedb: Update the script database.
--script-help=<Lua scripts>: Show help about scripts.
<Lua scripts> is a comma-separated list of script-files or
script-categories.
OS DETECTION:
-O: Enable OS detection
--osscan-limit: Limit OS detection to promising targets
--osscan-guess: Guess OS more aggressively
TIMING AND PERFORMANCE:
Options which take <time> are in seconds, or append 'ms' (milliseconds),
's' (seconds), 'm' (minutes), or 'h' (hours) to the value (e.g. 30m).
-T<0-5>: Set timing template (higher is faster)
--min-hostgroup/max-hostgroup <size>: Parallel host scan group sizes
--min-parallelism/max-parallelism <numprobes>: Probe parallelization
--min-rtt-timeout/max-rtt-timeout/initial-rtt-timeout <time>: Specifies
probe round trip time.
--max-retries <tries>: Caps number of port scan probe retransmissions.
--host-timeout <time>: Give up on target after this long
--scan-delay/--max-scan-delay <time>: Adjust delay between probes
--min-rate <number>: Send packets no slower than <number> per second
--max-rate <number>: Send packets no faster than <number> per second
FIREWALL/IDS EVASION AND SPOOFING:
-f; --mtu <val>: fragment packets (optionally w/given MTU)
-D <decoy1,decoy2[,ME],...>: Cloak a scan with decoys
-S <IP_Address>: Spoof source address
-e <iface>: Use specified interface
-g/--source-port <portnum>: Use given port number
--proxies <url1,[url2],...>: Relay connections through HTTP/SOCKS4 proxies
--data <hex string>: Append a custom payload to sent packets
--data-string <string>: Append a custom ASCII string to sent packets
--data-length <num>: Append random data to sent packets
--ip-options <options>: Send packets with specified ip options
--ttl <val>: Set IP time-to-live field
--spoof-mac <mac address/prefix/vendor name>: Spoof your MAC address
--badsum: Send packets with a bogus TCP/UDP/SCTP checksum
OUTPUT:
-oN/-oX/-oS/-oG <file>: Output scan in normal, XML, s|<rIpt kIddi3,
and Grepable format, respectively, to the given filename.
-oA <basename>: Output in the three major formats at once
-v: Increase verbosity level (use -vv or more for greater effect)
-d: Increase debugging level (use -dd or more for greater effect)
--reason: Display the reason a port is in a particular state
--open: Only show open (or possibly open) ports
--packet-trace: Show all packets sent and received
--iflist: Print host interfaces and routes (for debugging)
--append-output: Append to rather than clobber specified output files
--resume <filename>: Resume an aborted scan
--stylesheet <path/URL>: XSL stylesheet to transform XML output to HTML
--webxml: Reference stylesheet from Nmap.Org for more portable XML
--no-stylesheet: Prevent associating of XSL stylesheet w/XML output
MISC:
-6: Enable IPv6 scanning
-A: Enable OS detection, version detection, script scanning, and traceroute
--datadir <dirname>: Specify custom Nmap data file location
--send-eth/--send-ip: Send using raw ethernet frames or IP packets
--privileged: Assume that the user is fully privileged
--unprivileged: Assume the user lacks raw socket privileges
-V: Print version number
-h: Print this help summary page.
EXAMPLES:
nmap -v -A scanme.nmap.org
nmap -v -sn 192.168.0.0/16 10.0.0.0/8
nmap -v -iR 10000 -Pn -p 80
SEE THE MAN PAGE (Chapter 15. Nmap Reference Guide) FOR MORE OPTIONS AND EXAMPLES

C:\>
 

wapaper59

Young grasshopper
Joined
Jan 25, 2017
Messages
99
Reaction score
2
It's a command-line program. You need to run cmd (Start | Run | Cmd) to get a command window then run nmap.
If you just double-click on it in Windows it will do as you describe.

On nmap - assuming that 192.168.44.x is the normal address range that your LAN uses (it's a bit unusual), and the PC is still using an address in that range, at the command line a simple scan to use would be:
nmap 192.168.44.1-254

I don't understand your ONVIF Device Manager screenshots.
Finding an ONVIF device on the same LAN address range as the PC is on is generally automatic.
The devices found would be automatically listed, if they respond to the ONVIF dialogues.
It looks like you have manually added some IP addresses - is that correct?
And the addresses shown are on different address ranges. The 192.168.0.1 looks more like a gateway/router address.
Sorry! The default IP address of GeoVision cameras is supposedly 192.168.0.10. I left off the 0 on the end. :/ I also found out that the easiest way to change the IP address is to use the GV software so I'll download that and try this all again.
 
Top