Our Products:   CompleteFTP  edtFTPnet/Free  edtFTPnet/PRO  edtFTPj/Free  edtFTPj/PRO
0 votes
13.3k views
in .NET FTP by
Hello.

I'm using function FTP.DirDetails(dir) to receive the list of files from remote host. This works perfect, but I saw that the date "LastModified" is incorrect!
If the real date of the last file modification is "28.10.2004 11:00", that edtftpnet returns the date "28.10.2005 11:00"! It's changing only the Year!

How to fix this problem?

Thanx. And sorry for my bad English.

18 Answers

0 votes
by (158k points)
Can you log into the FTP server via the command line FTP, do a "dir" and post the listing?

Hello.

I'm using function FTP.DirDetails(dir) to receive the list of files from remote host. This works perfect, but I saw that the date "LastModified" is incorrect!
If the real date of the last file modification is "28.10.2004 11:00", that edtftpnet returns the date "28.10.2005 11:00"! It's changing only the Year!

How to fix this problem?

Thanx. And sorry for my bad English.
0 votes
by
Can you log into the FTP server via the command line FTP, do a "dir" and post the listing?

This is very strange for me!
From the one FTP server edtftpnet shows incorrect data, but from the another FTP gives fully correct files list :shock:

FTP-1 (incorrect Year value)
edtftpnet gives me the list:
template.shtml      5374       10.12.2005 20:35:00
test.html      4937       27.01.2005 19:11:00
test.shtml      16620       10.12.2005 20:35:00
test.txt      4960       25.10.2005 14:00:00
top.inc      2691       25.10.2005 14:00:00
top_1.inc      1854       06.12.2005 12:39:00
top_2.inc      267       25.10.2005 14:00:00
top_index.inc      2420       25.10.2005 14:00:00
users               13       25.05.2004
videos.shtml      21518       05.03.2005 13:07:00

But Far FTP client shows me this picture:
[ img ]

FTP-2 (correct Year for all files)
edtftpnet gives me the list:
billiard.zip             184647               11.11.2002          <FILE>
makaki.jpg           785314               11.05.2004          <FILE>
index.html              45845               26.11.2005 12:29:00          <FILE>
fon.jpg                   51236               09.09.2002          <FILE>
photos                       512              31.03.2004          <FOLDER>
billiard_800.gif     128468               01.11.2002          <FILE>
billiard_big.gif        17573               05.11.2002          <FILE>
shareware            512              20.05.2003          <FOLDER>
billiard.files           4096              01.11.2002          <FOLDER>
index_.html            1780               09.09.2002          <FILE>
billiard_small.gif     12626               05.11.2002          <FILE>
ozonsoftware              512              28.05.2003          <FOLDER>
flower.jpg            1576863               11.05.2004          <FILE>
IMG_0154.JPG            826115               11.05.2004          <FILE>
luzh.jpg                   16913               02.06.2004          <FILE>
test.html                  4941               01.02.2005 11:10:00          <FILE>
test.txt                    9               01.02.2005 13:35:00          <FILE>

And the picture from the Far FTP client:
[ img ]

What's the problem?
0 votes
by (158k points)
Can you log in via command line FTP, and do 'dir' and post the output. We need to have this listing to figure out the problem
0 votes
by
Can you log in via command line FTP, and do 'dir' and post the output. We need to have this listing to figure out the problem

My FTP connections requires Passive Mode.
Sorry, but I don't know how to enable passive mode for ftp connection by command line. That is why I can't execute 'dir' command and getting the file listing.
0 votes
by (158k points)
Ok, use edtFTPj's dir() command to get a listing instead in passive mode. It returns an array of strings.

Can you log in via command line FTP, and do 'dir' and post the output. We need to have this listing to figure out the problem

My FTP connections requires Passive Mode.
Sorry, but I don't know how to enable passive mode for ftp connection by command line. That is why I can't execute 'dir' command and getting the file listing.
0 votes
by
Hi there...

Does anybody have a solution for that problem?

It happens only when ftp server runs on linux. On Windows all works fine.

Kind regards,
rjb
0 votes
by (158k points)
If you can give us a directory listing from the linux FTP server we'll take a look

Hi there...

Does anybody have a solution for that problem?

It happens only when ftp server runs on linux. On Windows all works fine.

Kind regards,
rjb
0 votes
by
Hi again...


Here is a file as it seen by a WC ftp client on a linux ftp server and after download:
[ img ]

Here is the same linux server, but from edtftp:
[ img ]

...and edtftp from a windows ftp server:
[ img ]

regards,
rjb
0 votes
by (158k points)
I probably wasn't clear. To test this, we need a text listing of the directory.

You can get this by loggin in with ordinary FTP command line and typing "dir" in the directory.

Cut 'n paste that into notepad or vi and save as a text file, and post it here.
0 votes
by
Here is go:


