DVR- Internet access - old story, old problems but still....

[scorpion 0]

What port does your DVR use?

 

In your router what ip address did you forward that port number too?

 

Thanks,

 

Locally I could access it with : 11.22.33.44:234

 

Then with Dyndns, I picked a domain name. I submitted the Ip address from ISP gave me.

 

yesterday, I talked with my ISP. He mentioned that ALL ports going to my computer were closed. I Still couldn't figure it out, as some friends suggested that I requested a private port.

 

Please help

 

I am still at a loss as to what your DVR's port number is.

I do not recognize 11.22.33.44 as a legitimate router LAN IP address.

 

I do understand why you would not want to print your WAN IP address, but you should be safe printing your local LAN IP address.

 

is 234 your port number, or is this a representation of a port number?

 

I wanted to know this information to see if your router was set up correctly.

 

I can only guess that your system works on the local LAN, and the reason that it does not work outside of your house/work is that you do not have the DVR port set up to be forwarded.

 

The ISP says that all of your ports are closed!

 

This is great!! This means your router, and the combination of any firewalls are doing their job. You should have at least one port open, and they would have seen your DVRs port number open. This tells me your router is not set up correctly.

 

For others reading this post there are individuals who are trying to use their WAN IP address at the same place where the DVR is located, and what they will usually see is the router's home page. This is correct. You cannot for the most part use the WAN IP address as a local address. There are exceptions, and you can test it to see where you stand. Just be do not be surprised if you outside address does not work.

 

For those of you who want to know what your outside address is so that you can write it down, and test it somewhere else then go to http://www.ipchicken.com/ and write that number down. Once you have this working off site then you can use your dns account. If it works with the ipchicken, and it does not work with the dns then the dns account may have an error.

 

http://scorpiontheater.com/troubleshooting.aspx

 

http://scorpiontheater.com/videonetworkingwithavtech.aspx

 

http://scorpiontheater.com/router.aspx

 

http://www.portforward.com/english/routers/port_forwarding/routerindex.htm

 

 

DYNDNS.ORG!

www.dyndns.com

 

Primer on how to access your DVR

http://dyndnscommunity.com/forum/viewtopic.php?f=17&t=502

 

http://www.dyndns.com/support/

 

http://www.dyndns.com/support/general.html

 

http://www.dyndns.com/support/kb/

 

http://www.dyndns.com/support/clients/hardware/

 

 

 

What do you think?

[fuzzelogic 0]

All,

 

If your router has the ability to be remotely accessed, you can allow temp access to see if you can access your router remotely. If you cannot access this portion remotely, there is little chance you are going to successfully access the DVR remotely.

 

To Run your tests, you really don't have to be at another location to test this functionality. All you need to do is type in the IP provided from your provider into the browser / DVR software.

 

For example , If you enable remote router configuration and then from the same location, type in your IP provided by the provider you should be able to access this functionality.

 

This will save you lots of time wating to test this functionaltiy from remote location at night, etc.

 

Obviously, for the FINAL Test, you would want to make sure from your remote location you can access the DVR. All of the tests before though can be run from the same location as the equipment.

[scorpion 0]

We cannot do what you described with our large name ISP. You have to bring a computer with you with an air card in order to test the WAN.

[vin2install 0]

Or setup a computer at the office with Remote Desktop or VNC to test it from the site. Thats what i usually do. ISP's will block you for accessing your WAN address directly sometimes.

[bascovon 0]

Thanks scorpion.

 

I thimnk i gave a wrong info about Ip.

11.22.33.44:234 is how i access my TP link Wr543.

with subnet :255.255.255.0

 

in WAN my IP : 192.168.2.12 (Set to Dynamic)

Gateway :192.168.1.1

 

with primary DNS : 202.47.66.***

 

DHCP enabled : 11.22.33.1 end : 11.22.33.199

 

I applied for Static one from dyndns, and there, I got a domain name.

In there (dyndns) I supplied the IP of the DNS on my Tp Link

 

That's what I have done so far.

 

On Video server E screen, I put IP : 11.22.33.44

with port 90...and it apperead on my screen monitor, which is What I wanted.

 

Now what I wanna do is to access the domain name I obtained frm dyndns, outside my network, on the internet. which I could not manage.

 

Some suggestions mentioned that I should have an IP PUBLIC full dedicated, or special private port to deliver my request to DVR via my ISP.

 

