• March 28, 2024, 09:27:49 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: [1] 2

Author Topic: 936L - the most frustrating camera ever  (Read 7815 times)

silvertank

  • Level 1 Member
  • *
  • Posts: 10
936L - the most frustrating camera ever
« on: June 11, 2018, 08:00:45 AM »

I have 6 cameras in my house, and recently one of my 930L's died. I wanted a wider viewing angle, and the techs at D-Link suggested the 936L.
I ordered one and it arrived last weekend. While install went fairly well, I can't seem to convince the camera to work outside my home network.
Here are the details.
1. I configured the camera using MyDlink lite on my iPad. This got it on the wifi, then I changed the IP to the old static IP of my dead 930L.
This killed the MyDlink cloud camera, but I'm not too worried about that. maybe someone could help with that later.
2. Now that I could access the camera using a web browser (IE, because apparently nothing else works), I set the HTML to port 444 to match the old port of the dead 930L. Now I had the 936L setup to all the same parameters as my old 930L.  Which are port forwarded in my router.
3. I was able to get both OWLR on my iPad and IP CAM controller on my Windows 10 phone to work with the new camera. While on my home wifi it was fine.
4. Outside my home network I get nothing. No response on either my iPad or phone. No response using a web browser (which works fine for ALL my other cameras). This is confusing as my 936L is configured the same as my dead 930L, and that worked fine (until it blew up).

I have tried multiple apps, multiple devices and can't get the dang thing to work. Any suggestions would be great. Thanks!
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 936L - the most frustrating camera ever
« Reply #1 on: June 11, 2018, 08:15:40 AM »

Link>Welcome!

  • What Hardware version is your modem? Look at the sticker under modem.
  • Link>What Firmware version is currently loaded? Found on the modems web page under status.
  • What region are you located?

Camera:
Link>Welcome!

  • Link>What Firmware version is currently loaded? Found on the DCSs web page under status.
  • What region are you located?

What Mfr and model is the main host router?
Port Forwarding is not needed with these cameras. Just uPnP and a internet service that has a signal NAT condition with your ISP modem and any external routers.
I have this model camera alone with a 933L and 960L. Access all cameras from MyDLink app from work and home.

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #2 on: June 11, 2018, 09:18:30 AM »

Thanks for the quick reply.
I tried to Teamview into my home Pc and get some more info, but I seem to have messed up that connection. Everything breaks at once.
I have considered using uPnP to streamline port forwarding to MyDlink, but not all my cameras are DLinks. Unless there is a way to add non DLink cameras, then I have to stick with port forwarding and apps like iSpy, and OWL (which are vendor agnostic)
I am in Tampa FL, USA, using Frontier Internet, stock Frontier fiber router/wifi AP. I'll get model specific info for you.
I was able to get into the 936L before I messed up my home PC. I changed the Dynamic DNS to No-Ip and added my credentials (just in case that was the issue)
I then added a DNS server to the 936L, and then lost connection when it rebooted. For some reason, that cause the PC to lose it's routing.
Anyway, I'll know more tonight when I get home.
Logged

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #3 on: June 11, 2018, 10:48:02 AM »

Question, are these the current URLs for video on the 936L? There is too much conflicting info out there right now

MJPEG video/mjpg.cgi
JPEG   image/jpeg.cgi

also, do I need to put the user/password in the URL? I really need a good way to test streaming from any browser.
That way, I will know if the camera is the problem or my network settings
Logged

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #4 on: June 12, 2018, 06:38:53 AM »

OK, I got it to work.... sort of

Let me begin by saying that if you want an easy to use webcam and you DO NOT want to use MyDlink, then the 936L is not for you. It is specifically designed to function with MyDlink to the point where it's very difficult to use as a regular webcam.

First off, the setup function will push you to register the camera with MyDlink. Don't do it, that will misconfigure several camera settings. Instead, skip MyDlink and finish connecting to the local wifi. After that, get into the camera's webpage and change the network parameters to hard code the IP. BTW, having a webpage that only works in Internet Explorer is about the dumbest thing I can imagine. IE is the least stable browser platform and most people don't even use it. I have IE on my Windows phone and the camera's webpage still shows "unsupported browser". This is another example of pushing the user towards only using MyDlink.
After you register the camera correctly to your network, you should be able to open the correct ports to push streaming to the Internet. If you have a DLink router, then uPnP will do it for you. Too bad 99% of us use our ISP's routers. Getting good video on the other end is also tough, since the camera uses 3 channels and high end video. The default channel (1) is high def, so you may want to change it to the smaller size of channel two (2). This will stop the high def channel from timing out on most webcam apps. If the app can select camera channels, then use channel two (2), and you should be ok.
Honestly, DLink has a really good camera in the 936L if they would just stop cramming MyDlink down our throats. At $30 USD, it's a good deal. It has awesome video, good security features and I really like the mounting bracket. By shaving down the plastic hinge stop, I was able to convert the base into a window mount. Using poster putty, I mount the ring base to the window; then swing the camera down 180 degrees to face outside. This is where the horizontal adjustment ring really shines. I just rotate the ring so the camera is now rightside up. Infrared has to be shutdown, because it just bounces off the glass and blinds the camera. Still, for the money, it's a well made camera. DLink, please stop trying to push your MyDlink site unless you plan to allow people to register non Dlink products. I like your cameras, but I like Foscam as well.
« Last Edit: June 12, 2018, 06:42:22 AM by silvertank »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 936L - the most frustrating camera ever
« Reply #5 on: June 12, 2018, 07:40:23 AM »

