Router Blocking Outside connection to my DVR

Toggle sidebar Toggle sidebar
H

hxdrummerxc

Reputable
Mar 1, 2014
5
0
4,510
Hello,

Let me start off by saying, Im not new to networking. I go to school for networking and I currently have my CCNA cert. However, I have never encountered a problem like this.

I have a home security system with DVR. I have the DVR setup for network use, and it works great when im on my local network. I have set up DDNS so that I can just connect to a hostname (example myhomesec.com), and it will forward to my ISP's dynamically given IP address. All of this works fine. Even when conencting to the DDNS within my LAN it still works properly.

I have set up port forwarding on my router to allow, incoming connections from 0.0.0.0 (all) to my DVR local ip (192.168.1.10) using the proper http port that my DVR is using. (88)

But when I attempt to access my DVR when im outside my local LAN, it always fails. It doesn't matter if I use my current ISP given IP address, or my DDNS domain. It will fail.

Everything works fine inside my LAN. I can connect 3 ways:
1. Using the local IP address of my DVR 192.168.1.10:88
2. Using my public IP address given by my ISP xxx.xxx.xxx.xxx:88
3. And using my DDNS domain name (ex myhomesec.com)

But Outside my local LAN, NOTHING can get access. It has to be my router blocking connections. But everything is properly port forwarded. And even canyouseeme.org, is saying that my ports are open and connection is successful. My DVR doesn't have a firewall, so that can't be stopping anything.

I don't know what else to do right now. Anyone got any ideas?
Thanks a lot
 
Sort by date Sort by votes
Someone Somewhere

Someone Somewhere

Titan
Sep 23, 2012
22,291
8
84,965
Other than the external firewall test, the obvious answer is that your ISP is using either CG-NAT or has a firewall in front of you.

The router should have an external IP visible somewhere in it's config (this is NOT 192.168.x.x). Is this the same as what an external webpage (google what is my ip address) tells you?

Wikipedia says that Port 88 is earmarked for use by Kerberos - have you tried using a different port? Your ISP may be blocking it, or only allowing genuine kerberos traffic through.
 
Upvote 0 Downvote
H

hxdrummerxc

Reputable
Mar 1, 2014
5
0
4,510


I just checked, The public (external) IP address is the same yes.
Also my DVR originally used port 80, but that didn't work so I tried port 88 because I thought maybe my ISP was blocking 80. I also just now tried 82 and it still failed. Even though canyouseeme.org reports that those ports are successful. Im totally lost :(

 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,283
2,743
125,640
Are you sure the DVR has the correct default gateway set.

I would try to forward the port to your PC and run wireshark and see if you are getting syn packets from a outside device.

....or you can get frustrated with these so called routers and use one that puts your CCNA to good use. I get so spoiled by the cisco debug commands. You would know this in 2 seconds if you could put in a nat debug.
 
Upvote 0 Downvote
H

hxdrummerxc

Reputable
Mar 1, 2014
5
0
4,510


Yea, the DVR has the default gateway of my router's local IP.
That's a good idea. Im gonna give wireshark a try.

I used to have my cisco router and switch hooked up. It was nice, but I have a 2600 router and a 3500 switch, and they are both fairly loud. It got kind of annoying lol. I just moved into this house, so when I get the time, I may run all my ethernet to the basement where I can store the cisco equip without worrying about the noise. (its a 3 level house, with my computer(s) upstairs)
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom