ceglia - I am envious. I can't get ftp to do anything on the DCS-2330L. Has anyone else figured out what the ftp problem is?
I have a DCS-2132L that FTPs across a local network to a server, and it works fine.
This DCS-2330L is otherwise working fine. It is on the local network, it can be pinged, it is running in D-ViewCam. The onboard setup runs fine, along with the live view on the camera. I can send URL commands and acquire stills and video.
The DCS-2330L, however, doesn't even write any log entries while yielding the infamous "TEST ERROR" result when testing the ftp configuration on the camera. I have been through an assortment of configuration variations in an attempt to troubleshoot. The bottom line is that the DCS-2330L ftp routine is not doing anything. We can't debug a problem when the camera is choosing to not send any ftp commands whatsoever.
Yes, I have tried everything: a different ftp account on the client, and using the same ftp account as the DCS-2132L; firewall on and off; wireless vs. ethernet cable; server IP address vs name as suggested above. No difference. The camera log still does not record the ftp test event, meaning the camera did not try to connect, so of course the ftp client does not record any login attempts because none came in to the server. (An ftp test on the 2132L yields an ftp login/success line in the camera log, and a corresponding line in the ftp client log.) If there was a login attempt in the ftp client, then I could debate if there is a target file path string error. The ftp test does not even get that far, and besides, I am using the DCS-2132L ftp config as a template. In other words, I know the ftp configuration in the 2330L is correct, routers are fine, the server is ok, the ftp client is configured correctly, the firewall is not in the way. Everything suggests the 2330L has a firmware problem.
Here's the kicker. I bought the 2330L last week. It came with firmware version 1.01.06, and I am tempted to move it backwards to 1.00.04 - an undesireable route that is likely to cause heartburn.
All that said - is anyone else still having ftp trouble, or perhaps found a quirky way around the failure of 2330L ftp to work?
***** EDIT: Solved. *****
My fault.
Using FileZilla as ftp client. I forgot there for IP filters, there are global filters and user account filters. I had changed the user account IP filters, but not the global IP filters. Adding the 2330L to the global IP filters allowed the camera to access and write via FTP.
Then, adding or changing a target ftp directory in the camera's ftp configuration required an immediate camera reboot for the correct target ftp path to take effect. But this reboot requirement was not consistent. It seems that rebooting is the safe method each time.
In FileZilla, changing target (home) directories for ftp accounts, and changing IP filter entries, each required a pgm restart to take effect. (Ouch. Lost some time there.)
Without doing the above tasks, the camera would not do ftp writes, and there was no indication as to why.
That said, whether ftp writes are successful or not, the 2330L is not writing ftp events to the camera log. On both the 942Ls and 2132L, ftp actions are adding log entries - whether they are fails or successful - making debug easier.