ftp> dir
200 PORT command successful
150 Opening ASCII mode data connection for file list
-rwxr-x--- 1 root root 1622481 May 14 22:14 radacct-log.log
-rwxr-xr-x 1 root root 68654 May 13 23:55 radacct-log.log.1.gz
-rwxr-xr-x 1 root root 77722 May 4 23:59 radacct-log.log.10.gz
-rwxr-xr-x 1 root root 39510 Feb 4 00:00 radacct-log.log.100.gz
-rwxr-xr-x 1 root root 37764 Feb 2 23:59 radacct-log.log.101.gz
-rwxr-xr-x 1 root root 39263 Feb 1 23:57 radacct-log.log.102.gz
-rwxr-xr-x 1 root root 40126 Jan 31 23:58 radacct-log.log.103.gz
-rwxr-xr-x 1 root root 35896 Jan 31 00:00 radacct-log.log.104.gz
-rwxr-xr-x 1 root root 34802 Jan 29 23:59 radacct-log.log.105.gz
-rwxr-xr-x 1 root root 36014 Jan 28 23:52 radacct-log.log.106.gz
-rwxr-xr-x 1 root root 36947 Jan 27 23:53 radacct-log.log.107.gz
-rwxr-xr-x 1 root root 37725 Jan 26 23:55 radacct-log.log.108.gz
-rwxr-xr-x 1 root root 36922 Jan 25 23:56 radacct-log.log.109.gz
-rwxr-xr-x 1 root root 75701 May 3 23:57 radacct-log.log.11.gz
-rwxr-xr-x 1 root root 33564 Jan 24 23:59 radacct-log.log.110.gz
-rwxr-xr-x 1 root root 34282 Jan 23 23:58 radacct-log.log.111.gz
-rwxr-xr-x 1 root root 29215 Jan 22 23:59 radacct-log.log.112.gz
-rwxr-xr-x 1 root root 33051 Jan 21 23:59 radacct-log.log.113.gz
-rwxr-xr-x 1 root root 31921 Jan 20 23:58 radacct-log.log.114.gz
-rwxr-xr-x 1 root root 25496 Jan 19 23:56 radacct-log.log.115.gz
-rwxr-xr-x 1 root root 25625 Jan 18 23:57 radacct-log.log.116.gz
-rwxr-xr-x 1 root root 21531 Jan 17 23:57 radacct-log.log.117.gz
-rwxr-xr-x 1 root root 19530 Jan 16 23:58 radacct-log.log.118.gz
-rwxr-xr-x 1 root root 19642 Jan 15 23:59 radacct-log.log.119.gz
-rwxr-xr-x 1 root root 73967 May 2 23:58 radacct-log.log.12.gz
-rwxr-xr-x 1 root root 20627 Jan 14 23:51 radacct-log.log.120.gz
-rwxr-xr-x 1 root root 21107 Jan 13 23:56 radacct-log.log.121.gz
-rwxr-xr-x 1 root root 18336 Jan 12 23:53 radacct-log.log.122.gz
-rwxr-xr-x 1 root root 21440 Jan 11 23:55 radacct-log.log.123.gz
-rwxr-xr-x 1 root root 21903 Jan 10 23:56 radacct-log.log.124.gz
-rwxr-xr-x 1 root root 20954 Jan 9 23:57 radacct-log.log.125.gz
-rwxr-xr-x 1 root root 20380 Jan 8 23:58 radacct-log.log.126.gz
-rwxr-xr-x 1 root root 17490 Jan 7 23:59 radacct-log.log.127.gz
-rwxr-xr-x 1 root root 16876 Jan 6 23:59 radacct-log.log.128.gz
-rwxr-xr-x 1 root root 19744 Jan 5 23:56 radacct-log.log.129.gz
-rwxr-xr-x 1 root root 70827 May 1 23:59 radacct-log.log.13.gz
-rwxr-xr-x 1 root root 17781 Jan 4 23:58 radacct-log.log.130.gz
-rwxr-xr-x 1 root root 16486 Jan 3 23:59 radacct-log.log.131.gz
-rwxr-xr-x 1 root root 18519 Jan 2 23:58 radacct-log.log.132.gz
-rwxr-xr-x 1 root root 19989 Jan 1 23:59 radacct-log.log.133.gz
-rwxr-xr-x 1 root root 18105 Dec 31 23:51 radacct-log.log.134.gz
-rwxr-xr-x 1 root root 20890 Dec 30 23:52 radacct-log.log.135.gz
-rwxr-xr-x 1 root root 20387 Dec 29 23:54 radacct-log.log.136.gz
-rwxr-xr-x 1 root root 19780 Dec 28 23:55 radacct-log.log.137.gz
-rwxr-xr-x 1 root root 16960 Dec 27 23:56 radacct-log.log.138.gz
-rwxr-xr-x 1 root root 18105 Dec 26 23:57 radacct-log.log.139.gz
-rwxr-xr-x 1 root root 72236 Apr 30 23:57 radacct-log.log.14.gz
-rwxr-xr-x 1 root root 17889 Dec 25 23:58 radacct-log.log.140.gz
-rwxr-xr-x 1 root root 18071 Dec 24 23:59 radacct-log.log.141.gz
-rwxr-xr-x 1 root root 20786 Dec 23 23:59 radacct-log.log.142.gz
-rwxr-xr-x 1 root root 17730 Dec 22 23:57 radacct-log.log.143.gz
-rwxr-xr-x 1 root root 17332 Dec 21 23:58 radacct-log.log.144.gz
-rwxr-xr-x 1 root root 13227 Dec 20 23:57 radacct-log.log.145.gz
-rwxr-xr-x 1 root root 10811 Dec 19 23:49 radacct-log.log.146.gz
-rwxr-xr-x 1 root root 12258 Dec 18 23:50 radacct-log.log.147.gz
-rwxr-xr-x 1 root root 12773 Dec 17 23:51 radacct-log.log.148.gz
-rwxr-xr-x 1 root root 15039 Dec 16 23:52 radacct-log.log.149.gz
-rwxr-xr-x 1 root root 75363 Apr 29 23:58 radacct-log.log.15.gz
-rwxr-xr-x 1 root root 16928 Dec 15 23:54 radacct-log.log.150.gz
-rwxr-xr-x 1 root root 71164 Apr 28 23:59 radacct-log.log.16.gz
-rwxr-xr-x 1 root root 71826 Apr 27 23:54 radacct-log.log.17.gz
-rwxr-xr-x 1 root root 69070 Apr 26 23:55 radacct-log.log.18.gz
-rwxr-xr-x 1 root root 70499 Apr 25 23:56 radacct-log.log.19.gz
-rwxr-xr-x 1 root root 70181 May 12 23:56 radacct-log.log.2.gz
-rwxr-xr-x 1 root root 70178 Apr 24 23:58 radacct-log.log.20.gz
-rwxr-xr-x 1 root root 68962 Apr 23 23:59 radacct-log.log.21.gz
-rwxr-xr-x 1 root root 73134 Apr 22 23:59 radacct-log.log.22.gz
-rwxr-xr-x 1 root root 75211 Apr 21 23:59 radacct-log.log.23.gz
-rwxr-xr-x 1 root root 70540 Apr 20 23:59 radacct-log.log.24.gz
-rwxr-xr-x 1 root root 69211 Apr 19 23:57 radacct-log.log.25.gz
-rwxr-xr-x 1 root root 68683 Apr 18 23:58 radacct-log.log.26.gz
-rwxr-xr-x 1 root root 67882 Apr 17 23:59 radacct-log.log.27.gz
-rwxr-xr-x 1 root root 67124 Apr 16 23:57 radacct-log.log.28.gz
-rwxr-xr-x 1 root root 68392 Apr 15 23:58 radacct-log.log.29.gz
-rwxr-xr-x 1 root root 67941 May 11 23:57 radacct-log.log.3.gz
-rwxr-xr-x 1 root root 67346 Apr 14 23:53 radacct-log.log.30.gz
-rwxr-xr-x 1 root root 64564 Apr 13 23:54 radacct-log.log.31.gz
-rwxr-xr-x 1 root root 62315 Apr 12 23:55 radacct-log.log.32.gz
-rwxr-xr-x 1 root root 63002 Apr 11 23:57 radacct-log.log.33.gz
-rwxr-xr-x 1 root root 59687 Apr 10 23:58 radacct-log.log.34.gz
-rwxr-xr-x 1 root root 60047 Apr 9 23:59 radacct-log.log.35.gz
-rwxr-xr-x 1 root root 60452 Apr 8 23:59 radacct-log.log.36.gz
-rwxr-xr-x 1 root root 70242 Apr 7 23:54 radacct-log.log.37.gz
-rwxr-xr-x 1 root root 68315 Apr 6 23:55 radacct-log.log.38.gz
-rwxr-xr-x 1 root root 65632 Apr 5 23:54 radacct-log.log.39.gz
-rwxr-xr-x 1 root root 62012 May 10 23:58 radacct-log.log.4.gz
-rwxr-xr-x 1 root root 66168 Apr 4 23:57 radacct-log.log.40.gz
-rwxr-xr-x 1 root root 66821 Apr 3 23:56 radacct-log.log.41.gz
-rwxr-xr-x 1 root root 68291 Apr 2 23:59 radacct-log.log.42.gz
-rwxr-xr-x 1 root root 68309 Apr 1 23:58 radacct-log.log.43.gz
-rwxr-xr-x 1 root root 68529 Mar 31 23:59 radacct-log.log.44.gz
-rwxr-xr-x 1 root root 64143 Mar 31 00:00 radacct-log.log.45.gz
-rwxr-xr-x 1 root root 60684 Mar 29 23:56 radacct-log.log.46.gz
-rwxr-xr-x 1 root root 60597 Mar 28 23:57 radacct-log.log.47.gz
-rwxr-xr-x 1

Categories

...