- Contact Us
I have my ports forwarded. I set up two different hostnames pointing to 126.96.36.199 I used the Open Port Tool and I got the message that 188.8.131.52: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 184.108.40.206. 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 220.127.116.11 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 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.
Answer by VikingTiger · Jul 23, 2010 at 02:26 PM
Thanks. Yes, I was using 18.104.22.168:8000 and I got the message "Internet Explorer can't display the Website". My router shows the following WAN settings: IP Address: 22.214.171.124 Subnet Mask: 255.255.255.0 Default Gateway: 126.96.36.199 DNS: 188.8.131.52 I just checked my DVR and the Gateway was reporting 192.168.0.1 (a private IP address) I just changed it to 184.108.40.206? Of course, I can't try it remotely? I CAN'T access my DVR through my network now that I changed the http Port from 80 to 8000 and changed my port forwarding on my DLink 1310 router from 80 to 8000?
First, it must work locally. When you're testing this locally, don't use the public IP - use the private IP of the DVR. When testing in Internet Explorer, remember to prefix with "http://". Internet Explorer doesn't know what protocol to use when specifying a non-default port (8000) unless you explicitly specify it.
The gateway address must be the private IP of the router. 192.168.0.1 sounds right. All local devices must use local addresses to communicate with each other.
When it works locally on port 8000, it's time to check whether it works from remote locations. We can help you test that if you want.
A question: Do you have only one router/modem or do you have several of them?
Answer by cygnusarg · Jul 23, 2010 at 03:33 PM
Hi, I have the same problem, and now is running ok.
Recommended: Try to start over again. why? maybe your doing it right but your burned XD - keep reading.
Its just a port forward from your router to the DVR IP with ports 80,3777,3666,37778 ; 4 rules must be created on your router and nothing else (excep for the ddnds acount hehe)
The DVR config must say in the multicast the same IP of the GW, I mean, the router.
After all that essencial steps, TURN OFF BOTH THE ROUTER AND THE DVR
you wont beleive me if a tell you I was crackin my head 'bout 3 days ago trying to make it visible from outside 'cause i know how (I thought hehe) to configure it but the thing was this is not working, and when I decidec to lay down on this, it works just whitouth touch anythin else..
PD: excuse my english language please ;)
Remotely Accessing my Dreambox 1 Answer
Cannot load hostname and cctv web client 3 Answers