Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[andoR]

Hi guys,

I have a big problem with my DCS-5222L. I tried EVERYTHING I can find on Google and in various manuals, but nothing works.

Here's my problem:
Everything works fine when I'm in the same WIFI as the camera, but if I want to watch it from home it always says that there's no connection.
I am using the TinyCam Monitor App on my Samsung Smartphone and a DNS adress from dlinkddns.com.
Everything works with the official D-Link+ App, but I have another camera from another manufacturer, so want both cameras in the same app.
The Hostname and password settings are right everywhere (so says google, manuals and the customer service). I enabled port forwarding and DNS on my router with the IP from the cam and so on, everything I could look up is in shape. I entered the IP adress from my cam in the dlinkddns.com account.

So the question is, why does it work with the D-Link App, but not with the TinyCam Monitor? Is there something wrong with my DNS adress or the settings on the dlinkddns page (there aren't many options...).

I don't know much about DNS or cameras so if you need any more details, feel free to ask. I'm thinking about sending the camera back because nobody else could help and it's pretty useless if you have a cam in your office which you can't watch when you're at home.

Thanks in advance!

[JavaLawyer]

I also recommend re-posting your question on the following board which has some discussion on third party apps: DCS series Network Cameras

[JavaLawyer]

@andoR - check your Private Messages (PM).

[andoR]

Thank you very much!

[JavaLawyer]

Thank you very much!

 

[ReverendTed]

My first guess would be misconfiguration of the dlinkddns.  Typically, DDNS would be set up in the camera and the camera would report its IP address automatically.  This is why the Dlink App works, registering the camera with MyDlink.com is essentially a dynamic DNS service for the camera.
Your application will need to know the External IP address of the location where your camera is connected, then any devices along that chain will need to forward the appropriate ports along to the camera.
For instance, a common set of connections is the External IP address is held by the Modem, which needs to forward the request to a router, which needs to forward the request to the camera.  (In many settings, though, the modem and router are one and the same.)
If you're on the same network as the camera, the External IP address you'd need to use would be found by (for example) whatismyip.com.

[andoR]

Thanks for the help. I think this exaclty was the error. I set the IP on the ddns Page to the IP the router has and it worked.

I hope it still works tomorrow because my connection has a dynamic IP... but that's the reason somebody uses a DNS service and should work finde, right?

[ReverendTed]

I hope it still works tomorrow because my connection has a dynamic IP... but that's the reason somebody uses a DNS service and should work finde, right?

If you had to manually enter the IP address, then it's likely to stop working once your IP changes.
Most DDNS services will be set up on a device (modem, router, camera) to automatically update the service when an IP change is detected.

[aidenator]

I had this exact same issue. Everything on my DCS-934L was working perfectly on the local network, but nothing would make its way through from outside the network. Turns out I just needed to fill in the "Default Gateway" line in the Manual Network Setup section. I put in my router's IP address there and it worked perfectly afterwards. If you don't know your default gateway, on windows go into Command Prompt and type "ipconfig" and it should list it.

[FurryNutz]

Thanks for this information. Hope it helps future users.
Enjoy. 

I had this exact same issue. Everything on my DCS-934L was working perfectly on the local network, but nothing would make its way through from outside the network. Turns out I just needed to fill in the "Default Gateway" line in the Manual Network Setup section. I put in my router's IP address there and it worked perfectly afterwards. If you don't know your default gateway, on windows go into Command Prompt and type "ipconfig" and it should list it.