Print

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

[FurryNutz]

I recommend you phone contact support and ask for help and information regarding this. Please let us know how it goes. Reference this thread if needed.

[mikesweden]

Is this the form I shall use in order to get in contact with the support:

https://services.eu.dlink.com/home/main/SSPLogin.aspx

or is it:

http://www.dlink.com/se/sv/contact-d-link

I posted the issue in https://services.eu.dlink.com/home/main/SSPLogin.aspx before but it was removed and I don't know why.

BR Mikael

I recommend you phone contact support and ask for help and information regarding this. Please let us know how it goes. Reference this thread if needed.

[FurryNutz]

Please phone contact support:
Kontaktuppgifter

D-Link Sweden AB
Box 15036
S-167 15 BROMMA
Sweden

Växel: +46 (8) 564 619 00
Fax: +46 (8) 564 619 01

[mikesweden]

I have found out when the bug happens. It happens on firmwares later than v1.03 b01 on DCS-935L when the HTTP port is changed to something else than 80.

I have been in contact with the technical support and they can reproduce the issue by changing the port number.

Hopes for an update soon.

Best regards Mikael

[FurryNutz]

Thanks for posting the information. Hope it gets fixed soon. Please be patient.

[drbart]

I have this same problem. Configuration is flaky to begin with, but even after setting it up correctly and having it generate a few snapshots, the camera stops sensing.

It remains online, just dead in the water as far as monitoring is concerned.

I am away from the device and the web app doesn't show the firmware revision. It might be 1.06 but I can't be sure. It was an OTA upgrade offered through the Android app.

[FurryNutz]

Link>Welcome!

• What region are you located?

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?

I have this same problem. Configuration is flaky to begin with, but even after setting it up correctly and having it generate a few snapshots, the camera stops sensing.

It remains online, just dead in the water as far as monitoring is concerned.

I am away from the device and the web app doesn't show the firmware revision. It might be 1.06 but I can't be sure. It was an OTA upgrade offered through the Android app.

[ON4KKP]

i have a problem with my 935l  i tried to put new firmware in it, and we had a powerfail during the process, i think my camera is bricked. how can i put firmware into the camera (not wired) only wifi maby by USB?  the standard ssid {dcs-935l-161c}  is changed into {rescue-161c} i have no webinterface.  someone an idea  "to buy a new one, i had figguerd that out by my self LOL" 

[FurryNutz]

I recommend that you phone contact your regional D-Link support office and ask for help and information regarding this. We find that phone contact has better immediate results over using email.
Let us know how it goes please.

i have a problem with my 935l  i tried to put new firmware in it, and we had a powerfail during the process, i think my camera is bricked. how can i put firmware into the camera (not wired) only wifi maby by USB?  the standard ssid {dcs-935l-161c}  is changed into {rescue-161c} i have no webinterface.  someone an idea  "to buy a new one, i had figguerd that out by my self LOL"

[ON4KKP]

I had contact D-link and they give good help with the special software that's needed to put new firmware into a bricked camera and a link to latest firmware.
I didn't had time to test,  of it will work out, i will give the results here.
  for now i'm happy 

The sollution that D-link me gave, doesn't work but i have it works again. 
the camera works with a bootloader!  how it works?
when the camera is bricked  the ssid will change from DCS-935L-161C    THE 161C are the last 4 digits of the MAC-ID of the device, so this is different on all camera's  so when you see 161C  you have to converted into the last 4 digits of your device.
In case of bricked camera: the SSID will change into rescue-161C (without encryption) because of the rescue  in the ssid  you will know that the camera is bricked so without a firmware.
So you have to start with the built-in bootloader, when you connected wifi with the camera (dhcp), the website of the bootloader wil be 192.168.1.30
so in the browser you can browse to the firmware file and start the process, the update wil take at least 140 sec when the leds are out, the firmware is ready, unplug the power and replug it, after a wile you see the SSID  (With encryption) the same as written on the device, and you can follow the config as a new device.  login naam "admin"   and leave password blank.   So i hope that can help this other people.

Thanks to for helping me out,
ing. Berry van der Looij
Integration Multimedia Services
03140 Guardamar España

[FurryNutz]

Good to know. Let us now how it goes. 

[FurryNutz]

http://forums.dlink.com/index.php?topic=66281.0

[heathenchimp]

I have found out when the bug happens. It happens on firmwares later than v1.03 b01 on DCS-935L when the HTTP port is changed to something else than 80.

I have been in contact with the technical support and they can reproduce the issue by changing the port number.

Hopes for an update soon.

Best regards Mikael

I was having my two DCS-935L drop out on a daily basis (at leat one of them) and switching to firmware version 1.03 has worked well for me. Four days since switching one of the cameras to 1.03 and absolutely no unscheduled disconnection issues. The camera still works fine with Synology DiskStation 8 as well. HIGHLY RECOMMENDED fix.

[FurryNutz]

Glad downgrading helped. Enjoy.