I presently run SuSE 9.1 with KDE 3.2.2.level "a" When I am having a problem with KBEAR (FTP) if I transfer a .jpg to the webserver they will not display. If I copy the jpg to Windows (yak) and use WSFTP they work. This just started happening recently. Checking the permissions show they are the same if I use kbear or WSftp. Only message I see in Kbear that I do not seein in WSFTP is kbear tries the following: 250 CWD command successful. type A 200 Type set to A. EPSV 500 EPSV not understood. PASV 227 Entering Passive Mode (216,40,195,82,11,76). list -a 150 Opening ASCII mode data connection for file list 226 Transfer complete. I do not see that EPSV message in WSftp it starts in passive mode. I use the icon to provide a link to another site. The file does transfer. If I put my cursor over the area where the jpg should be I can click I can link to the site. I tryed looking at the SuSE update site but it says I have the latest versions of KDE. Can anyone give me an idea what to look at. I will be tring a manual update from the console or Konqueror. The linux browser I've tryed are Konqueror and Mozilla. Both exhibit the same issue until I transfer the jpg with WSftp from Windows. -- Russ
Le Lundi 28 Février 2005 22:30, Russ a écrit :
I presently run SuSE 9.1 with KDE 3.2.2.level "a" When I am having a problem with KBEAR (FTP) Kbear is still a little bit buggy... Use Konqueror instead.
15 days ago I still didn"t know Konqueror was able to manage FTP. Now I use it every times for FTP transfers and it does the trick very well. You can even use FTP bookmarks and save the password of the FTP server in kwallet. Furthermore, you can use tabs between the FTP server and your local machine. The only feature missing is "synchronise folder", but it doesnt work in Kbear either Fred
On Mon, 2005-02-28 at 16:30, Russ wrote:
I presently run SuSE 9.1 with KDE 3.2.2.level "a" When I am having a problem with KBEAR (FTP) if I transfer a .jpg to the webserver they will not display. If I copy the jpg to Windows (yak) and use WSFTP they work. This just started happening recently. Checking the permissions show they are the same if I use kbear or WSftp. Only message I see in Kbear that I do not seein in WSFTP is kbear tries the following: 250 CWD command successful. type A 200 Type set to A. EPSV 500 EPSV not understood. PASV 227 Entering Passive Mode (216,40,195,82,11,76). list -a 150 Opening ASCII mode data connection for file list 226 Transfer complete.
It is setting itself to ascii mode instead of binary mode. At the prompt type bin then transfer the file and see if is correct. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Monday 28 Feb 2005 22:45 pm, Ken Schneider wrote:
On Mon, 2005-02-28 at 16:30, Russ wrote:
150 Opening ASCII mode data connection for file list
It is setting itself to ascii mode instead of binary mode. At the prompt type bin then transfer the file and see if is correct.
KBear will ask for directory listings in ASCII mode, but the setting for files is separate and defined on a per-site basis. Russ, check the setting for the site you're connecting to in the Advanced properties of the connection you're using in the Site Manager. It defaults to binary for file transfer, however, so that's unlikely to be the problem, I suppose. It's not something weird like case-sensitivity screwing up the links, is it? I only ask, because if it works going through Windows, it may be that Windows is translating the case of the filenames to something different -- and the web server is likely to be case-sensitive. Are the filenames _exactly_ the same when transferred via Windows and via KBear? Matt -- "It's the small gaps between the rain that count, and learning how to live amongst them." -- Jeff Noon
On Monday 28 February 2005 03:14 pm, Matt Gibson wrote:
On Monday 28 Feb 2005 22:45 pm, Ken Schneider wrote:
On Mon, 2005-02-28 at 16:30, Russ wrote:
150 Opening ASCII mode data connection for file list
It is setting itself to ascii mode instead of binary mode. At the prompt type bin then transfer the file and see if is correct.
KBear will ask for directory listings in ASCII mode, but the setting for files is separate and defined on a per-site basis.
Russ, check the setting for the site you're connecting to in the Advanced properties of the connection you're using in the Site Manager. It defaults to binary for file transfer, however, so that's unlikely to be the problem, I suppose.
It's not something weird like case-sensitivity screwing up the links, is it? I only ask, because if it works going through Windows, it may be that Windows is translating the case of the filenames to something different -- and the web server is likely to be case-sensitive. Are the filenames _exactly_ the same when transferred via Windows and via KBear?
Matt
-- "It's the small gaps between the rain that count, and learning how to live amongst them." -- Jeff Noon
No it not the case sensitive issue. I've checked that several times. Just rechecked it again case is correct. I noticed in the advanced setting I can disable the EPSV so I will try that. This was working until recently. Checking to see if host site made any changes. -- Russ
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/
participants (5)
-
Carl E. Hartung -
Fred -
Ken Schneider -
Matt Gibson -
Russ