Core FTP

That might be tough. The reason i switched to Core FTP was becausze the server implemented SSL/TLS and Wise FTP doesn't support that!

Let me see what I can figure out...

(By the way, I REALLY appreciate you sticking with me on this!)

I modified a file on my system so it had the timestamp of 6/3/04 8:27.

After uploading, Core FTP displayed the timestamp as 6/3/04 8:27.

After refreshing the file listing on the server the timestamp of the file was displayed as 6/3/04 13:26.

OK, Sorry, once again i reveal my stupidity!! Anyway, below is the log of transfering one file with "Do Not Use MDTM" option checked. =================================== Resolving upload.att.net... Connect socket #564 to 204.127.135.142, port 21... 220- 220-Welcome to the AT&T WorldNet...

Was this post meant for a different thread?

OK, next set of dumb questions!

How come Wise FTP worked?

I can't find any mention of the Log's location in the help file except where it says to look at it! Where is it? And what's it called?

Thanks!

I have read a couple of other messages here about file timestamps when uploading files, but I am still confused! When I used Micro$ofts Web Publishing Wizard, the files on my FTP server got the same date/time as my local files. This is also the case with Wise FTP, but when I use Core FTP Lite (V1.3 ...