Sign in with
Sign up | Sign in
Your question

Cannot access my DLINK DCS-900 camera on the web

Last response: in Networking
Share
August 12, 2006 1:08:33 AM

I have a DLINK DCS-900W camera. This camera is like a web server in itself and you are supposed to be able to see the cam image of let say your home remotely on a web browser via the internet by just entering http://YOUR_IP_ADDRESS:p ORT. So I have setup the camera local IP address to let say 192.68.0.50 and I used port 5000 to forward the image. Then I go to my router which is a DLINK 624 router and where my camera is connected to, and create a virtual web server with local LAN address of 192.68.0.50 and I let port 5000 go through my firewall and filter. So now I should be able to access my camera from the internet but I cannot. But if I go to my local LAN and type in http://192.168.0.50:5000 then I can "see" my camera fine. So that means that port 5000 is forwarding correctly. So what else did I miss to setup my router that makes m camera not accessible on the internet?

If some experts out there with good networking knowledge want to take a look at my router to help me, please e-mail me and I will give you my IP address and my router user name and password and port and you can actually access my router remotely and take a look at the configurations I have setup.

My home was just burglarized and I need to setup this camera to check on my home remotely. My e-mail address is jerrylev@gmail.com if you want to contact me to take a look at the router. Thanks.
August 14, 2006 4:08:47 AM

Just a thought: have you tried accessing your router remotely yourself? Some ISP's (like mine) have a firewall set up by default which blocks many ports that are risky but useful to have open. Also, just to check, are you also writing the :5000 after the IP address when you are trying to access the router from outside your home? Otherwise the forwarding won't occur. Just some things you might want to check in case you didn't.
August 14, 2006 9:26:50 PM

Okay, your router has a public IP address and you set up your router to forward 5000 to 192.168.0.50, which is attached to the switch side of the router. You attach to the camera via: http://PUBLIC_IP_ADDR_OF_ROUTER:5000 and you don't get anything?


Quote:
I have a DLINK DCS-900W camera. This camera is like a web server in itself and you are supposed to be able to see the cam image of let say your home remotely on a web browser via the internet by just entering http://YOUR_IP_ADDRESS:p ORT. So I have setup the camera local IP address to let say 192.68.0.50 and I used port 5000 to forward the image. Then I go to my router which is a DLINK 624 router and where my camera is connected to, and create a virtual web server with local LAN address of 192.68.0.50 and I let port 5000 go through my firewall and filter. So now I should be able to access my camera from the internet but I cannot. But if I go to my local LAN and type in http://192.168.0.50:5000 then I can "see" my camera fine. So that means that port 5000 is forwarding correctly. So what else did I miss to setup my router that makes m camera not accessible on the internet?

If some experts out there with good networking knowledge want to take a look at my router to help me, please e-mail me and I will give you my IP address and my router user name and password and port and you can actually access my router remotely and take a look at the configurations I have setup.

My home was just burglarized and I need to setup this camera to check on my home remotely. My e-mail address is jerrylev@gmail.com if you want to contact me to take a look at the router. Thanks.
Related resources
August 14, 2006 10:18:42 PM

Quote:
Okay, your router has a public IP address and you set up your router to forward 5000 to 192.168.0.50, which is attached to the switch side of the router. You attach to the camera via: http://PUBLIC_IP_ADDR_OF_ROUTER:5000 and you don't get anything?



This is right.

Just a double check, you did tell you router to forward port 5000 to IP address 192.168.0.50

