May 3, 2013
Let me start by saying I am a networking professional, so I know how to set up port forwarding, NATting, etc., and have done it many times….
That said, I am having a problem trying to access my DVR from outside my network. It works fine from inside my network. I have the port forwarding set up correctly (and have verified it by configuring another device with the same IP and port, and I can access it just fine from outside).
Is there something in the DVR that would cause it to only respond to internal IP addresses?
Thanks for your post. There are actually 3 ports that need to be pointed to the DVR. You need to open the HTTP, TCP and UDP ports. By default they are 88, 37777 and 37778 unless you changed those ports you will need to point them to the internal IP address of your DVR.
When connecting to the DVR webserver (usually with Internet Explorer) you will use the HTTP port. When connecting with a smart device like phone or tablet, or when connecting with the video management software (TechproSS-PC or TechproSS-MAC) you will use port 37777 (by default unless you changed it). Otherwise, there is nothing special about setting up a DVR vs any other network device. If all of this has been done and you attempting to connect to the correct port and you are still unable to reach the DVR then double check the internal IP address of your DVR and make sure that you have pointed to the corrected address. Also, turn off DHCP in the DVR so that your network will not change that address without your permission.
Lastly, this is basic, but often missed. Make sure you are using your WAN IP address when outside your network and not the LAN address and follow the address with the port number in this format – XX.XXX.XXX.XX:YYYYYY (where Y is the port number)
If you still need help, our tech support team is available and can remote in to your network to give assistance M-F 9am – 6pm EST.
May 3, 2013
Unfortunately, I’ve done all that you suggested. I’ve ensured that all 4 ports are open and forwarded (8080 TCP, 554 TCP, 37777 TCP, and 38888 UDP). I changed the DVR to use port 8080 (although I’ve tested it wilth the default of 80, too). I have double-checked the IP address, and turned off DHCP.
This DVR is actually replacing an old one that has been giving me problems. It, too, had a web interface, and I had holes punched in my firewall for it as well. I’ve reused the same IP address, and the same HTTP ports (8080) to keep things consistent. Plus, I know that my ISP isn’t blocking 8080, since it’s worked fine for my old DVR.
I’ll triple-check everything again just to be sure I haven’t missed something obvious. If not, I’ll try to see if someone can remote in on Monday.
Let me jump in this conversation. Can you please tell us your network setup? Is the layout like ISP Modem/Router connected to a switch or ISP Modem/Router connected to a Wireless Router? Whats the Private IP address of the tour Router? Where is the DVR connected to? Is your setup Dual Nat? where the main internet Router is DHCP enable and another router is attached to it also with DHCP enable? Is your Gateway configure correctly in the DVR? Can you please provide a detailed layout of how the network is configured to help us understand and troubleshoot these issues.
Please private mail this information directly to Jesus. DO NOT post your private IP addresses on the forum. Thanks!
NOTE: Please send me any info in a Private Message (PM)
Since you are able to reach the DVR from inside the network using the LAN address, the issue has to be something other than an issue with the DVR. The DVR does not know the difference between WAN and LAN traffic because to the DVR all traffic is coming from inside the network. It is the job of your ISP, the ISP modem (if you have one) and the DHCP router to allow traffic through and to direct traffic correctly from the outside (WAN) into your network (LAN). Since you have no problem reaching your DVR inside the network the issue is not a DVR issue.
Either way, we will be happy to assist you with this on Monday. You can PM me your phone number and best time to reach you and I can have someone call you, or you can email firstname.lastname@example.org with the information so that a technician can call you, or call us at our toll free number 866-573-8878 and select option 3 for tech support. Any of those methods will get you the help you need.
May 3, 2013
Jesus and bbesner,
Thanks for your very quick replies!
I was able to fix the problem, although I can’t quite explain why…
It appears that the ISP’s gateway was somehow holding on to the IP-to-MAC binding. So, when requests were coming through the firewall for port 8080 (for example), it was trying to forward it to the OLD DVR’s MAC address that HAD BEEN associated to the internal IP address. It wasn’t forwarding the packets to the NEW DVR’s MAC address, which was now using the same IP address.
What solved it was to set up the new DVR on a different IP that had never been used, then set up the port forwarding to that IP address. Voila! Success!
Again, I’m not sure why the gateway wasn’t updating it’s internal tables, but bottom line is it now works. (And, as bbesner correctly asserted, the problem was with the ISP and port-forwarding, NOT the DVR – yeah!)
Thanks to everyone for double-checking my logic!
I’m Glad that everything works now. I quick way to fix this issue without changing the IP address of the DVR is to simply reboot your network devices. This will allow the Router/switches to refresh the arp tables and start mapping the correct MAC addresses to the devices attached to the network.
Cheers to you and Brad!
Most Users Ever Online: 138
Currently Browsing this Page:
Dan Maresca: 460
Techpro Security: 404
Night Hawk: 100
West Coast Jones: 66
Guest Posters: 105
Administrators: Damon Delcoro, Brad Besner, Jose Malave, Gabe Garcia
Moderators: Ryan, Zeke Richey, Jorge Nava, Heath Phillips, Brian Lee, Eric Wilson, Michael, Tonya Haley, LittleBrad, Ted, Matthew Ernst, Ariel Millard, Thomas Dapra