|
Hi! I already went through the guide and looked up the conveniently appearing posts related to my question. By reading through them I managed to filter the possible issues. As you can see, this is not a very commonly asked question and the problem has probably more weight on the receiving end of the connection than on the config of the router, dvr or update client. The dns host im using is http://conspsg.dvrdns.org:888 and (for now) the external IP of the network the dvr is in is 201.137.20.203:888. The cameras connect to a DVR Pentaplex H.264 MDR688. Im using port 888 just because it appeared in an example and because the net the dvr is in, is pretty active and I fear something might want to use the ftp (80) port sometime. The network (meaning all computers in my house)I am in, has access both through the ip and the dns (I just tested it out on another one 3000 km away from here). But so far the 2 computers that really need the access, get a "the page cannot be displayed" error on their browser. Unlike the case of another post here, the firewall isnt the problem because i disabled it... at least the ones in the computer. I dont know if the router can block receiving connections from a specific port through the httprotocol, but the lap I´m in does have a router firewall and is not having that problem. Considering that I´ve already achieved connection with XP, OS X and 7, I'm guessing the problem isnt the OS. Asides from that, the two pc´s the problem persists on are prrety functional computers that can surf through the vast majority of the popular web addresses nowadays. Can anyone help me find an answer to this problem or give me hints to narrow it down? Thx in advance |
|
I have had that problem a few times as well and the common theme between them was that they all used the same make of router (Netgear). I think it is a firmware problem with some models only but even upgrading the firmware did not resolve the issue, hence replace the router. When I changed the routers to another make (TP Link) the problems went away. |
|
If it works from some locations outside your network then you've largely done everything at your end you can, or need to. The possibilities are:
You can eliminate some of those as potential causes by using the default HTTP port of Thanks for the quick answer. Yes port 80 is the http port not ftp which is 21. And it is always being used... or something like that. I'll try it out.
Sep 11 at 01:27 PM
Neto
Is it true that if I manage to connect with Teamviewer from the pc the dvr is in to the problem location possbilities 1-3 wouldnt be the case anymore? Could I rule them out just doing a ping?
Sep 11 at 02:33 PM
Neto
|
|
Thx to everyone for helping. I finally got to speak with the person who had the problem and it was in fact the port that wouldnt let him get through. |
|
Had a similar occurrence one time. My ISP had a problem with their system, wasn't updating certain DNS servers... for a while. |
That might rule out 3, but not necessarily 1 or 2.
No. What do the problem locations have in common with each other, and what makes them different from the locations that work? Are they all home connections, work connections...? Do they all use the same ISP? So far I havent had the chance to change to port 80. But as far as the other questions go. The problem locations dont have very much in common. One of them is a work connection, the other ones a home connection. The ones that can connect are all home connections. The ISPs differ in every location. I havent really been in one of the problem locations so its difficult for me to find common things. Still theres that thing with the http port. Thx again for the quick answer
Sep 13 at 09:06 PM
Neto
|