In addition your ISP may not give out 'public' IP addresses, check to see if you WAN address is in the public domain. It is possible that your ISP blocks ALL inbound traffic, just like your router :( 
August 15, 2006 2:05:58 AM

Hello all,

I have forwarded port 5000 to 192.168.0.50. On the DLink router, there is something called Virtual Server and that's how I set it. There is no menu to set port forwarding directly so I think virtual server and port forwarding is the same. Then I can access my camera locally on my LAN by typing http://192.168.0.50:5000. But when I enter http://MyPublicIPAddr:5000, it will time out. I have tried to use other ports also and I have called my ISP (Comcast) who said that they block a dozen of ports, and the ports I used are not on their list.

I also set up remote access on my router to port 8080, so you can actually type http://MyPublicIPAddr:8080 and you can see my router and with a login and password, you can actually change the router configuration. When I go home tonight, I will try to set port 5000 as remote access port to see if I can access my router by typing http://MyPublicIPAddr:5000 or not. If I can then port 5000 is not a problem but it's something to do with how I set my port forwarding on my router. My DLink router is pretty straight forward and there is only one place (virtual server) where I can set port forwarding.

I am offering to e-mail my IP address so somebody with network knowledge who can take a look at my router for me. Sorry I cannot post my IP address here for fear of hackers.
August 15, 2006 2:44:36 AM

I looked up the manual on dlinks site. Link to Manual

Virtual Servers is what you want.

The only thing that you may want to check is what port is used for the 'public and private' ports.

Example 1 from manual:
Quote:
If you have a Web server that you wanted Internet users to
access at all times, you would need to enable it. Web
(HTTP) server is on LAN (Local Area Network) computer
192.168.0.25. HTTP uses port 80, TCP.
Name: Web Server
Private IP: 192.168.0.25
Protocol Type: TCP
Private Port: 80
Public Port: 80
Schedule: always


Example 2 from manual:
Quote:
If you have an FTP server that you wanted Internet users to access by WAN port
2100 and only during the weekends, you would need to enable it as such. FTP
server is on LAN computer 192.168.0.30. FTP uses port 21, TCP.
Name: FTP Server
Private IP: 192.168.0.30
Protocol Type: TCP
Private Port: 21
Public Port: 2100
Schedule: From: 01:00AM to 01:00AM, Sat to Sun
Using the Configuration Menu (continued)
Advanced > Virtual Server continued
Click on this icon to edit the virtual service
Click on this icon to delete the virtual service
All Internet users who want to access this FTP Server
must connect to it from port 2100. This is an example of
port redirection and can be useful in cases where there
are many of the same servers on the LAN network.
August 15, 2006 4:14:59 AM

JJW, thank you very much for your help. Unfortunately, that's what I did too as in example 1 except that I used port 5000 for both public and private and schedule always (I have tried port 80 also) but it doesn't work for some weird reason. I am going to switch to an old Netgear router when I get some free time to see what happens. Thanks.
August 15, 2006 8:22:09 PM

You mentioned your ISP was comcast... I tried to do the same a while back, with the same camera, but a different router (either a netgear or linksys) and had similar luck. I have comcast too.

I did not try nearly as hard as you have at this point, I gave up. Good luck moving forward, Best as I can tell you're on the right track.

An alternative solution, if all you need is static photos (no video) is to write a perl script or similar that downloads photos from the DCS-900 and posts them to your comcast personal web page...

Something like this is what I came up with to do a time laps, It requires a command line program called "imgcon" to make the animation. The DCS-900 can only spit 1 image/sec using this method. This script was written for windows.

[code:1:a8b91182e0]
#!/usr/bin/perl
#
# perl -MCPAN -e 'install Bundle::LWP'
#


#########################################################################################################

use LWP::UserAgent;
$camerauserid = 'Guest';
$camerapassword = 'Guest';
$cameraip = 'http://192.168.0.20/IMAGE.jpg';

open(FF, ">imagelog.txt");
print FF "Begin Logging Images\n";
close FF;



$ua = new LWP::UserAgent;

$req = HTTP::Request->new (GET => $cameraip);
$req->authorization_basic($camerauserid,$camerapassword);

$res = $ua->request($req);
if ( $res->is_success )
{
$istart=01; # starting counting at 1
$end_i=15; # Number of Frames
$i=$istart;$end_i++;

open(EE, ">list.txt");

while ($end_i > $i) {
$res = $ua->request($req);

$data = $res->content;

open (FF , ">testing$i.jpg");
binmode FF;
print FF $data;
close FF;

print "Got Image $i\n";
print EE "testing$i.jpg\n";

$i++
}

close EE;

}
else
{ print "Error: unable to access camera\n";
exit 1;
}

system("imgcon -avi 5 -output test.avi -list list.txt");[/code:1:a8b91182e0]

At one time I had an applet that animated a series of jpeg images without having to create an avi file, but it was slow to load.

I don't know if I have a code snippet for uploading by ftp, but they are relatively easy to come by...
August 15, 2006 9:26:24 PM

I have similar problem with my DCS-900 before. My solutions is forward the router's port number to the exact web sever port number (in your DCS-900 webcam setup page).
So if you open the link to you DCS-900 camera you should be able to change the web sever port in setup page to for example 8082, then forwarding the port in your dlink router to that port. I have no problem access my camera from distance now, but viewing the image is pain. It works well for few weeks, but now it freeze most of the time giving me no access at all. Weird DLink cam.
August 15, 2006 11:12:46 PM

JJW, hey thanks for your perl script, that's pretty neat. I can get the pic on my LAN OK so if I push it out to a web page like you said, then it will do the job.

I am a little bit ignorant on perl script so may be you can help me understand a little bit. I can follow up to the part where you open my camera and grab the jpg photo. But then I get lost on how you post it on the web page. I see that you print to EE and FF. Which one is the web page? And what does list.txt contain?

I suppose that you run this script inside your web page, is that right? So if you put this in a loop, would it refresh for you and update the jpg photo automatically (kind like what the java program in the DLink camera does). Thanks.
August 16, 2006 2:00:58 AM

JJW,

I posted earlier but somehow my post did not appear here, so I will try again.


JJW, hey thanks for your perl script, that's pretty neat. I can get the pic on my LAN OK so if I push it out to a web page like you said, then it will do the job.

I am a little bit ignorant on perl script so may be you can help me understand a little bit. I can follow up to the part where you open my camera and grab the jpg photo. But then I get lost on how you post it on the web page. I see that you print to EE and FF. Which one is the web page? And what does list.txt contain?

I suppose that you run this script inside your web page, is that right? So if you put this in a loop, would it refresh for you and update the jpg photo automatically (kind like what the java program in the DLink camera does). Thanks.
August 16, 2006 2:41:57 AM

By the way, the DCS-900 internet camera series from DLink is pretty neat and inexpensive if you can make it work properly. It costs something like $50 at Fry Electronics when they are on sale. Not only it's like a webcam but it is a web server all in itself in that little box. The pic under low light is not that great but it's good with adequate lighting.
August 16, 2006 2:43:29 AM

This is weird. I have to post twice before my post will appear here. Here is what I just posted but it disappears.


By the way, the DCS-900 internet camera series from DLink is pretty neat and inexpensive if you can make it work properly. It costs something like $50 at Fry Electronics when they are on sale. Not only it's like a webcam but it is a web server all in itself in that little box. The pic under low light is not that great but it's good with adequate lighting.
August 16, 2006 2:44:49 AM

You have to post twice before it comes up. ???
August 16, 2006 6:10:06 PM

yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 16, 2006 6:11:08 PM

yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 16, 2006 6:12:54 PM

yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 16, 2006 7:02:14 PM

Just post something so that I can see the previous post.
August 16, 2006 10:22:38 PM

I run the script locally and the list.txt is a list of images used by the imgcon program to create the video.

The print FF writes the image file out (it is stored as the variable $data) A note on perl, you must write the image file as 'binary'
print EE writes to list.txt with the image file name.

As I noted, the script does not upload automatically to a website (yet), in the current form all it does is capture a series of images, saves them locally and calls an external program (imgcon) to create an avi file.
August 16, 2006 10:32:23 PM

What is up with the posting?
August 17, 2006 6:43:33 PM

Hi all, I see that JJW and one more person posted something but it does not appear on the thread. For some reason, you have to post twice before your post will appear here so I can you repost what you posted yesterday. In particular, I am very interested in the perl script that jjw has posted because that will do the job for me. I have tried to setup my router and camera again using all the different ports (20, 23, etc) but it still does not allow me to see the camera on the internet. I am just about giving up going that route.
August 17, 2006 6:46:07 PM

Hi all, I see that JJW and one more person posted something but it does not appear on the thread. For some reason, you have to post twice before your post will appear here so I can you repost what you posted yesterday. In particular, I am very interested in the perl script that jjw has posted because that will do the job for me. I have tried to setup my router and camera again using all the different ports (20, 23, etc) but it still does not allow me to see the camera on the internet. I am just about giving up going that route.
August 17, 2006 6:47:16 PM

Hi all, I see that JJW and one more person posted something but it does not appear on the thread. For some reason, you have to post twice before your post will appear here so I can you repost what you posted yesterday. In particular, I am very interested in the perl script that jjw has posted because that will do the job for me. I have tried to setup my router and camera again using all the different ports (20, 23, etc) but it still does not allow me to see the camera on the internet. I am just about giving up going that route.
August 17, 2006 7:20:05 PM

JJW, I finally see your posts after posting a bunch of dummy posts to 'flush it out'. Has anyone contacted the admin person about this problem?

Anyhow, I see what you are doing now. What does it take to post an image on a web page automatically? Thanks.
August 17, 2006 7:20:46 PM

JJW, I finally see your posts after posting a bunch of dummy posts to 'flush it out'. Has anyone contacted the admin person about this problem?

Anyhow, I see what you are doing now. What does it take to post an image on a web page automatically? Thanks.
August 17, 2006 7:21:25 PM

JJW, I finally see your posts after posting a bunch of dummy posts to 'flush it out'. Has anyone contacted the admin person about this problem?

Anyhow, I see what you are doing now. What does it take to post an image on a web page automatically? Thanks.
August 17, 2006 10:59:19 PM

[code:1:025b5a695e]###################
#!/usr/local/bin/perl
#
use Net::FTP;

$ftp = Net::FTP->new("upload.comcast.net");
$ftp->login("username","password");
$ftp->pasv;
$ftp->binary;
$ftp->cwd("/pub/ftp");
$ftp->put("imagefile.jpg");
$ftp->quit;

exit;
###################[/code:1:025b5a695e]

This is what I found (a quick search for "perl ftp put")

I haven't tried it but it looks right. I don't think you need the line with cwd unless you want to put the files in a specific directory.

You may want to insert a variable for "imagefile.jpg" so that you can put in a rolling sequence of images or something.

http://search.cpan.org/~gbarr/libnet-1.19/Net/FTP.pm
----------------
EDIT: Added binary mode switch to perl code
Tested, it works for me.
August 18, 2006 2:35:51 PM

yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 18, 2006 2:38:37 PM

Quote:
JJW, I finally see your posts after posting a bunch of dummy posts to 'flush it out'. Has anyone contacted the admin person about this problem?

Anyhow, I see what you are doing now. What does it take to post an image on a web page automatically? Thanks.


yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 18, 2006 2:39:59 PM

yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 18, 2006 2:40:17 PM

yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 18, 2006 2:44:27 PM

yeah, kinda weired, I posted it before in here but it showed up wrong dated and nothing display. Must be some kinda bugs.
Anyways, I have DCS900 and it gave me same problem . My solution was turn on the setup page fo DCS900 and change the port of webserver in setting to for example 8082. Forwarding the port of router to 8082. And voila it should not give you any problem. You should also download latest firmware from DLink.
If you have dynamic IP then you should go to dyndns.org to register for free an alias such as mywebcam.dns.org and then set it up so it will monitor your home IP address. then you can log on to http://mywebcam.dns.org in the future.
August 19, 2006 1:30:59 AM

Thank you JJW, I look at your 2 PERL scripts and I think they will do the job. It's wonderful. I have to build a Linux box to try this out, or may be I will make a Knoppix disk and boot my Windows PC from there. I am anxious to get through this Dlink bug.
August 19, 2006 1:31:41 AM

(repost)

Thank you JJW, I look at your 2 PERL scripts and I think they will do the job. It's wonderful. I have to build a Linux box to try this out, or may be I will make a Knoppix disk and boot my Windows PC from there. I am anxious to get through this Dlink bug.
August 19, 2006 1:32:18 AM

(repost)

Thank you JJW, I look at your 2 PERL scripts and I think they will do the job. It's wonderful. I have to build a Linux box to try this out, or may be I will make a Knoppix disk and boot my Windows PC from there. I am anxious to get through this Dlink bug.
August 19, 2006 1:33:01 AM

Thank you JJW, I look at your 2 PERL scripts and I think they will do the job. It's wonderful. I have to build a Linux box to try this out, or may be I will make a Knoppix disk and boot my Windows PC from there. I am anxious to get through this Dlink bug.
June 14, 2007 8:15:15 PM

Hi, im new here, have same issue, but don't see confirmation this issue was ever resolved. I have a dcs-950G dlink internet cam, belkin 802.11g router, and comcast isp. I can connect internally to my cam but not from outside router. I set virtual fw to pass port 8080 to the cameraip:80. I can connect to myrouterip and get on my router, but when i put in with myrouterip:8080 it does not connect to my cam. Any suggestions would be appreciated, thanks.

Bill
July 23, 2007 9:30:56 PM

Help! I'm having the exact same problem.

I’m trying to configure a D-Link DCS-G900 Wireless-G Internet Camera for use with a D-Link DI-524 router.

I’ve assigned the camera a fixed IP address of 192.168.1.120 and added this address to the Static DHCP Client List in the router.

The camera has a built-in web server, on port 80. I’m on AT&T Yahoo! DSL and understand that port 80 is sometimes blocked. I’ve enabled Second HTTP port 81 on the camera.

In the router Virtual Server setup, I’ve set up port forwarding for ports 80 and 81 to the camera address (192.168.1.120), using Protocol Type BOTH.

When I run Look@LAN on 192.168.1.120 (the camera) it reports HTTP service on port 80 and hosts2-ns (HOSTS2 Name Server) on port 81.

I can successfully bring up the camera by entering either of the following into my browser:

http://192.168.1.120 or http://192.168.1.120:81

I cannot bring up the camera on either port by entering my Router’s IP address into my browser, i.e.:

http://71.225.155.62 or http://71.225.155.62:81

Any advice would really be appreciated!

One other note: I have a TiVo on my home network and have port forwarding successfully enabled and working with this D-Link router. I tried a Trendnet router early today with the same result (TiVo port forwarding worked, Camera port forwarding did NOT work).

One other question: The camera setup has a field for Default Gateway and DNS IP address. Should I be using the values reported by the router, or reported by my DSL modem? (Neither seem to work).

Thanks in advance!

----------------------------------------

Solved: The DEFAULT GATEWAY setting in the camera setup had to match my router's IP address: 192.168.1.1
July 28, 2007 5:58:56 AM

Mitchk. Thanks man! Guess I shoulda RTFineM, huh. There it was...

: )
October 15, 2007 8:30:27 PM

