Archive-Date: Tue, 11 Oct 2005 12:18:29 -0400 Date: Tue, 11 Oct 2005 11:59:06 -0400 From: Richard Whalen Reply-To: Info-TCPware@process.com Subject: Re: TCPWare-TCP 5.6-2:FTP & Anonymous To: info-tcpware@process.com Message-ID: "Ruslan R. Laishev" wrote in message news:47C5F2A2C90633361807147B22D33BC5@nntp... > Hello All! > > I have tried to implement a different access for anonymous users with different > passwords: > > $ sho lo ftp_spool /full > "FTP_SPOOL" [exec] = "$1$DUA122:[FTP_SPOOL.]" [concealed,terminal] > (LNM$SYSTEM_TABLE) > $ > > > login.com: > > $ RUN TCPWARE:FTP_SERVER > $ PWD = F$TRNLNM("TCPWARE_FTP_ANONYMOUS_PASSWORD") > $ DEASSIGN TCPWARE_FTP_GET_REMOTE_INFO > $ > $ DEFINE TCPWARE_FTP_DISALLOW_UNIX_STYLE FALSE > $ DEFINE TCPWARE_FTP_UNIX_STYLE_BY_DEFAULT TRUE > $ > $ IF PWD.EQS."pwd1" > $ THEN > $ DEFINE TCPWARE_FTP_ANONYMOUS_ROOT FTP_SPOOL: > $ DEFINE TCPWARE_FTP_ANONYMOUS_RIGHTS "WRITE,RENAME,DELETE" > $ ENDIF > $ > $ IF PWD.EQS."pwd2" > $ THEN > $ DEFINE TCPWARE_FTP_ROOT DISK$LOGS:[FTP_SPOOL.] > $ ENDIF > > If a logins unders anonymous/pwd1 and try to LIST current directory I getting: > > $ ftp starlet > 220 DTV1.DeltaTel.RU (172.16.0.8) FTP-OpenVMS FTPD V5.6-2 (c) 2002 Process Software > _Username [laishev]: anonymous > 331 Send ident as password. > _Password: > 230 User logged in, proceed. > FTP> dir > 200 STRU command okay. > 200 PORT command okay. > 550 Request not permitted for user. > %TCPWARE_FTP-E-FILRCVERR, error receiving SYS$OUTPUT:.; from server > -TCPWARE-I-REPLY, server's reply was "550 Request not permitted for user." > FTP> > > > Is there what I'm need to check ? > > What's the protection on the directory that is FTP_SPOOL and what is the user UIC? ================================================================================ Archive-Date: Wed, 12 Oct 2005 09:34:44 -0400 Date: Wed, 12 Oct 2005 09:04:45 -0400 From: Richard Whalen Reply-To: Info-TCPware@process.com Subject: Re: TCPWare-TCP 5.6-2:FTP & Anonymous To: info-tcpware@process.com Message-ID: Focusing on the login.com that you included: "Ruslan R. Laishev" wrote in message news:B2FBE1E756C6E88E1F3E63FC837EB578@nntp... > Hello Richard! > >>login.com: > >> > >>$ RUN TCPWARE:FTP_SERVER At this point the FTP_SERVER will start processing commands unless the logical TCPWARE_FTP_GET_REMOTE_INFO is defined. If the logical is defined, then it will define the logicals TCPWARE_FTP_ADDRESS, TCPWARE_FTP_HOSTNAME and TCPWARE_FTP_LOCAL_ADDRESS and exit. So, the problem could be that the commands below this are not being executed until after the session has completed. Have you verified that the directory is what you expect it to be with PWD? > >>$ PWD = F$TRNLNM("TCPWARE_FTP_ANONYMOUS_PASSWORD") > >>$ DEASSIGN TCPWARE_FTP_GET_REMOTE_INFO > >>$ > >>$ DEFINE TCPWARE_FTP_DISALLOW_UNIX_STYLE FALSE > >>$ DEFINE TCPWARE_FTP_UNIX_STYLE_BY_DEFAULT TRUE > >>$ > >>$ IF PWD.EQS."pwd1" > >>$ THEN > >>$ DEFINE TCPWARE_FTP_ANONYMOUS_ROOT FTP_SPOOL: > >>$ DEFINE TCPWARE_FTP_ANONYMOUS_RIGHTS > > > > "WRITE,RENAME,DELETE" > > > >>$ ENDIF > >>$ > >>$ IF PWD.EQS."pwd2" > >>$ THEN > >>$ DEFINE TCPWARE_FTP_ROOT DISK$LOGS:[FTP_SPOOL.] > >>$ ENDIF > >> > >>If a logins unders anonymous/pwd1 and try to LIST current directory I > > > > ================================================================================ Archive-Date: Thu, 13 Oct 2005 09:48:30 -0400 Date: Thu, 13 Oct 2005 09:01:40 -0400 From: Richard Whalen Reply-To: Info-TCPware@process.com Subject: Re: TCPWare-TCP 5.6-2:FTP & Anonymous To: info-tcpware@process.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN Content-Transfer-Encoding: QUOTED-PRINTABLE Good to hear that you figured out your problem. I take it you looked= at TCPWARE:FTPSERVER_DTP.COM and discovered that it was doing a SET DEFAULT to the target directory before starting the FTP server. "Ruslan R. Laishev" wrote in message news:BDA020A9D7A67794F276D074F14E6BE3@nntp... > Hi , All! > > Resolve the probleb by adding set default to a target directory= =F6 > > $ IF PWD.EQS."SALE_AVI" > $ THEN > $ SET DEFAULT FTP_SPOOL:[000000] > $ DEFINE TCPWARE_FTP_ANONYMOUS_ROOT FTP_SPOOL: > $ DEFINE TCPWARE_FTP_ANONYMOUS_RIGHTS > "WRITE,RENAME,DELETE" > $ ENDIF > > > > > > Ruslan R. Laishev wrote: > > > Hello, Richard! > > > > I lost first lines of the login.com in the previous mail: > > $ > > $ DEFINE TCPWARE_FTP_GET_REMOTE_INFO " " > > $ RUN TCPWARE:FTP_SERVER > > $ PWD =3D F$TRNLNM("TCPWARE_FTP_ANONYMOUS_PASSWORD") > > $ DEASSIGN TCPWARE_FTP_GET_REMOTE_INFO > > $ > > $ DEFINE TCPWARE_FTP_DISALLOW_UNIX_STYLE FALSE > > $ DEFINE TCPWARE_FTP_UNIX_STYLE_BY_DEFAULT TRUE > > $ > > $ IF PWD.EQS."SALE_AVI" > > $ THEN > > $ DEFINE TCPWARE_FTP_ANONYMOUS_ROOT FTP_SPOOL= : > > $ DEFINE TCPWARE_FTP_ANONYMOUS_RIGHTS > > "WRITE,RENAME,DELETE" > > $ ENDIF > > $ > > $ IF PWD.EQS."SPOOL" > > $ THEN > > $ DEFINE TCPWARE_FTP_ROOT DISK$LOGS:[FTP_SP= OOL.] > > $ ENDIF > > $ > > > > Richard Whalen wrote: > > > >> Focusing on the login.com that you included: > >> > >> "Ruslan R. Laishev" > >> wrote in message news:B2FBE1E756C6E88E1F3E63FC837EB578@nntp... > >> > >>> Hello Richard! > >>> >>login.com: > >>> >> > >>> >>$ RUN TCPWARE:FTP_SERVER > >> > >> > >> > >> At this point the FTP_SERVER will start processing commands unle= ss the > >> logical > >> TCPWARE_FTP_GET_REMOTE_INFO is defined. If the logical is defin= ed, then > >> it will define the logicals TCPWARE_FTP_ADDRESS, TCPWARE_FTP_HOS= TNAME > >> and TCPWARE_FTP_LOCAL_ADDRESS and exit. > >> > >> So, the problem could be that the commands below this are not be= ing > >> executed > >> until > >> after the session has completed. Have you verified that the dir= ectory is > >> what you > >> expect it to be with PWD? > > > > > > > > > >> > >> > >> > >>> >>$ PWD =3D F$TRNLNM("TCPWARE_FTP_ANONYMOUS_PASSWORD") > >>> >>$ DEASSIGN TCPWARE_FTP_GET_REMOTE_INFO > >>> >>$ > >>> >>$ DEFINE TCPWARE_FTP_DISALLOW_UNIX_STYLE FALSE > >>> >>$ DEFINE TCPWARE_FTP_UNIX_STYLE_BY_DEFAULT TRUE > >>> >>$ > >>> >>$ IF PWD.EQS."pwd1" > >>> >>$ THEN > >>> >>$ DEFINE TCPWARE_FTP_ANONYMOUS_ROOT FTP_S= POOL: > >>> >>$ DEFINE TCPWARE_FTP_ANONYMOUS_RIGHTS > >>> > > >>> > "WRITE,RENAME,DELETE" > >>> > > >>> >>$ ENDIF > >>> >>$ > >>> >>$ IF PWD.EQS."pwd2" > >>> >>$ THEN > >>> >>$ DEFINE TCPWARE_FTP_ROOT DISK$LOGS:[FTP_SPOOL.] > >>> >>$ ENDIF > >>> >> > >>> >>If a logins unders anonymous/pwd1 and try to LIST current dir= ectory I > >>> > > >>> > > >> > >> > >> > >> > >> > > > > > > --=20 > + WBR, OpenVMS [Sys|Net] HardWorker ............. Skype: SysMan-One= + > Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator > Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-32= 22 > +http://starlet.deltatelecom.ru ............. Frying on OpenVMS onl= y + ================================================================================ Archive-Date: Fri, 28 Oct 2005 09:56:32 -0400 Date: Fri, 28 Oct 2005 09:56:19 -0400 From: bryant@PROCESS.COM Reply-To: Info-TCPware@process.com To: TCPware-Announce@PROCESS.COM Message-ID: <00A4BF2E.4EB42B1C.2@triton.process.com> Subject: TCPware ECO kit available: NFSDV3_V562P070 TCPware ECO kit announcement The following ECO kit is now available for TCPware: ECO: NFSDV3_V562P070 Description: Corrects a problem with corrupted file writes Release date: 28-OCT-2005 Ranking: 2 Max ranking: 2 Versions: 5.6-2 ftp://ftp.process.com/support/56_2/nfsdv3_v562p070.zip To search the TCPware ECO database, please visit the following URL: http://vms.process.com/eco.html For more information, contact Process Software via: E-mail: support@process.com Phone: 1-800-394-8700 The ECO kit README contents are below. ----------------------------------------------------------- ----------------------------------------------------------------------------- NFSD V3 Patch kit (rev. 7.0) for TCPware V5.6-2 28-Oct-2005 Copyright (c) 2005 by Process Software, LLC This ECO kit provides a new version of the following file for TCPWare 5.6-2: NFSDV3.EXE This VMS installable saveset corrects problems found in the TCPware for OpenVMS NFS Version 3 server. This patch supports TCPware V5.6-2 for OpenVMS VAX v5.5-2 through v7.3 and OpenVMS Alpha v6.2 through v7.3-2. This kit has an ECO ranking of 2 (Recommended; individual component may fail). The overall ECO rank of this kit is 2. (Recommended; individual component may fail) Included in this kit is a fix for the following D/E: o Corrects a problem with corrupted file writes. Write procedures with an offset in the starting block other than zero were being incorrectly calculated as zero. [D/E 10157] Changes made in rev 6.2: o Improved performance/response times of directory listings and lookups within very large directories. [D/E 9987] o Corrected problem with corrupted writes within newly created files. [D/E 9986] o Corrected ODS-5 to ODS-2 mapping scheme when using the TCPware NFS client. The leading '$' is no longer displayed when listing filenames. [D/E 9823] Changes made in rev 5.0: o D/E 9809: Corrected a problem with READDIRPLUS handling of dircount/maxcount args when verifying buffer size. This problem was resulting in an I/O error with Linux NFS clients. o D/E 9544: Added support for TCPWare ODS-2 NFS client to access ODS-5 exports Change made in rev 4.0: o D/E 9764: Fixed problem with V3 CREATE procedure, corrected handling of EXCLUSIVE type create functionality. Changes made in rev 3.0: o Added support for ODS-5 filesystem. o D/E 9541: Corrects a problem where parsing of ODS-2 directories could result in a hang. Changes made in rev 2.0: o D/E 9359: Cannot move a file from export after upgrade to V3 server. Fixed a problem with the new V3 procedure ACCESS. Changes made in rev 1.0: o Fixed problem with reading & writing to/from very large files (greater than 4 gigabytes) with variable record formats. Support for 64-bit data types added to attribute handling for variable type files. [D/E 8335] o Fixed problem with FSSTAT response (used by clients to show total disk space, etc). Was not supporting very large exports (greater than 4 gigabytes). [D/E 8335] o Fixed intermittent problem with READDIRPLUS handling of directory cache. After any QIO failures during a directory read (to build the directory cache) entries may have been corrupted. This NFSDV3 Version 3 server supports both NFS V2 and V3, and is designed to meet the specification as defined in RFC 1813. Please refer to RFC 1813 for detailed descriptions of the NFS V3 protocol. The existing NFS Server must be shut down before installation by issuing the command: @TCPWARE:SHUTNET NFS To activate the NFS V3 server, configure it by running "@TCPWARE:CNFNET NFS". Select the V3 server when prompted and complete the configuration. NFS V2 server variables set previously will be retained during the configuration. At the end of the configuration, answer "YES" to "Do you wish to restart the NFS-OpenVMS server?" If for any reason you wish to fall back to the V2 server, run "@TCPWARE:CNFNET NFS" and answer "NO" to the question: "Do you want the NFS V3 Server (NFSDV3) [YES]:". Select the V2 server at the next configuration prompt, and when the configuration is complete then answer "YES" to the "Do you wish to restart the NFS-OpenVMS server?" question. *********************************************************************** * PLEASE NOTE: The V2 server (NFSD.EXE) DOES NOT have ODS-5 support. * * Process Software recommends running the V3 NFS server. * *********************************************************************** [End of ECO announcement]