I am totally confused, since I have no experience on it.

 

Thank you for yr help sir.

[bascovon 0]

@Scorpion

 

Well, it is getting clearer now. The bug seems to be in IP Public which I should have to view my dvr outhere!

 

My ISP won't give any IP Public, as he said it was not a service like that, n I probably need to leave it soon!

 

My question: Wonder if there is a way I can avoid IP public to view my dvr from the internet outhere?

 

How to deliver the request to reach my dvr on my internet browser outside?

 

 

 

 

Thank you

[scorpion 0]

I can see why your are confused. I am more confused then you are!

 

in WAN my IP : 192.168.2.12 (Set to Dynamic)

Gateway :192.168.1.1

 

This maybe a mis type, but the numbers are mismatched.

the Gateway should be 192.168. *2*.1, or the the IP should be 192.168.*1*.12.

 

I think you are going to have to have a computer service company to come out, and help get your situation taken care.

[bascovon 0]

I can see why your are confused. I am more confused then you are!

 

in WAN my IP : 192.168.2.12 (Set to Dynamic)

Gateway :192.168.1.1

 

This maybe a mis type, but the numbers are mismatched.

the Gateway should be 192.168. *2*.1, or the the IP should be 192.168.*1*.12.

 

I think you are going to have to have a computer service company to come out, and help get your situation taken care.

 

@scorpion,

 

Thanks for yr suggestion. I am truly perplexed with yr quoted reply.

 

As I directly wrote down what appeared on screen, when I access my AP.

 

It again says :192.168.2.212 (Obtained it after refreshing it)

Gateway : 192.168.1.1

 

 

My question is How to access DVR frm outside which I think must go through setting up the router.

 

 

 

Please let me know If I really need an extra IP public, besides the one from my ISP.

 

Once again, I am totally new to this. Sorry if such questions bother u

 

 

Thanks

[SRC666 0]

The problem is that your ISP is using NAT (Network Address Translation) routing, just like your own router is doing for your local network.

 

NAT routing hides a large number of machines behind one IP address. For example your local network is 192.168.1.???, but the router's outside address might be 172.16.38.28 (just made up). Normally, all the computers on the internet would see your system as 172.16.38.28, but your ISP has added another layer of NAT. This means that all of their _clients_ computers on the ISP's network will have addresses in the 172.16.???.??? range, but to the outside world they _all_ look like 11.22.33.44. This second layer of indirection is what is killing you.

 

Also note that IP addresses between 172.16.0.0 through 17.32.255.255 are not publicly routable - they will NEVER be available on the general internet.

 

The way NAT routing works is that a request from INSIDE the network sets up a temporary tunnel, or virtual connection between your computer and the outside computer (google.com, for instance). The Router knows of this connection, and it automatically redirects the return traffic from google to the right computer.

 

Requests to connect that originate from outside the local network to a computer inside the local network, however, just try to hit 11.22.33.44, and that router has no idea which of the internal computers that request was for. So it drops the packet.

 

When you set up port forwarding on your router, you are saying "Send any packets sent to 172.16.38.28:1000 to the internal computer 192.168.1.10". This lets an outside system start a conversation with a specific computer on your network. However, since your ISP is also using NAT, you would have to have THEM set up a rule on THEIR router that says "Send any packets sent to 11.22.33.44:1000 to the internal computer 172.16.28.28:1000", where your local router rule would pick it up and send it to your computer. And they will not do that.

 

If they will not rent you a public, routable IP address, then your only option is to find another ISP who will.

 

For a bit more information, you can see a list of the non-routable IP addresses (these usually get used behind NAT routers) here: http://www.jpsdomain.org/networking/nat.html. Information on NAT can be found at: http://en.wikipedia.org/wiki/Network_address_translation

[SRC666 0]

It again says :192.168.2.212 (Obtained it after refreshing it)

Gateway : 192.168.1.1

 

Sorry I missed this in my earlier reading of the thread. This just confirms my suspicion. Any address that begins with 192 is not routable on the internet (internal use only).

 

Since your ISP is giving your router a WAN address of 192.168.2.??? (the last set will change every few days, probably), your router is NOT visible to any system outside of your ISP. It _cannot_ be accessed from the internet unless they set up special routing for your system.

 

There is no good solution short of getting a public IP address, period.