- Contact Us
I have my ports forwarded. I set up two different hostnames pointing to 184.108.40.206 I used the Open Port Tool and I got the message that 220.127.116.11:80 is open and accepting connections. This indicates the port is not being blocked by either a firewall or your ISP and is currently operational. I CAN acces my DVR from computers within my own network both wired and wirelessly. However, if I take my laptop to somewhere outside my network (Like a hotel, when I was away from home a few days ago.) or if I have someone out on the Internet trying to access my DVR, they can't get through. One of my hostnames is: dalerp.dyndns.ws It is set up to point to 18.104.22.168. Obviously, there is some, one small item, that is preventing access from outside my home network. Can someone please get me up and running? (The whole objective of setting up my surveillance system was to be able to view it when I'm NOT at home!)
Additionally, I just spoke with my ISP and they assure me that 22.214.171.124 IS A PUBLIC IP ADDRESS! They "ping" it and packets get through in both directions! I've read the other FAQ's and answers and I know there are people with similar problems and I've used the other suggestions to no avail. HELP!
After reading additional responses to the same basic question, I tried changing my DVR http port from 80 to 8000 just in case there was a conflict with the admin access to my router as someone suggested. I changed the port forwarding to port 8000 and used the port testing tool and it claims that both 80 and 8000 are "OPEN". However, now I can't access my DVR from within my own network! Before I change it back to 80, I'll give someone a chance to tell me what the HECK is going on?
Answer by VikingTiger · Jul 24, 2010 at 07:13 PM
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 dalerp.dyndns.ws
Uhm.. Yes, I had already tried connecting with both the IP and the hostname you previously mentioned: 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 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 dalerp.dyndns.ws, but only when using that specific hostname.
Answer by diarbake · Jul 30, 2010 at 09:53 PM
i would check to see if your router or isp are blocking ports from their end, comcast and verizon block ports and lead customer on to believe they are unlocked by default, lmao what scumbags, seemyport.com "the truth test"
Answer by asdf · Jan 29, 2012 at 01:34 PM
I am also having this stupid problem after I've changed my router from Netgear to D-Link. In short, I could login to my DVR locally (i.e. http://192.....:XXXX), but when I login publicly (i.e. http://60....:XXXX), I cannot seem to connect. Here's what i've tested 1. Local login - works 2. Local login via mobile - works 3. Public login but via the same adsl router - doesn't work 4. public login (mobile) but via the same adsl router (wifi) - doesn't work 5. Remote login from home - doesn't work 6. Remote login (mobile) - works All I did was changed my router from NetGear to Dlink. Called up Customer service and they couldn't understand why either. Upgraded the router software and it's still not working. I seriously think it's the modem! Dlink has a crappy configuration and somewhat won't allow it to go via certain port!
Answer by Cry Havok · Jul 22, 2010 at 09:43 PM
When trying I'm getting a connection reset error. It could be any number of problems, but I'd start by working through this guide to begin with. If that doesn't solve your problem edit your question with the step you've reached and what the error is.
Answer by VikingTiger · Jul 23, 2010 at 11:28 AM
When trying to access the DVR from within your local network, now that it's set up to listen on port 8000, are you specifying the port number in the URL? Such as: http://192.168.0.40:8000
It's hard to say why it's not possible to connect from outside. There are several possibilites. For example, it is important that the DVR has a proper network configuration. For example, it needs to have a correct "default gateway" setting in order to be able to communicate with remote networks.
Remotely Accessing my Dreambox 1 Answer