<x-flowed> We are having issue with uploading files with the white spaces - from Windows env (clients) through UNIX proxy to Windows (destination) Does anybody experience problem with ftpproxy and File/Folder Name Conventions? I'm sure we are not the only one who are using the Windows/UNIX environment and having problem with the white spaces.
Issues: 1.) We can't tell clients to change the file name convention. They have to continue to transfer files with white spaces in the file name. 2.) When I tried double quotes (a temporary solution) to upload "ntpdate Magda.log" the file name was truncated to "ntpdate" even if the output that the remote name is "ntpdate Magda.log" Any help /explanation on this? Why the file name shows up truncated up to the first white space? ftp> put "ntpdate Magda.log" local: ntpdate Magda.log remote: ntpdate Magda.log -rwxrwxrwx 1 owner group 85 Mar 11 11:55 ntpdate Examples of file which can't be send thorough ftpproxy: -rwxrwxrwx 1 owner group 1261031 Nov 5 2003 E-Book - JRR Tolkien - History Of Middle-Earth.zip -rwxrwxrwx 1 owner group 3272070 Jan 6 9:24 Frank Sinatra - Come Fly With Me.mp3 -rwxrwxrwx 1 owner group 3363620 Jan 6 9:26 Frank Sinatra - I've Got You Under My Skin.mp3 drwxrwxrwx 1 owner group 0 Mar 11 10:45 new folder spaces Regards, Magda _________________________________________________________________ Get a FREE online computer virus scan from McAfee when you click here. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 --general-l------------------------------------ To unsubscribe please visit: http://www.ftpproxy.org/html/maillinglists.html </x-flowed> From [EMAIL PROTECTED] Mon Mar 22 10:35:21 2004 Return-Path: <[EMAIL PROTECTED]> Received: from mail.compucation.de (mail.compucation.de [213.185.64.44]) by um1.pce.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id i2BJHDw13697 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for <[EMAIL PROTECTED]>; Thu, 11 Mar 2004 20:17:13 +0100 Received: from hotmail.com (bay15-f60.bay15.hotmail.com [65.54.185.60]) by compucation.de (mail.compucation.de [213.185.64.44]) (MDaemon.PRO.v7.0.0.R) with ESMTP id md50000000693.msg for <[EMAIL PROTECTED]>; Thu, 11 Mar 2004 20:16:27 +0100 X-Originating-IP: [205.189.242.104] X-Originating-Email: [EMAIL PROTECTED] X-Sender: [EMAIL PROTECTED] From: "Magdalena Hewryk" <[EMAIL PROTECTED]> To: "general-l List Member" <[EMAIL PROTECTED]> Subject: [general-l] The white spaces in a file name {01} Date: Thu, 11 Mar 2004 19:15:26 +0000 Mime-Version: 1.0 Message-ID: <[EMAIL PROTECTED]> X-OriginalArrivalTime: 11 Mar 2004 19:15:26.0835 (UTC) FILETIME=[35E00430:01C4079D] X-Lookup-Warning: MAIL lookup on [EMAIL PROTECTED] does not match 65.54.185.60 X-MDRemoteIP: 65.54.185.60 Sender: [EMAIL PROTECTED] X-Return-Path: [EMAIL PROTECTED] Precedence: bulk List-Unsubscribe: <mailto:[EMAIL PROTECTED]> X-MDMailing-List: [EMAIL PROTECTED] X-MDSend-Notifications-To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] X-MDAV-Processed: mail.compucation.de, Thu, 11 Mar 2004 20:16:31 +0100 X-UIDL: hP"#!5I^"!k)>"!ITf"! Status: O X-Status: X-Keywords: X-UID: 844 X-Eudora2Unix: 3905-11-05T08:39:36Z converted <x-flowed> Hi, We have a production issue with files transferred from NT thorough ftpproxy (on Unix/RH) to Windows NT. Some clients are using the white spaces in the filename when sending files and unfortunately the name of the file is cut off. For example a file Electronic Banking_DRFAFT_2.0 will end up in the destination as Electronic A file name Frank Sinatra - Come Fly With Magda become a Frank file name. How can I overcome this problem? The end user is using CuteFtp on Windows, ftpproxy is a RH Fedora/RH9 and the destination is Windows NT. Mar 11 14:06:24 proxy02 ftp.proxy[26484]: STOR /magda/test1_test2_test3_test4_test5_test6_test7-test8/Electronic: 342528 bytes ============================================================ We are having issue with uploading files with the white spaces - from Windows env (clients) through UNIX proxy to Windows (destination) Does anybody experience problem with ftpproxy and File/Folder Name Conventions? I'm sure we are not the only one who are using the Windows/UNIX environment and having problem with the white spaces. Issues: 1.) We can't tell clients to change the file name convention. They have to continue to transfer files with white spaces in the file name. 2.) When I tried double quotes (a temporary solution) to upload "ntpdate Magda.log" the file name was truncated to "ntpdate" even if the output that the remote name is "ntpdate Magda.log" Any help /explanation on this? Why the file name shows up truncated up to the first white space? ftp> put "ntpdate Magda.log" local: ntpdate Magda.log remote: ntpdate Magda.log -rwxrwxrwx 1 owner group 85 Mar 11 11:55 ntpdate Examples of file which can't be send thorough ftpproxy: -rwxrwxrwx 1 owner group 1261031 Nov 5 2003 E-Book - JRR Tolkien - History Of Middle-Earth.zip -rwxrwxrwx 1 owner group 3272070 Jan 6 9:24 Frank Sinatra - Come Fly With Me.mp3 -rwxrwxrwx 1 owner group 3363620 Jan 6 9:26 Frank Sinatra - I've Got You Under My Skin.mp3 drwxrwxrwx 1 owner group 0 Mar 11 10:45 new folder spaces Regards, Magda _________________________________________________________________ Add photos to your messages with MSN Premium. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines --general-l------------------------------------ To unsubscribe please visit: http://www.ftpproxy.org/html/maillinglists.html </x-flowed> From [EMAIL PROTECTED] Mon Mar 22 10:35:21 2004 Return-Path: <[EMAIL PROTECTED]> Received: from mail.compucation.de (mail.compucation.de [213.185.64.44]) by um1.pce.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id i2BJaiw14086 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for <[EMAIL PROTECTED]>; Thu, 11 Mar 2004 20:36:45 +0100 Received: from um1b.pce.de (um1b.pce.de [213.185.64.7]) by compucation.de (mail.compucation.de [213.185.64.44]) (MDaemon.PRO.v7.0.0.R) with ESMTP id md50000000698.msg for <[EMAIL PROTECTED]>; Thu, 11 Mar 2004 20:36:18 +0100 Message-ID: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Thu, 11 Mar 2004 20:34:01 +0100 To: "general-l List Member" <[EMAIL PROTECTED]> From: Wolfgang Zekoll <[EMAIL PROTECTED]> Subject: [general-l] The white spaces in a file name {02} In-Reply-To: <[EMAIL PROTECTED] e> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 X-Lookup-Warning: MAIL lookup on [EMAIL PROTECTED] does not match 213.185.64.7 X-MDRemoteIP: 213.185.64.7 Sender: [EMAIL PROTECTED] X-Return-Path: [EMAIL PROTECTED] Precedence: bulk List-Unsubscribe: <mailto:[EMAIL PROTECTED]> X-MDMailing-List: [EMAIL PROTECTED] X-MDSend-Notifications-To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] X-MDAV-Processed: mail.compucation.de, Thu, 11 Mar 2004 20:36:21 +0100 X-UIDL: @VM!![]##!hT3"!e]<"! Status: O X-Status: X-Keywords: X-UID: 848 X-Eudora2Unix: 3905-11-05T08:39:36Z converted <x-flowed> Hello Magda, >We have a production issue with files transferred from NT thorough ftpproxy >(on Unix/RH) to Windows NT. >Some clients are using the white spaces in the filename when sending files >and unfortunately the name of the file is cut off. what you describe here is what I call a "protection feature". So first of all, disallowing blanks in filename is a feature of ftp.proxy. Why? If users which don't know or don't care upload filenames with blanks onto a UNIX machine it is more than likely that these files smash the UNIX admin's maintaince scripts because blanks in filenames are very unusual under UNIX. On the other hand it's clear that today's users either don't know or don't care since they are used to it from their Windows boxes. Having said this, the solution to your problem is to give ftp.proxy the `-b' command line option to make ftp.proxy not to care about blanks in filenames. But before doing so you should first talk to your local UNIX administrator, discussing blanks in filenames on his harddisks. Now that I think about it, ftp.proxy could most probably implement an optional "filename rewrite" function which would %-encode all unusual characters in the filename. This would result in different real filenames on the Windows client and UNIX server but since there's is an automatic translation for FTP the client would never notice. Regards Wolfgang Zekoll --general-l------------------------------------ To unsubscribe please visit: http://www.ftpproxy.org/html/maillinglists.html </x-flowed> From [EMAIL PROTECTED] Tue Apr 20 09:06:04 2004 Return-Path: <[EMAIL PROTECTED]> Received: from mail.compucation.de (mail.compucation.de [213.185.64.44]) by um1.pce.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id i3JJdpa29078 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for <[EMAIL PROTECTED]>; Mon, 19 Apr 2004 21:39:51 +0200 Received: from hotmail.com (bay15-f37.bay15.hotmail.com [65.54.185.37]) by compucation.de (mail.compucation.de [213.185.64.44]) (MDaemon.PRO.v7.0.1.R) with ESMTP id md50000004778.msg for <[EMAIL PROTECTED]>; Mon, 19 Apr 2004 21:38:48 +0200 X-Originating-IP: [205.189.242.159] X-Originating-Email: [EMAIL PROTECTED] X-Sender: [EMAIL PROTECTED] From: "Magdalena Hewryk" <[EMAIL PROTECTED]> To: "general-l List Member" <[EMAIL PROTECTED]> Subject: [general-l] ftpproxy and data session on port 20 times out {01} Date: Mon, 19 Apr 2004 19:38:40 +0000 Mime-Version: 1.0 Message-ID: <[EMAIL PROTECTED]> X-OriginalArrivalTime: 19 Apr 2004 19:38:40.0330 (UTC) FILETIME=[EA92BAA0:01C42645] X-Lookup-Warning: MAIL lookup on [EMAIL PROTECTED] does not match 65.54.185.37 X-MDRemoteIP: 65.54.185.37 Sender: [EMAIL PROTECTED] X-Return-Path: [EMAIL PROTECTED] Precedence: bulk List-Unsubscribe: <mailto:[EMAIL PROTECTED]> X-MDMailing-List: [EMAIL PROTECTED] X-MDSend-Notifications-To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] X-MDAV-Processed: mail.compucation.de, Mon, 19 Apr 2004 21:38:51 +0200 X-UIDL: &fJ"!T1:"!<A;!!m&N!! X-Eudora2Unix: 3905-11-05T08:39:36Z converted <x-flowed> Hi, Is the pftpproxy using different ports (not TCP 20) for data session? I run netstat and I can see two port 21 and 22 open for ftp connection and data session but I want to make sure for network group asks the questions cp 0 0 172.16.1.40:51064 10.249.31.8:20 ESTABLISHED tcp 0 0 172.16.1.40:51071 10.249.31.8:20 ESTABLISHED tcp 68 0 172.16.1.40:51063 10.249.31.8:21 ESTABLISHED tcp 71 0 172.16.1.40:51070 10.249.31.8:21 ESTABLISHED We have a client who tries ftp through the ftpproxy to the server, is authenticated correctly but when the client tries to transmit data the 0 byts of the transferred file name is created. Basically an empty file is created. If we do the test all looks OK. I suspect the client must have some rules on firewalls which prevents the session from starting on port 20. However they were always able to ftp data to the FTP Server, when asked to go through ftpproxy they fail. Other seventy clients are OK. Any thoughts? Regards, Magda . _________________________________________________________________ Add photos to your messages with MSN Premium. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines --general-l------------------------------------ To unsubscribe please visit: http://www.ftpproxy.org/html/maillinglists.html </x-flowed> From [EMAIL PROTECTED] Fri Apr 23 10:27:56 2004 Return-Path: <[EMAIL PROTECTED]> Received: from mail.compucation.de (mail.compucation.de [213.185.64.44]) by um1.pce.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id i3ML27a04522 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for <[EMAIL PROTECTED]>; Thu, 22 Apr 2004 23:02:07 +0200 Received: from um1b.pce.de (um1b.pce.de [213.185.64.7]) by compucation.de (mail.compucation.de [213.185.64.44]) (MDaemon.PRO.v7.0.1.R) with ESMTP id md50000005248.msg for <[EMAIL PROTECTED]>; Thu, 22 Apr 2004 23:02:05 +0200 Message-ID: <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Thu, 22 Apr 2004 23:00:22 +0200 To: "general-l List Member" <[EMAIL PROTECTED]> From: Wolfgang Zekoll <[EMAIL PROTECTED]> Subject: [general-l] ftpproxy and data session on port 20 times out {02} In-Reply-To: <[EMAIL PROTECTED] e> References: <[EMAIL PROTECTED]> Mime-Version: 1.0 X-Lookup-Warning: MAIL lookup on [EMAIL PROTECTED] does not match 213.185.64.7 X-MDRemoteIP: 213.185.64.7 Sender: [EMAIL PROTECTED] X-Return-Path: [EMAIL PROTECTED] Precedence: bulk List-Unsubscribe: <mailto:[EMAIL PROTECTED]> X-MDMailing-List: [EMAIL PROTECTED] X-MDSend-Notifications-To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] X-MDAV-Processed: mail.compucation.de, Thu, 22 Apr 2004 23:02:09 +0200 X-UIDL: I5]!!IOZ!!":k!!,7>!! X-Eudora2Unix: 3905-11-05T08:39:36Z converted <x-flowed> Hello Magda, >Hi, > >Is the pftpproxy using different ports (not TCP 20) for data session? yes, at least by default. You can however configure it to use port 20 but this requires also that the proxy runs as `root' - not recommended. >I run netstat and I can see two port 21 and 22 open for ftp connection and >data session but I want to make sure for network group asks the questions > >cp 0 0 172.16.1.40:51064 10.249.31.8:20 >ESTABLISHED >tcp 0 0 172.16.1.40:51071 10.249.31.8:20 >ESTABLISHED >tcp 68 0 172.16.1.40:51063 10.249.31.8:21 >ESTABLISHED >tcp 71 0 172.16.1.40:51070 10.249.31.8:21 >ESTABLISHED What is what? Or in other words: is 172.16.1.40 an FTP client or ftp.proxy and what about 10.249.31.8, proxy or server? >We have a client who tries ftp through the ftpproxy to the server, is >authenticated correctly but when the client tries to transmit data the 0 >byts of the transferred file name is created. Basically an empty file is >created. If we do the test all looks OK. > >I suspect the client must have some rules on firewalls which prevents the >session from starting on port 20. However they were always able to ftp data >to the FTP Server, when asked to go through ftpproxy they fail. Other >seventy clients are OK. Using port 20 as data source port is pretty uncommon these days. So I don't think this is the problem. Do you have some error messages in the proxy's syslog? And another question, would it be possible to run the ftp.proxy in debug mode with the broken client? I think this would help really much. Regards Wolfgang Zekoll --general-l------------------------------------ To unsubscribe please visit: http://www.ftpproxy.org/html/maillinglists.html </x-flowed> From [EMAIL PROTECTED] Fri Jun 04 10:54:59 2004 Return-Path: <[EMAIL PROTECTED]> Received: from mail.compucation.de (mail.compucation.de [213.185.64.44]) by um1.pce.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id i547jea18689 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO) for <[EMAIL PROTECTED]>; Fri, 4 Jun 2004 09:45:40 +0200 Received: from smtp2.sycor.de (dns2.sycor-world.de [194.31.240.5]) by compucation.de (mail.compucation.de [213.185.64.44]) (Cipher TLSv1:RC4-MD5:128) (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000009926.msg for <[EMAIL PROTECTED]>; Fri, 04 Jun 2004 09:43:31 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:recallmessage MIME-Version: 1.0 Subject: [general-l] Rückruf: help {01} Date: Fri, 4 Jun 2004 09:43:22 +0200 Message-ID: <[EMAIL PROTECTED]> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: help Thread-Index: AcRKB5yxd5wnRZMqSdmq6qhXa1qPTg== Priority: Urgent Expiry-Date: Sun, 6 Jun 2004 09:43:19 +0200 From: "Albrecht Marcus" <[EMAIL PROTECTED]> To: "general-l List Member" <[EMAIL PROTECTED]> X-MDRemoteIP: 194.31.240.5 Sender: [EMAIL PROTECTED] X-Return-Path: [EMAIL PROTECTED] Precedence: bulk List-Unsubscribe: <mailto:[EMAIL PROTECTED]> X-MDMailing-List: [EMAIL PROTECTED] X-MDSend-Notifications-To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] X-MDAV-Processed: mail.compucation.de, Fri, 04 Jun 2004 09:44:28 +0200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by um1.pce.de id i547jea18689 X-UIDL: +`Y"!a<S"!J,H!!Z,H"! X-Eudora2Unix: 3905-11-05T08:39:36Z converted Albrecht Marcus möchte die Nachricht "help" zurückrufen. --general-l------------------------------------ To unsubscribe please visit: http://www.ftpproxy.org/html/maillinglists.html
