On Monday 28 February 2005 16:30, Russ wrote: <snip> Hi Russ, The symptom you've described, i.e. the .jpg file uploading with the correct permissions to the correct location but not rendering in your browsers, resembles what happens to binary files that have been inadvertently transferred in ASCII mode, hence corrupted (actually mangled.) And there's something about the following sequence that is 'bugging' me. I can't put my finger on it, but I'll step through it with remarks and hopefully the list can expand on these thoughts:
250 CWD command successful.
OK, so it Changed the Working Directory. I'd expect that it accomplished this in ASCII mode. Then...
type A 200 Type set to A.
"Resets" to ASCII mode? Is it supposed to do this at each and every step while you're navigating the site or should it only be resetting the connection type when the client requests it?
EPSV 500 EPSV not understood.
The server doesn't support the IPv6 extension to passive mode. Not a problem... it should fall back:
PASV 227 Entering Passive Mode (216,40,195,82,11,76).
It does.
list -a
Requesting a complete directory listing...
150 Opening ASCII mode data connection for file list
"Resets" to ASCII mode again?
226 Transfer complete.
Directory listing transferred. Between this seemingly labored navigation and your .jpg file not rendering after being uploaded, my guess is KBear and the server are somehow now speaking different 'dialects' of 'ftp' and are having a hard time communicating with each other. This is probably resulting in your .jpg file being corrupted. As others have suggested, you can try Konqueror or another ftp client; Kftp and gftp come to mind. Good luck & regards, - Carl -- _______________________________________________________________________ C. E. Hartung Business Development & Support Services http://www.cehartung.com/ carlh@cehartung.com Dover Foxcroft, Maine, USA Public Keys 68396713 & F8207216 Reg. Linux User #350527 http://counter.li.org/