|
I lost my ability to connect via "dyndns.org" to my IP cam (more details later). I have read a number of the threads on this on what to check, but unfortunately, at least for the time being, I am remote and cannot access the gateway router or camera information. I am hoping someone can give me suggestions as to what might have happened, and why, and depending on the potential cause(s), whether there is some "fix" that can be enacted remotely. The camera access (port 80) and video were working perfectly via iPhone remote access. Sometime within the next day, I could not connect with the camera login page - which has been the status for 2 days now. The error messages I get vary by device: on my computer "network connection problem"; on my Blackberry "connection timed out"; on the iPhone "cannot connect to the server hosting the webpage". I know that my remote computer connection to "dyndns" is good as my son has a camera which I have no issue logging into remotely (noting the dyndns name is different). Additionally, no settings were changed on my gateway router or network between the time the camera was accessible and the time it was not. Can someone please shed some light on what might cause a perfectly functional remote cam access to go bad? Thanks.
(comments are locked)
|
|
Note that all Dyn is doing for you is resolving a hostname to an IP address. It isn't involved in the actual connection beyond that, so that it works for an unrelated hostname means nothing. There isn't a lot you can do remotely. The problem could be anything from a power outage, loss of Internet, that the update client you've configured doesn't work... You need to get somebody on site and have them work through this sticky. That also lists the information we need to be able to help you. Sorry, guess I should have posted my "thanks" as a comment rather than an "answer". Many thanks. I've arranged to get my son on-site this evening; we'll try working through the suggestions. Issue resolved; many thanks. The problem/solution was covered in the "sticky". The camera IP address was incorrectly set within the DHCP range of the router. After some period of good operation, a conflict must have occurred which locked up the router. Resetting the router and changing the IP address (and port forwarding address), and voila! - back in action.
(comments are locked)
|
|
Many thanks. I've arranged to get my son on-site this evening; we'll try working through the suggestions.
(comments are locked)
|
