|
I have my ports forwarded. I set up two different hostnames pointing to 67.54.130.50 I used the Open Port Tool and I got the message that 67.54.130.50: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 67.54.130.50. 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 67.54.130.50 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?
(comments are locked)
|
The question has been closed Jan 29 '12 at 01:44 PM by RotBlitz for the following reason:
Abandoned question
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. OK. Thanks. I guess I need to take my laptop somewhere off my home network and try to connect? My hosts: dalerp.dyndns.ws and 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".)
(comments are locked)
|
|
hi again, sorry Dave, I could not understand you very well, I mean, in concrete, the part you tell me that I was lucky for just trying? and I guess is not necessary for this problem to say for what companies your worked for, I'm very glad of it and I dont doubt about it, neither your knowledge. I didn't wanted to say that, maybe i'll say it wrong,but the thing is I was telling you that in some situations, we are "stressed" and cannot see the solution because the problem overwheilm us, thats why I used the term 'burned' not for insult you. respect to the ports, I just telling what of these i've forwarded, just to remind you that nothing else is needed... because I think there is no such benefit to ISP to block the port for a camera device, with the purpose of not to be installed on their clients... Best regards,
(comments are locked)
|
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: dalerp.dyndns.ws and 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. Good advice! I'm going to check my DVR manual, I don't recall seeing anything there and it's NOT that well written, and I can also call the tech support guru from the company that sold me the system. (He's pretty good and he may be able to supply the missing information you are suggesting.) I appreciate your thoughts and continued assistance. I'll need to find a place to use my laptop away from my home network...
(comments are locked)
|
|
Well, I can see that port [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. I just looked at the DVR network setup and confirmed that the DVR does have it's default gateway set to the LAN address of the router. I did Google the Wildblue/DVR issue and found a post on another site where someone claims that they have this working. The general description of how it was accomplished, matches my configuration. I guess I should take my laptop somewhere outside my home network and try to connect. Maybe I can get in, although other than messing around with a few changes that were suggested...I'm at my original configuration that didn't appear to be working????
(comments are locked)
|
|
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? I only have the satellite link. No landline, no dial up, no DSL, no cable broadband...where I live, the options are dial up (waaaaaaayyyyy too slow) or satellite. 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
(comments are locked)
|
1 2 3 next page »
I was having the same problem but I joined by business and they helped me set mine up, you will need to make sure that the settings on your router and DVR gateway are the same. You may need to open your ports if you go to ping.eu enter this in the address bar and click ping when you get the listing up and then click port test , put your static ip address in and the port for example 8011 click go and it will tell you if the port is open or closed