The Graveyard - Products No Longer Supported > DCS-5029L

DCS-5029L Not sending motion snapshots to FTP server

(1/4) > >>

cjens19:
I've got 3 cameras, 2 older DCS-932L's, and a newer DCS-5029L. The 2 932's work flawlessly as far as sending motion-detected image snapshots to an FTP server of mine in the Azure cloud. However, I cannot get my DCS-5029L to send images. I can see in Filezilla on my server that the 5029 is connecting, but no images ever are sent. I also can tell that motion is being triggered because in the Live Video tab in the GUI, the little running man in the top-left flashes orange, and then I see the connections appear in Filezilla on my server, but no images. I have verified several times that the FTP connection info is the same across all 3 cameras. The 2 932's worked on the first try and I haven't had to mess with those at all, but the 5029 seems to be having some issues. I'm on current 1.11 firmware version, but was thinking of downgrading to 1.02 to see if maybe the newer firmware is just buggy. Has anyone reading this successfully gotten a motion event to send images to an FTP server with a 5029L? One odd thing I noticed with my 5029's FTP connection, is that filezilla sees it as passive, even though I have the Passive Mode box Un-ticked in the FTP Server options page.

Lines from filezilla connection log showing passive mode:
(000629)11/18/2015 17:59:22 PM - (not logged in) (173.26.228.2)> Connected on port 21, sending welcome message...
(000629)11/18/2015 17:59:22 PM - (not logged in) (173.26.228.2)> 220-FileZilla Server 0.9.53 beta
(000629)11/18/2015 17:59:22 PM - (not logged in) (173.26.228.2)> 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
(000629)11/18/2015 17:59:22 PM - (not logged in) (173.26.228.2)> 220 Please visit https://filezilla-project.org/
(000629)11/18/2015 17:59:22 PM - (not logged in) (173.26.228.2)> USER main
(000629)11/18/2015 17:59:22 PM - (not logged in) (173.26.228.2)> 331 Password required for main
(000629)11/18/2015 17:59:22 PM - (not logged in) (173.26.228.2)> PASS ***********
(000629)11/18/2015 17:59:22 PM - main (173.26.228.2)> 230 Logged on
(000629)11/18/2015 17:59:22 PM - main (173.26.228.2)> PWD
(000629)11/18/2015 17:59:22 PM - main (173.26.228.2)> 257 "/" is current directory.
(000629)11/18/2015 17:59:22 PM - main (173.26.228.2)> CWD /
(000629)11/18/2015 17:59:22 PM - main (173.26.228.2)> 250 CWD successful. "/" is current directory.
(000629)11/18/2015 17:59:22 PM - main (173.26.228.2)> EPSV
(000629)11/18/2015 17:59:22 PM - main (173.26.228.2)> 229 Entering Extended Passive Mode (|||60064|)

I apologize if this post seems a little all over the place, it's been a long day and now I'm racking my brain trying to figure this out.

Thanks in advance.

cjens19:
In case others are having a similar issue, I downgraded my firmware to 1.02 and viola, the sending of motion-detected images to my FTP server works like a charm. At some point I may try upgrading back to 1.11 but for now it's working so I'm just going to leave it.

Cheers!

cjens19:
Well I upgraded back to 1.11 firmware, and now sending to FTP server is broke again. I changed no settings at all, but when I hit Test button in FTP server setup page, it gives me a "test error" message. Pretty sure now that the 1.11 firmware is bugged in regards to FTP.

The 1.02 firmware worked for a while, but sometime last night, it stopped sending motion jpgs and instead was only sending event logs that motion was detected. So, it appears that this model of camera is just plain not good at sending motion-detected images to an FTP server. Such a shame, my 2 other, cheaper D-Links have had zero problems. They even auto-create a new date-stamped folder every day, whereas the 5029L was not, it was just throwing the images all into the same root folder.

Does anyone from D-Link ever read these forums? Just wondering.

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?

Be to enable uPnP and uPnP Port Forwarding ON ALL cameras. I recommend setting up static IP addresses ON each camera thats outside of the main host routers DHCP default IP address pool, i,e, 192.168.#.92 and .93 for the 932Ls and 192.168.#.29 for the 5029L.

cjens19:
Thanks for the response, Furry.

I'm located in the US region.
My router is a TP-Link Archer CR700
I am using Wireless N with a WPA2-PSK
Distance between camera and router is perhaps 25', no obstruction or walls.
I've already set up static IPs for all 3 of my cameras that fall outside the DHCP scope.
UPnP presentation was already ticked, but UPnP port forwarding is not. Would you be so kind to describe what I need to enable for port forwarding?

Navigation

[0] Message Index

[#] Next page

Go to full version