[Closed] I can't access my DVR from the Internet...

Thanks, I'll do a WildBlue search to see if I can find the references you describe. Someone out there may have figured this out...I'm just NOT aware of it. I'll assume someone has tried to reach my hostname with NO success...it is http://dalerp.dyndns.ws

Uhm.. Yes, I had already tried connecting with both the IP and the hostname you previously mentioned: http://dalerp.homedns.org. I got a connection reset most of the time, but sometimes a timeout (packet dropped at destination). At some point I suspected the DVR for not accepting my connections (e.g. some sort of filter at application level).

BUT: When using http://dalerp.dyndns.ws in the Host: header, I am actually getting a real HTTP response! Which now leads me to believe that your DVR only accepts HTTP/1.1 connections with an expected hostname in the Host header.

In simpler terms: It pretty much works to connect to your DVR (on HTTP, port 80) when I'm using the hostname http://dalerp.dyndns.ws, but only when using that specific hostname.

Good Point!! My ISP is WildBlue Satellite Internet. I don't necessarily believe that the Broadband MODEM at my residence is also a router but I DO suspect that when my signal comes back down from outer space to their ground station in Cheyenne, WY that their router does exist there! ALL of my problems may be due to the way my Internet works and it's out of my control. Too bad, if that's true because the technical support at Wildblue is the World's worst! They query, "Can you get onto the Internet? If so, OK then, that's all we can do for you!" They have very LOW END support!!!

Come to think of it, the fact that you're able to access your device locally by using the public IP indicates that the public IP is in fact controlled by the D-Link (which has the NAT mappings / port forwardings configured).

I regret that I must draw a blank. The only other possible issues I can think of at your end is local security filters/firewalls. Either some sort of firewall rule on the DVR or firewall rules on the router, which block the inbound traffic to the DVR. However, I consider that more of a theoretical possibility than a probability.

I also consider it a possibility that the issue is at the ISP's end, but I have no evidence for that conclusion. If you're unable to achieve anything useful by contacting the ISP, perhaps you will find useful discussions about the same ISP somewhere on the web, in the interest of "ruling out" a general problem with receiving inbound connections with that ISP.

Other users here may possibly be able to assist you further.

If you search for WildBlue you'll find a few other threads with similar issues. Do you only have a satellite link, or do you also have a land line connection?

Well, I can see that port 80 is open (others aren't), and the Connection Reset error:

[begin response]

[end response]

Connection reset

Suggests that your DVR may have a software firewall or some other restrictions configured. The other option is that your DVR doesn't have the router's LAN address as it's default gateway.

OK. Thanks. I guess I need to take my laptop somewhere off my home network and try to connect?

Yes, you should test it remotely.

My hosts: http://dalerp.dyndns.ws and http://dalerp.homedns.org are configured exactly the same way. I only created the second one when I couldn't get through on the first one. (Just in case I had a typo or some other such "bug".)

They both point to 67.54.130.50

Yes, and that is precisely my point. The difference lies not within the DNS, but within the DVR. Networking-wise, it makes no difference whether you use the first or the second hostname, or the IP address directly. The traffic reaches the DVR anyway. However, the DVR's HTTP service seems to only reply when a certain hostname was given by the client browser (the HTTP protocol has a "Host" header, where this information is passed), probably for security reasons ("if you don't know my name, I shall not serve you"). Additionally, it would seem it even banned me at some point, temporarily, after attempting several times within a short timeframe.

My guess is that the DVR has a setting where you specify its hostname. Choose that carefully. If it is possible to not specify anything there, that may possibly disable this security feature, but I wouldn't know. I would expect the DVR's user manual to document this behaviour.