1. Ya, D-Link cams are not supporting of web cam configurations.
2. You can use FF ESR version of there browser. Still supports plug ins. Most other browsers have blocked plugins so is a reason why they don't work anymore. It's a security related issue with browsers.
3. You don't have to use mydlink services if you don't too. Its handy for remote access though.
4. You can always use a 2ndary router with your ISP modem. Most ISP modems are not designed as well as actual dedicated routers.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #6 on: June 26, 2018, 07:58:13 AM »

More problems. The camera quit after a power outage. I update the firmware to the latest version from the DLINK support page. the camera came back locally but it's not working remotely. All the other cams are fine and nothing changed on my router's port forwarding table. I use DDNS setup through the router, so DNS is handled correctly. Not sure why the cam is not forwarding but I can't do anything till later today. Any suggestions on what I should check?
The camera is mounted in a window, but so was my 930L. It works locally, so I assume it works and didn't shutdown. It also pings just fine.
Going to give it a few more efforts then send it back to Amazon.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 936L - the most frustrating camera ever
« Reply #7 on: June 26, 2018, 08:57:03 AM »

I have a static IP address set up on my 936L, outside of the IP address pool of the router. My pool is set for .100 thru .200. IP address on camera is 192.168.0.94. No PF configurations used on my router for any cameras. Just uPnP. Seen no problems with cameras coming back on line after a power outage.

What is the Mfr and model# of you ISP modem/router?
What wireless modes are you using?
What channels are you using?
Distance between camera and wireless router?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #8 on: June 26, 2018, 09:18:14 AM »

I'm using the same type of IP addressing, low numbers for my cameras, +100 for DHCP. Static PF on the ISP router, which has always worked well.
The old ISP didn't do uPnP, so I've just stuck with PF tables on the new routers.

1. I'm fairly sure my ISP modem is an Arris NVG468MQ, but I'll verify that tonight
2. I left the wifi on standard so B/G/N, though I may have turned off B
3. My Meraki MR18 AP is set to  Channel 1 and the ISP Arris is channel 11. The camera prefers the Meraki though the Arris is closer to it
4. Distance to the Arris is approx 12 feet with one wall in between, distance to Meraki is approx 30 feet with 2 walls in between

The camera pings and local viewing works without issue, so I'm guessing something went South when I upgraded the firmware. Possible the DNS server info was scrambled again. My ISP (Frontier) has this goofy way of not using defined DNS servers. For some reason, that gives this camera heartburn.
« Last Edit: June 26, 2018, 09:22:10 AM by silvertank »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 936L - the most frustrating camera ever
« Reply #9 on: June 26, 2018, 09:32:02 AM »

Have you specified static DNS on the camera as well?

After the FW update, did you do a factory reset and set up from scratch?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #10 on: June 26, 2018, 09:57:34 AM »

1. Camera has always been static. After the FW update the camera started pinging and working correctly, so I assumed the configs stayed after the update

2. No, I only checked to make sure the camera's http page was working and that I could see it internally. Is a full reset required after a FW update? Seems wasteful.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 936L - the most frustrating camera ever
« Reply #11 on: June 26, 2018, 10:06:05 AM »

Sometimes in odd cases like this, a factory reset and set up from scratch maybe needed. Something to try.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #12 on: June 26, 2018, 10:16:48 AM »

yeah, I agree. I'll check all the settings to make sure nothing changed during the update. If that doesn't fix the issue, I'll reset and try a full reload.

Seriously thinking about just using another 930L or some other brand. Too many quirks in the 936.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: 936L - the most frustrating camera ever
« Reply #13 on: June 26, 2018, 10:33:27 AM »

I haven't had any major issues for a while. Only issue I had initially was I could not get it connected to my DIR-890L at all. I tired other routers and it connected there. Come to find out that I had an early edition 890L. D-Link graciously replaced the 890L, then the 936L finally connected. Had no major problems since then. Accept for the false motion detection's which was fixed a couple of versions back. Other than these two items, camera has been good.

Wondering if you maybe have just a bad unit...
« Last Edit: June 26, 2018, 10:51:14 AM by FurryNutz »
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

silvertank

  • Level 1 Member
  • *
  • Posts: 10
Re: 936L - the most frustrating camera ever
« Reply #14 on: June 26, 2018, 05:31:17 PM »

Well, now it seems my ISP router is smarter than I give it credit. It is an Arris NVG468MQ Frontier modem/router/AP
My port forwarding apparently not only uses the IP but also the MAC. So when I changed from a 930 to the 936, it had issues with the change.
Why did it work initially? I dunno. Maybe uPnP decided to work? It is turned on at both sides, but didn't work after the power outage.
I'm guessing the bad entry in the IP forward tables messed up everything. It works now, so I'll see how it fairs during the next outage.

Problem #2 is my network UPS is not working right. Probably took too many hits and needs to be replaced. Maybe the camera couldn't find a network and just timed out. Who knows, it's working for now and I'm off to shop for another UPS.

I still hate having to use an old copy of IE to manage the camera, but maybe if we complain enough we'll get a new update.
Logged
Pages: [1] 2