D-Link DCS-942L :: Cannot Get Camera To Work On PC
Jan 4, 2013
I just purchased 2 cameras and have one set up.
Firmware V 1.12
Works great on my android phone and connects fairly quick. When I try to see the camera image on my PC with windows 7 64 bit, I log into my d-link and it shows the camera name on left side of screen, then says Java run time environment not installed.I uninstalled java 5 times and re installed both 32 and 64 bit but keeps coming back as not installed. Camera is set up wirelessly through a Belkin router, so far no EZ config
Has anybody gotten the FTP option to work with this camera? And if so how did you set up the path to point to the ftp share. The instructions say one thing but that one thing doesn't work. FTP is setup locally on my NAS box which does work. Or is this another one to add to the Firmware which list?
I have a new apple airport extreme wireless router and have done all the port forwarding and gave the camera a static address and cannot view my camera outside my network. I also have done the dyndns service also. I will note if I change the http port in the camera settings to say 82 I get a black screen and cannot view my camera till I switch back to port 80. Reason why I want to do this is I need to view my camera for more then 60 seconds.
i bought wireless camera dcs942l everything works but my sd card 32 gb is not recording the camera is not recording in my sd card i formated sd card still not recording camera works good quality picture network working but not recording on my sd card and i can not record in my computer
Months ago i can enter in the camera interface by using 192.168.1.100 , its correct ip to enter in the cammera ? Now i dont know what is happening i connect the ethernet cable correctly from PC to the camera and i type in the browser : 192.168.1.100 but nothiung happen ?
I can access my DCS cameras directly using several iPhone apps such as IP Cam Viewer Pro. Is it possible to access the camera directly using a web browser (I have tried without success) e.g. do you need to use a specific port?Also, the DCS-942L has RTSP. I am not clear as to the difference between RTSP and HTTP streaming of video, any resource that clarifies with respect to D-Link cameras?
It didn't fill it up completely, it stopped at the 200 meg free mark, however I have cyclic checked (which btw is not mentioned anywhere in the manual). I assumed this option would cycle by deleting the oldest file to continue recording.
Just got this & set it up today. Wanted to buy a couple more in the next few days; but wanted to test out the D-Viewcam service. The application (D-Viewcam) is not able to find my camera.I have 'ticked' the uPNP & the forward; tried to disable it as well. No luck.
Camera 942l is on ver 1.1 D-Viewcam = v 3.2 Both reside on the same LAN
I'm able to view the camera on the browser. And on my phone.
I installed my first IP camera. Things seem to have went ok with the installation andd router. I can view the video live from mydlink.com.I've tried the dlink software, but it can't find the camera so I can control recording options, ftp, etc. i've also tried 3rd party software that can't find my camera.I'm fairly internet savvy, but do not have access to my router admin atm. (cable company installed their own) My home ip address is supposed to be dynamic. I thought that would cause me problems viewing from mydlink.com, but it hasn't so far.
In my Ipad (I have Dlink+), I can only see 1 minute of the Cameria 942L...the faq says that I need a conection witn Upnp.I have a Cisco EA2700 and I check the box of Upnp,,but I still cant see my camera from more than a minute,, then I have to reload.
I have four DCS-942L cameras and a 2012 model Airport Express router. I cannot view live video from outside the router in any fashion other than mydlink.com's poor quality time-limited forwarded video. Here is what I have done.I have manually mapped four TCP ports through the router for accessing the cameras' web servers. This works--I can access the camera settings that way, albeit with NO SSL support (dammit). So, fundamentally, port forwarding works on this router. The "live view" accessed through the camera's web server does not work, though.I mapped port 554 on each camera to ports on the WAN side of my router, TCP and UDP.I have made sure that the external ports set on the camera under "Enable UPNP port forwarding" are the same as the external ports set on my router. (Otherwise the web server wouldn't work from outside.)When I access the mydlink web site from inside the LAN, I can view my video. When I run netstat -n -p tcp, I can see connections open to the local 192.168.0.* addresses of my cameras, so it is connecting via the LAN.If I connect to the Internet outside my LAN, and use the mydlink web site, I get the forwarded, mini-sized video with a 60 second limit. netstat reveals that connections are being attempted to the INTERNAL ip addresses of my cameras, which of course cannot succeed from outside. In addition, if I try to stream video using QuickTime Player from outside, using the URL [URL], the player connects, then says "waiting for stream" and then "switching transports." It gets stuck there and does not proceed. On the LAN, using the local IP address, I can stream video just fine.
Any way to change this?What other ports do I need to open to make the video stream work? I tried mapping ports 5556-5559 to one of my cameras, but that did not work. Also, I have four cameras and need to be able to map to all of them for this to work.The AirPort Express supports "NAT Port Mapping Protocol" which, from my limited research, is not the same as UPNP. How to successfully viewed video from outside a router without using UPNP?I have scoured these forums considerably and have read some success stories using UPNP. From the DCS-942L manual, it seems like I should be able to set up manual port forwarding in some fashion to make the video stream work. Clearly, though, some auxiliary connection is being attempted and the client cannot get through to the camera. Is it possible to even pick this statically, or is the port always dynamically chosen by the camera and therefore absolutely must be set up on the router using UPNP? If I can't make static port forwarding work, then these cameras are headed to camera heaven soon.
The company has a glitch that they are not sure if they will fix so you can't record with mac. I am unable to return my cameras to staples and Im out the money for the memory cards I opened. It says you can record with MAC clearly on the box!!!! Bad business practice for STAPLES and DLINK.
I seem to be struggling to connect more than 4 cameras to my (ISP-supplied) modem/router by Netgear CGD24N via WPS. I'm on my 5th camera now (already have 3x 930L and 1x 942L) but the newest 942L just won't connect to the network at the moment and there's definitely no faults here as I swapped cameras today at the local retailer (and got an A3 942L!).I've even tried connecting the camera to my wireless extender (Netgear WN3000RP) but no luck there.
So far it has only worked twice for short periods of time (enough for me to configure the cameras) but since then I can't actually get it working. I've got a couple of spare wireless routers lying around too and should be receiving a DIR-600 soon (from the Netgear promotion in Australia) which could be useful?
I have a 932L already and wanted to add another camera, so I purchased the 942L in the US. I live in Canada. The 932 works perfectly, emailing me without any problem. Set up was a breeze. This new camera appears to be a problem. I cannot get this turkey to email. I am very computer literate, and I have been working on this thing for ages now without success. I would like to return this thing and get another 932, but hard to do from here. I see from these forums that nobody else appears to have gotten it to work either. By the way, I upgraded it to the latest version firmware, no change. How to email images using the motion detection?
I tried several times to see the DCS 942L camera picture on my Samsung Advance S smartphone on UMTS 3G net but also setting the video parameters profiles at minimum (64 Kbit/s) it does not work. The MyDlink lite version is the 2.6.1. release. Locally ,using Wi-Fi it works well of course.
I having issues with DView 3.11 on a WinXP Professional with SP3.There are 4 DCS 5300G cameras wired to the router.I can see the cameras using IE, but when I try to configure the DView in the camera section with the autodetect button it will show an error that the camera cannot be identified.I had checked the IP address, port, user & pass everything is ok. I even hard reseted one of the cameras and it won't work.
I have my 942L set up for continuous recording. When I look at the files, the camera will record between 20 and 55 seconds, end that file and start another. The next file then starts between a few seconds and as much as 40 seconds later leaving a gap in the video recoding. The file sizes are all different and the amount of record time is different for each file.
Also, about 80% of the time, the time increments a few seconds on a playback and then stops updating even though the video is longer.
I just got the camera today, looks good, works good, at least so far.. BUT I was SURE this camera had a battery and charge function!? What's the point of having this camera if I can't place it say inside my car or in the garage (where it needs to be hidden, alas I can't use any cords!)?
I asked a question recently about accessing camera via a smartphone but I realize that's not really the correct question. The smartphone works fine locally with wifi and has a browser available.
The real question I have is what is the easiest way to access any camera via a browser from a remote location. Years ago tech friend assisted me access my DCS-910 using dyndns.org. It was free and worked great. I guess it went away when they started charging for a basic account.
Is there an easy way to access a camera without using dyndns even if it involves putting in an IP address instead of a convenient domain name? I would just like to see at least one of my cameras in a browser off-site. If I have to pay $20/year for dyndns I can but I would prefer not to if possible.
I just got the e4200 the other day and everything has been great except I can't seem to get my ABS megacam 4 ethernet camera to work.It was working fine with my old router, and if I plug directly into it it works, but I can't access it through the router at all. I can see the camera in my routers client list, the camera is set to DHCP and it is assigning it an IP address but I can't connect to it. From my desktop pc (wired) I can using the IPwizard software that came with the camera and it will see the camera on the network but it wont connect to it, my wireless clients can't even see the camera using the same software.
As DCS-942L IP cam is compatible with "NVSCGI APIs" (search this string on a search engine and you will find some useful PDF docs), many features of this IP Cam may be enabled or disabled using any web browsers, for example we can manage the motion detect.
I just bought new 942L (HW Rev3, 1.12 FW) and the only profile which is used to stream to iPhone or Web browser in mydlink is profile 3 which is limited to JPEG. Is there some way how to change the profile to be used for streams or is there a way how to make to profile 3 something else then JPEG?
The DCS942 (which is right near but facing the other direction) is about 2 meters away from one of the 932's but the 942 keeps going offline - it comes back on and off probably 4-5 time during a 24hr period.
This is most frustrating - it would look like Wifi signal strength could be the issue but the other 932 right near it doesn't have this issue?
I initially set it up for static IP, which was a mistake for reasons I probably don't need to go into here. Having recognized my mistake, I've been trying to hard reset it so I can convince it to acquire its IP address by DHCP, but each time I reset it and return to the "First, select your camera" screen in the setup wizard, I'm faced with a single choice: the device as I first set it up for static IP. I don't seem to be able to convince it to give up that erroneous static IP address.I have read the FAQ section on hard reset. I've held down the reset button for a lot longer than 6 seconds while the cam was connected to power and ethernet, and I've watched it go through the sequence of flashing blue reset and WPS lights until it settles down, but this doesn't change the situation, evidently.
I'm trying to connect to the camera DCS-942L through the Rtsp Protocol.
Link do this : [URL]
But the video signal no. Tried different players. Players determine the model of the camera , but no image and after a couple of minutes is open. What I'm not doing all right?" My link has the correct view ?
Any replacement bracket or some other way to easily mount the 942l in a window? i have a long window next to my front door i want to just stick this someone about shoulder high in that window looking right to the door so will see anyone who comes.
My Dlink DCS-942Ls had been updated to the latest firmware both 1.12.1608WW and 1.12.1628EU. (I grouped them into two firmware devices). They are all H/W version A1, agent version 2.0.15-b11. If I setup time to automatic time configuration and sync with NTP servers ( all from drop down list and Thailand NTP server time1.nimt.or.th) , they did not work and I must set time manually every times I power off and on these IP cameras. I knew that this issues has been raised for long times and still exist in the current firmware.Simple way to eliminate this problem is specifying NTP server into IP number. ping your national NTP server URL and then get the IP address , e.g. time1.nimt.or.th has IP 184.108.40.206 , or ntp1.dlink.com has IP 220.127.116.11. I have tested many ways and the results can be comfirmed that URL NTP letter cannot sync time but IP number can do. I also has a DAP-1360 Repeater mode and test with its "System Check" ping test, the result are success either URL NTP server name and IP number. NTP protocol is different to ping test. I'm not sure that which parties (ISP, DNS, Router, IP camera device) should fix this error. I decided to specify NTP server with IP number to all network devices from D-Link. Minor risk may occur if a national NTP server change its IP number.