Hi I am new to this so bare with me.
When I first set up to observe web cam via internet all went well now nothing.
I checked thru host viewer all seemed OK. I checked thru open port tool and all seemed OK. I checked Dynamic DNS on router and OK including my port forwarding.
ADD: From the sticky
http://swampy.from-ny.net :8090 Router is a D-link dir-825 ver:B1 firmware:2.06NA internal reserved ip 192.168.x.xxx external dynamic ip 74.77.XX.XXX ported to a IPCAM Foscam f18918w
Using Dyn updater & D-link has an updater in router. Also see my comments above.
Hi, Using the URL above you say you can see the device. I take it you get to the user/password screen of the Web Cam, correct? Please verify.
I am interested to know why I can't get to it. The closest I can get to the Web Cam is the Dlink router administration sign in screen.
As for hiding information, I call it protecting! What I did not give I didn't believe would help resolve the issue.
I pinged the URL (DynDNS host name) and checked the port (via internet & PFPortchecker) and all seemed well. Just can't access thru DynDNS host name with the port forwarding.
answered Jan 01 '12 at 03:22 PM
Please work through the sticky and if you still need help edit your question to include all of the information listed at the end of that guide.
Most likely you didn't configure an update client, or the one you did configure doesn't work correctly.
As you chose to hide information it makes it much harder for us to help, however I can see your device. Did you remember to specify the port when you connect? For example
It is a camera I'm seeing.
Are you remembering to test from outside your network? Are you remembering to specify the port as I've shown above?
We can tell your current WAN IP from the hostname - giving us the WAN IP as shown in your modem/router's admin pages allows us to confirm that your update client is working and that your hostname resolves to your WAN IP - that is important information.
The LAN IP and other LAN details can't be used outside of your LAN, but allow us to spot any misconfiguration on your LAN.
In short, please don't assume that we don't need things just because you don't know why. The list in the sticky was built up over the last few years of experience amongst a number of us.
Ping doesn't tell you much unfortunately - at most it says that a host isn't running a firewall. The port checker is more relevant.