Print

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

[FurryNutz]

D-Link posted DCS-2330L Rev A firmware version v1.14 B03 which can be downloaded here: https://www.mydlink.com/download.
Select DCS-2330L

Problems Fixed
1. Fixed SD card non-recording and no recording icon issues
2. Fixed PPPoE issues.
3. Fixed issue where settings were not available when accessing device through portal Advanced Mode in Firefox and Chrome
4. Fixed E-mail Header/notification issues
5. Updated openssl libraries to latest to fix security issues CVE-2016-2107,
CVE-2016-2105, CVE-2016-2106, CVE-2016-2109, CVE-2016-2176
6. Added input validation in certain methods.
7. Fixed “Test FTP” and “Test Email” Button Errors
8. Fixed Login issue with customized User/Password
9. Fixed issues with UPnP AV function
10. Fixed issues caused by loading configuration from early firmware releases
11. Fixed issue where device could not go to preset in the Live Video context

New Features
1. mydlink agent upgrade to 2.2.0-b02.
2. Added UID support
3. Updates to adhere to latest EN300 328 requirements
4. Add support Dlink new anti-brute force mechanism(block only IP, reset when successful login from one IP)
5. Updated support URL

• Network Cameras - Important Posts & Information
  
• Network Cameras - Beta Firmware Terms and Conditions
  
• Network Cameras - Why Have Multiple Hardware Versions for the Same Model?
  
  

Please post your comments and observations as a reply to this thread.

    

[RYAT3]

I haven't noticed anything bizarre happening, no disconnects, appears stable.  Just using to record to DNR-202L.

[RYAT3]

Ok - upgraded to 1.14.  I thought I was seeing things like the IR light had a little light, thought the IR light was going dead - but looked in F/W and saw it was "turned off".

After reading the post in DCS-5222L about IRs being 1/2 lit when "Turned off" on the latest F/W....
http://forums.dlink.com/index.php?topic=65582.msg274396#msg274396


I began to question my 1.14 F/W.

I put it in front a mirror in a dark room with no other IR and confirmed it is on at some very low power level.



I upgraded immediately to 1.14 when I got the camera, so I don't know the characteristics of it before.  I'll try 1.12 again at some point this week.

(turning the IR on - does light up the room). Image settings are default.   

So does anyone else see this issue?  Or is it present in 1.12?

I have a 1.02 F/W on an outdoor camera, and I can't say I've noticed the IR on at a very low power level.

[RYAT3]

*confirmed. F/W 1.12 -the IR is completely off when "Turned Off".

So what gives in 1.14?

[FurryNutz]

I've passed this on to D-Link for review. Please be patient.

[RYAT3]

Thanks

[remoteCamsFarAway]

Just upgraded my three 2330L remote cams to 1.14.03 from 1.12.  Tried for the last couple of weeks and couldn't get it to work on any of the cams either directly to its web server or via myDlinkLite.  Today it worked on all three cams.  What's different?

1) I was getting many lockouts from the DNR-312L in the local network.  I had previously removed the cams from the 312L camera list but I was still seeing those lockouts from the 312L.  I believe they were interfering with the download.  I have since upleveled the 312L to the latest firmware and again removed the cams from the 312L camera list with the new firmware in place.  That seemed to stop the undesired accesses.

2) This time I was using the 1.14.03 download from the US site.  I think I was using the one from the UK web site last time since I did not see it on the US site.

All cams came back online following the upgrade.  One of my cams that had dropped out of myDlinkLite but was accessible via its web server also came back to myDlinkLite following the upgrade.

Positive experience so far.  Will post any issues that occur.

[FurryNutz]

Glad the new FW is working well. Enjoy. 

Just upgraded my three 2330L remote cams to 1.14.03 from 1.12.  Tried for the last couple of weeks and couldn't get it to work on any of the cams either directly to its web server or via myDlinkLite.  Today it worked on all three cams.  What's different?

1) I was getting many lockouts from the DNR-312L in the local network.  I had previously removed the cams from the 312L camera list but I was still seeing those lockouts from the 312L.  I believe they were interfering with the download.  I have since upleveled the 312L to the latest firmware and again removed the cams from the 312L camera list with the new firmware in place.  That seemed to stop the undesired accesses.

2) This time I was using the 1.14.03 download from the US site.  I think I was using the one from the UK web site last time since I did not see it on the US site.