Hello,

I have similar setup as mentioned my mitchk with difference of linksys router SPA2012. I have enabled the DHCP and assigned a fixed IP to the camera and opened port 80 and 81 through port forwarding. I can't get the webcam access through internet. I can access it within local network. I asked SBC, they said they are not blocking any ports. I can access the router through internet as well.
Can someone please help on this with proper steps ?
I guess I am missing something here?

Sam
Anonymous
June 21, 2010 5:27:04 PM

Just a fast reply to this old tread..

I read that seval people have problems with bringing the d-link DCS-900s local ip:p ort to the extern ip:p ort.

I own a DCS-900 myself and I had my share of problems with it too.. Usual it is pretty easy to set up those local ip cameras etc and making portforwards work, and as a level 3 network tech it should be peace of cake, but this camera gave me the grey hair..

I made it work in seval ways over time, but here is a few hints.


- Some cheep routers simply cant pass through the port forwarding correctly to the internal server and back, in this case the d-link camera, if the server (camera) is in the routers dhcp table. The only easy solution to this is to give the webcamera a static ip, and remember to give it a ip that is outside the routers dhcp scope, fx. if the router is set to give ips in the scope : 192.168.1.100 -> 192.168.1.150, then give the webcamera a static ip 192.168.1.151, you set this in the cameras web config. And also remember to set the default router, and dns in the webcam.

- Many routers use diffent kinds of NAT, try play the diffent NAT translations in the router settings and see if any will work with this cam. (It will properly not if you have problems from start)

- Chack the firewall settings in the router, it may block some of the packets in the portforward. You can try disable the firewall for a monent at see if it works..


Regards
Frank


August 14, 2010 9:40:54 PM

I found a nice how-to setup a 920 with a free online camera viewing/recording service here : http://www.tsheffler.com/blog/?p=187
the author mentions potential DNS issues, that might help
!