I have several HK cams already installed and working. Trying to add another one, but not doing too well. Installed cam, used SADP, found and set to an IP. Reboot and shows up. Open. Try to set a port for Cam disappears upon reboot. Ping says it's there. Tried original IP, new IP, new IP with new port, new IP without new port, nada. On SADP cam shows up intermittently, but still ping says all is well. Reset cam and the process repeats. I need (I think) a HTTP for PF like my other 9 cams, but this is not going right. Any thoughts? thx
HK 2032 Problems Accessing
- Thread starter dblee50
- Start date
Yes. Should have added. I have hooked it in to two different POE ports at different locations with different cables with same results.
Yes. after the last few days in frustration, I'm very familiar with all the IPs on my network. It is unique. I had a different one, or two before with same results.
For exp. I just reset cam. It came up on SADP right away with default IP. I reset IP to xxx.xxx.xxx.45. rebooted. Accessed it on computer, showed on SADP with .45 IP. Cam works fine....until I try to change http port. open configuration of cam, change http port from 80 to 8045 (or something else) it reboots, then nothing. Can't access using xxx.xxx.xxx.45:8045. ping says it's there.
fenderman
Staff member
- Mar 9, 2014
- 36,891
- 21,407
I dont know what the solution is...i have always been able to change the http port in hikvisions without issue, however, the truth is its not really needed....if you are port forwarding you can just use any external port and forward it to 80...
I am. To port forward the camera, I have to log into camera, go to configuration, go to port setting, and change http from 80 to something else. That's where I've been having the problems. It goes south from there.
fenderman
Staff member
- Mar 9, 2014
- 36,891
- 21,407
ok, so first, if you are just port forwarding to view video remotely and are using the hikvision app you only need to forward the media port (8000 by default) you should not forward the http port unless you have a specific reason for doing so.
Now, whether you choose to forward the http port or media port or whatever, you dont actually have to change the port on the camera..
In your routers port forward settings, it will allow you to choose the external (source) port and internal (destination) port..So you can choose that external port 8045 is routed to internal port 80..so it would be the same as changing the internal port to 8045
Now, whether you choose to forward the http port or media port or whatever, you dont actually have to change the port on the camera..
In your routers port forward settings, it will allow you to choose the external (source) port and internal (destination) port..So you can choose that external port 8045 is routed to internal port 80..so it would be the same as changing the internal port to 8045
With my head held low, my router is the uverse gateway. When I got to the so called port forwarding section, I have this:
[h=2]Firewall Application Profile Definition[/h]If the desired application requires multiple ports of both TCP and UDP ports, you will need to add multiple definitions. Current definitions for this profile are shown in the Definition List below.
[TD="class: tablesidebold"]Application Profile Name[/TD]
[TD="class: tablesidebold"]Create Application Definition[/TD]
[TD="class: indent"]Protocol[/TD]
[TD="class: indent"]Port (or Range)[/TD]
[TD="class: indent"]Protocol Timeout[/TD]
[TD="class: indent"]Map to Host Port[/TD]
[TD="class: indent"]Application Type[/TD]
I normally only have to enter port (or range) to the port that matches camera port I set up and all is well.
[h=2]Firewall Application Profile Definition[/h]If the desired application requires multiple ports of both TCP and UDP ports, you will need to add multiple definitions. Current definitions for this profile are shown in the Definition List below.
| TCPUDP | |
| FromTo | |
| TCP default 86400 seconds, UDP default 600 seconds | |
| Default/blank = same port as above | |
| - FTP (file transfer protocol) server H.323-based Internet telephony DirectX Game (DirectPlay) host IRC (Internet relay chat) server PPTP virtual private network server SIP-based Internet telephony | |
| Note: In some rare instances, certain application types require specialized firewall changes in addition to simple port forwarding. If the application you are adding appears in the application type menu above, it is recommended that you select it. |
[TD="class: tablesidebold"]Application Profile Name[/TD]
[TD="class: tablesidebold"]Create Application Definition[/TD]
[TD="class: indent"]Protocol[/TD]
[TD="class: indent"]Port (or Range)[/TD]
[TD="class: indent"]Protocol Timeout[/TD]
[TD="class: indent"]Map to Host Port[/TD]
[TD="class: indent"]Application Type[/TD]
I normally only have to enter port (or range) to the port that matches camera port I set up and all is well.
fenderman
Staff member
- Mar 9, 2014
- 36,891
- 21,407
Prop that head up! 
...all you gotta do is set "map to host port" to the internal port number..so for http it would be 80 or for media it would be 8000...
When you log in remotely, you use your externalipaddress:XXXX where XXXX is your EXTERNAL port -in your case the port you set in the "port (or range)" box..this will then be mapped by the router to the internal port of 80 or 8000 or whatever you enter into the "map to host port"
...all you gotta do is set "map to host port" to the internal port number..so for http it would be 80 or for media it would be 8000...When you log in remotely, you use your externalipaddress:XXXX where XXXX is your EXTERNAL port -in your case the port you set in the "port (or range)" box..this will then be mapped by the router to the internal port of 80 or 8000 or whatever you enter into the "map to host port"
I have been extensively trained through the network school of hard knocks so what worked in the past has generally worked ..... until now. Well I did what you said and it works. All I can say is thanks very much. I won't try to undo the other things I have set up that work for some reason, but this has made my life just a little bit easier today. Thanks.
All my other PF IPs were of the format: xxx.xxx.xxx.123 and I set up a port 8xxx so to address that device, I would enter xxx.xxx.xxx.123:8xxx when addressing locally. To address remotely, I would use my dyndns address, xxxxxx.dyndns.org:8xxx
all set up like this has worked well.
all set up like this has worked well.
New day. New problems. I think it may go beyond ip cams. This am, the cam I set up last night was working on computer using direct ip and in NVR window. All other cams were out on the NVR page. They could not be addressed on computer by direct ip address. All of them pinged, however initially there was unreachable errors, but eventually pinged ok. I took out newest cam that was configured as indicated last night just using default ports and a static ip to see if it had caused problems but no change. rebooted computer, no change.I could not direct access any of the remaining cams by xxx.xxx.xxx.xxx:xxxx as usual. I will reboot gateway in a little while to see if any thing changes. Looking at my NVR recordings, most of the cams dropped off line around midnight 30. If you're thinking DCHP release, all have static ips so, don't know.
Some additional info, not sure if relevant, I have uverse gateway with four ports on back. I have a uverse DVR hooked to one port, an 8port swt hooked to one port. From the switch, I have the computer hooked, several devices locally, another switch to other devices, AND an ethernet that runs to upstairs 16 port switch. That's where hardwired cams are routed to thru a POE injector. I have hooked the new cam into the POE at two or three locations (locations where some of the other cams were hooked) and it works fine so assume POE is ok. From there another run goes to an entertainment center where I have another switch and a router used as an access point. 30+ devices hooked up and the only issues seem to be the cameras.
I'll post back after a couple of things: First I'll take down one of the older cams and reset to let gateway refind it using similiar setup as new cam. If no joy, I'll reboot gateway. Worse case, I'll reset gateway and start over.
Some additional info, not sure if relevant, I have uverse gateway with four ports on back. I have a uverse DVR hooked to one port, an 8port swt hooked to one port. From the switch, I have the computer hooked, several devices locally, another switch to other devices, AND an ethernet that runs to upstairs 16 port switch. That's where hardwired cams are routed to thru a POE injector. I have hooked the new cam into the POE at two or three locations (locations where some of the other cams were hooked) and it works fine so assume POE is ok. From there another run goes to an entertainment center where I have another switch and a router used as an access point. 30+ devices hooked up and the only issues seem to be the cameras.
I'll post back after a couple of things: First I'll take down one of the older cams and reset to let gateway refind it using similiar setup as new cam. If no joy, I'll reboot gateway. Worse case, I'll reset gateway and start over.
UPDATE: Took down one of old cams. Reset to default ports on cam. PF as last night and it works. So, I'll start resetting all my other cams one at a time to see if things come back.