All cams came back online following the upgrade.  One of my cams that had dropped out of myDlinkLite but was accessible via its web server also came back to myDlinkLite following the upgrade.

Positive experience so far.  Will post any issues that occur.

[FurryNutz]

Can you down grade one of your cameras to v1.02 now that these version have been removed and see if this changes the behavior please?
You could provide us with more information about your camera configuration and networking configuration.
What Mfr router are you using?
What channels are you using?
How many devices are connected to the main host router?

Try using static IP addresses for the cameras that is out side of the main host routers DHCP IP address pool
Is uPnP Port Forwarding enabled on all cameras? Mine is and my camera is solid all the time.

After the last FW 1.14 upgrade both my 2330L are loosing Wi-Fi connectivity and I have to recycle the power each time. they work for couple days.
it used to work fine on 1.12 and I had 4 months of continuous uninterrupted no issues , until the latest 1.14 firmware...

I have been using D-link cameras 4 different models  for about 4 years now and I have been trough 15  FW revisions and I  can say that D-Link is not testing  their SW and consumer base are the guineapigs. Sad ... but  that is the reality. 

No more D-link's for me. 

[FurryNutz]

You can find v1.14 still on the MDL site:
https://www.mydlink.com/download

[Cam_2015]

Here is my experience from the upgrade to 1.14:  Upgraded and had to do a factory re-set afterwards to get connected (annoying).  Tried to roll back to 1.12, but could not tie to the D-Link after rolling back, this is a one-way upgrade.  Even though cam would take the 1.12 by rolling back, it just would not be picked up by the app until I put back to 1.14.  I have 3 more cams still on 1.12 and would not upgrade them.

1.12 is (was) not really that stable, there have been disconnects about twice a week, but from outside home network I can still connect and reboot (no problem), but with the 1.14 one of the cams went off line after 3 days of continuous run, I was not able to connect it from outside home network -- had to wait till I get home to reboot via power supply.

[FurryNutz]

What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
How many other wireless devices do you have connected to the main host router?

• Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
• Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.23 and .24 and so on.  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

Here is my experience from the upgrade to 1.14:  Upgraded and had to do a factory re-set afterwards to get connected (annoying).  Tried to roll back to 1.12, but could not tie to the D-Link after rolling back, this is a one-way upgrade.  Even though cam would take the 1.12 by rolling back, it just would not be picked up by the app until I put back to 1.14.  I have 3 more cams still on 1.12 and would not upgrade them.

1.12 is (was) not really that stable, there have been disconnects about twice a week, but from outside home network I can still connect and reboot (no problem), but with the 1.14 one of the cams went off line after 3 days of continuous run, I was not able to connect it from outside home network -- had to wait till I get home to reboot via power supply.

[Cam_2015]

Router is a Netgear, model WNDR4500 (it has the latest firmware V1.0.1.40_1.0.68 ).  As for distance from the router, I have many cams from 20 to 40 feet, they all behave the same one time or another.  All cams are connected at 2.4 Ghz dedicated to cams only, every other device or smartphone is connected at 5 Ghz, don’t have any cordless phones.  My neighbors are not very close.

All cams have dedicated static IP configured, that’s how I pick them up outside of home network via 3rd party apps (have many of these apps I use).  The uPnp is already enabled.  Cams do work fine for few days from outside, sometimes for 4-5 days, and then they go offline every so often.

Thanks.

What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
How many other wireless devices do you have connected to the main host router?

• Any 2.4Ghz or 5Ghz cordless house phones or WiFi APs near by that maybe causing interferences?
• Any other WiFi routers in the area that maybe causing interferences? Link> Use a WiFi Scanner to find out. How many?

I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.23 and .24 and so on.  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

[FurryNutz]

How many cameras do you have all connected to the main host router?

[RYAT3]

Ok - upgraded to 1.14.  I thought I was seeing things like the IR light had a little light, thought the IR light was going dead - but looked in F/W and saw it was "turned off".

After reading the post in DCS-5222L about IRs being 1/2 lit when "Turned off" on the latest F/W....
http://forums.dlink.com/index.php?topic=65582.msg274396#msg274396


I began to question my 1.14 F/W.

I put it in front a mirror in a dark room with no other IR and confirmed it is on at some very low power level.

It's been more than a couple months now.

What is dlink doing to fix this? Nothing?  Several models latest f/w's were affected.