| Well, Paul, it looks like you're gonna be the first one to test
it...
Yeah, check note 4589 on the Amiga_Sys (UseNet) conference on FRSOLD::.
It should be all in there...
Or better yet, I'll include the posting here...
<CB>
<<< FRSOLD::IS$NOTES:[NOTES$LIBRARY]AMIGA_SYS.NOTE;2 >>>
-< comp.sys.amiga - postings >-
================================================================================
Note 4589.0 Can't FTP? This note's for you... No replies
FRSOLD::ZIMMERMANN "xanth.cs.odu.edu!tadguy" 209 lines 1-JAN-1990 05:34
--------------------------------------------------------------------------------
Path: shlump.nac.dec.com!decwrl!ucbvax!tut.cis.ohio-state.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!xanth!xanth.cs.odu.edu!tadguy
From: [email protected] (Tad Guy)
Newsgroups: comp.sys.amiga
Subject: Can't FTP? This note's for you...
Message-ID: <[email protected]>
Date: 31 Dec 89 20:49:38 GMT
Sender: [email protected]
Organization: Old Dominion University, Norfolk, VA
Lines: 199
I recently received this. Thought those of you who cannot FTP to
xanth.cs.odu.edu might find this useful (probably the last great
understatement of the year...) :-)
...tad
Over the past several months, each of you has sent a request to
Princeton's BITNET FTP server, BITFTP@PUCC. In each case, you
have received a reply indicating that BITFTP was unable to serve
you because you appeared to it to be sending your request from a
node that was not directly attached to BITNET (or EARN or NetNorth).
(The problem was that it was unable to send non-mail files through
the mail-only gateways out of BITNET.)
However, I have recently enhanced BITFTP to enable it to send files
through mail-only gateways from BITNET into other networks. If you
have not already found a better way to get to BITFTP, you might wish
to try using it again. I append below a current HELP file to give
you more information on using BITFTP.
Note that if in parsing your mail BITFTP decides that your node is
on the other side of a mail-only gateway, it will send the files
you request in UUENCODED format inside mail files. UUENCODED
files will go safely through most mail-only gateways, but are not
absolutely guaranteed to do so. (They may be corrupted by incorrect
EBCDIC-to-ASCII translation at some node between ours and yours.)
Thus, if your node really is attached directly to BITNET or EARN or
NETNORTH, you should send me mail stating that fact so that I can
correct BITFTP to understand that it can send your files via BITNET.
Melinda Varian,
Office of Computing and Information Technology,
Princeton University
BITFTP -- Princeton BITNET FTP Server
BITFTP provides a mail interface to the FTP portion
of the IBM TCP/IP product ("FAL") running on the
Princeton VM system, to allow BITNET/NetNorth/EARN users
to ftp files from sites on the Internet.
BITFTP currently accepts requests only via RFC822-format
mail, IBM NOTE-format mail, PROFS-format messages, or
files with no headers at all. BITFTP currently returns
the requested files as NETDATA-format files or as mail files
containing UUENCODED data. If you specify "UUENCODE" or
"NETDATA" on your "FTP" command, BITFTP will attempt to
use that format. If you do not specify the format, BITFTP
will attempt to select the appropriate format for your node.
BITFTP attempts to send NETDATA-format files through the gateway
from EARN into Janet via the NIFTP facility at Rutherford Lab.
If BITFTP sends you a file you cannot read, THE FIRST THING
TO DO is to make sure that you specified ASCII if the file
should contain textual material or that you specified BINARY
if the file should contain binary data, executable programs,
tar files, or the like. VMS users should specify BINARY F 512
and should use RECEIVE/BINARY to receive the NETDATA-format
binary files BITFTP sends them.
To use BITFTP, send mail containing your ftp commands to
"BITFTP@PUCC". The first command to BITFTP must be "FTP"
or "HELP".
The recommended syntax for ftp requests is:
FTP hostname
USER username password
<other ftp subcommands>
QUIT
After the hostname on the FTP command, you may specify
"UUENCODE" or "NETDATA" to tell BITFTP the format in which
you wish to receive files.
(If the username is "anonymous", no password is required;
BITFTP will use your userid and nodeid as the password.)
Note that on many systems passwords are case-sensitive;
that is, the password may be required to be in lower case
or mixed case or upper case. (The same is true of directory
and file names.)
The following is an example of an ftp request:
FTP f.ms.uky.edu
USER anonymous
CD /pub/msdos/Games
DIR
BINARY
GET robotron.arc msdos.robotron
QUIT
BITFTP implements a subset of the ftp subcommands provided
in the IBM TCP/IP and uses the same syntax. Therefore, you
may find it useful to obtain the "IBM TCP/IP for VM Command
Reference Manual", IBM order number GC09-1204.
The currently supported subcommands are:
ACCT -- to send host-dependent account information.
format: ACCT account-information
ASCII -- to change the file transfer type to ASCII.
format: ASCII
BINARY -- to change the file transfer type to image.
format: BINARY <FIXED record-len> <VARIABLE>
CD -- to change the working directory.
format: CD directory
CLOSE -- to disconnect from the foreign host.
format: CLOSE
DIR -- to get a list of directory entries.
format: DIR
EBCDIC -- to change the file transfer type to EBCDIC
format: EBCDIC
GET -- to get a file from the foreign host.
format: GET foreignfile <localfile>
If you specify "localfile", it must be in
the forms "filename.filetype" or "filename",
and the filename and filetype may each be no
more than 8 characters long and may not contain
periods.
LOCSTAT -- to display local status information.
format: LOCSTAT
LS -- to list the files in a directory.
format: LS <name>
PWD -- to print the working directory.
format: PWD
QUIT -- to disconnect from the foreign host.
format: QUIT
STATUS -- to retrieve status information from a foreign host.
format: STATUS <name>
SYSTEM -- to get the name of the foreign host's operating system.
format: SYSTEM
TYPE -- to specify Image, ASCII, or EBCDIC file transfer.
format: TYPE <I|A|E>
The files you request will be sent to you in NETDATA format or
UUENCODED inside mail files.
You will also receive a mail file containing a log of your
ftp session. In that mail file, entries prefixed by ">" are
your original commands; those prefixed by ">>" are your
commands as interpreted by BITFTP and passed to TCPIP; those
prefixed by ">>>" are your commands as interpreted by TCPIP and
passed to the remote host; those prefixed by "<<<" are messages
from the remote host; and those prefixed by ">>>>" are completion
messages from BITFTP.
If BITFTP is unable to connect to the host you specify,
it will send you mail after the first attempt, but will keep
trying at intervals over three days. The only additional mail
files you will receive will be when the connection is made
successfully or when BITFTP gives up after three days.
The load on BITFTP is often very heavy, and network
backlogs are often so great that it may take several days
for a file to get to you once BITFTP sends it, so please be
patient and don't send multiple requests for the same file.
If your system allows you to send interactive messages, you
can inquire about BITFTP's backlog by sending the query
"How are you?", e.g., on a VM system:
TELL BITFTP AT PUCC How are you?
This service is currently under development and is far from
complete. Current plans for improvements include:
1. Acknowledgments via MSG when mail is received and when
processing has been completed.
2. A much more complete HELP facility.
Questions about BITFTP and suggestions for improvements
should be directed to Melinda Varian, MAINT@PUCC on BITNET or
[email protected] on the Internet.
The author gratefully acknowledges the use of the FTP
SUBCOM interface written by David Nessl (DAVID@NERVM), the
SENDJANI EXEC written by Alan Flavell ([email protected]),
the uuencoding utility written by John Fisher (FISHER@RPIECS),
and the RFC822 parsing routine written by Eric Thomas
(ERIC@LEPICS).
|
| Dick,
You haven't said what replies or error messages you are getting. If
you get replies from BITFTP, but errors like "file not found," then you
probably have some difficulty with directory names. You can also strip
out a lot of stuff from your commands. For instance, for your second
example, the following ought to work:
ftp cheops.cis.ohio-state.edu
cd pub/neuroprose
dir
binary
get fahlman.cascor-tr.ps.Z
quit
If your problem is no replies at all, just be patient! 24 hour
turnaround can be just as common as 1 hour service.
Good luck,
Wes
|
|
Re: .3
Use DECWRL::"[email protected]" at the To: prompt, Subject: FTP.
DECWRL::"[email protected]" might also work, John???
I've been using this server quite a while now, w/o problems.
Response time from decwrl to bitftp to xanth and back has been great,
the record has been 20 minutes turnaround time, but don't bet on it.
Looking at your requests, you seem to pretty certain on what you
want. I found it allways handy to insert to insert a DIR command
before the SEND, since in the case of a typo (!�%&?#+@ cAsE
sensitivity) you'll at least know what files were there.
Regards,
<CB>
|
| I send mail to DECWRL::"[email protected]". Subject is ignored.
Here's a sample xanth session and the bitftp reply:
here is the mail I sent (notice the UUENCODE on the FTP line. It tells
the server to UUENCODE binary files:
FTP xanth.cs.odu.edu UUENCODE
USER anonymous wjg
CD amiga
DIR
QUIT
Here is it's reply:
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by decpa.pa.dec.com; id AA05746; Tue, 8 May 90 16:18:26 -0700
Received: from PUCC.PRINCETON.EDU by pucc.PRINCETON.EDU (IBM VM SMTP R1.2.2MX) with BSMTP id 0326; Tue, 08 May 90 19:17:54 EDT
Received: by PUCC (Mailer R2.07) id 7310; Tue, 08 May 90 19:17:56 EDT
Date: Tue, 8 May 1990 19:17:53 EDT
From: Princeton BITNET FTP Server <[email protected]>
To: wjg::guineau
Subject: BITFTP REPLY
19:17:24 > FTP xanth.cs.odu.edu UUENCODE
19:17:24 > USER anonymous wjg
19:17:24 >> OPEN XANTH.CS.ODU.EDU
19:17:32 <<< 220 xanth FTP server (Version 4.209 Thu Jan 11 18:43:38
EST 1990) ready.
19:17:32 >> USER anonymous [email protected]
19:17:34 >>> USER anonymous
19:17:34 <<< 331 Guest login ok, send ident as password.
19:17:34 >>> PASS ********
19:17:34 <<< 230 Guest login ok, access restrictions apply.
19:17:35 > CD amiga
19:17:35 >> CD amiga
19:17:35 >>> CWD amiga
19:17:36 <<< 250 CWD command successful.
19:17:36 > DIR
19:17:36 >> DIR ( DISK
19:17:50 >>> PORT 128,112,129,99,91,216
19:17:50 <<< 200 PORT command successful.
19:17:50 >>> LIST
19:17:50 <<< 150 Opening ASCII mode data connection for /bin/ls (0 by
tes).
19:17:50 <<< 226 Transfer complete.
total 2784
drwx------ 2 13 46 512 Mar 7 13:39 .bad
-rw-rw-r-- 1 13 46 4604 Apr 29 18:05 README
drwxrwxr-x 2 902 46 512 Apr 30 16:08 a3000
drwxrwxr-x 2 13 46 512 Apr 3 16:36 analyticalc
-r--r--r-- 1 13 46 130594 Apr 7 1989 anim.zoo
-r--r--r-- 1 13 46 75016 Jun 28 1989 arp-1.3-doc.zoo
-rw-r--r-- 1 13 46 10342 Jun 15 1989 arp-1.3.tex.Z
lrwxrwxr-x 1 13 46 12 Dec 14 14:29 badge0 -> demos/badge0
lrwxrwxr-x 1 13 46 12 Dec 14 14:29 badge1 -> demos/badge1
lrwxrwxr-x 1 13 46 12 Dec 14 14:29 badge2 -> demos/badge2
-r--r--r-- 1 13 46 759 Jun 20 1989 butils.zoo
-r--r--r-- 1 13 46 878 Jun 20 1989 cc-1.0.zoo
-rw-r--r-- 1 13 46 419490 Nov 27 22:49 commontex.zoo
-r--r--r-- 1 13 46 134089 May 3 12:49 csa-intro.zoo
-r--r--r-- 1 13 46 249735 Apr 7 1989 dbw.zoo
drwxrwxr-x 9 13 46 512 Mar 24 09:16 demos
-r--r--r-- 1 13 46 5726 Apr 7 1989 distpro.zoo
-r--r--r-- 1 13 46 386525 Oct 9 1989 dnet-2.02L.zoo
drwxrwxr-x 2 13 46 512 Apr 11 10:15 fishcon
-r--r--r-- 1 13 46 45887 Apr 9 10:37 fishxref-340.zoo
-r--r--r-- 1 13 46 1422 Apr 23 1989 fixarchon.zoo
-rw-r--r-- 1 13 46 31656 Sep 3 1988 ftek.zoo
-r--r--r-- 1 13 46 106592 Nov 28 10:32 handshake-2.12.zoo
-r--r--r-- 1 13 46 36201 Oct 27 1989 lharc-1.0.zoo
-r--r--r-- 1 13 46 46935 Apr 13 19:10 lhwarp-1.31.zoo
-r--r--r-- 1 13 46 68723 Mar 27 1989 movie.zoo
-r--r--r-- 1 13 46 351587 Feb 23 20:06 plplot-2.6b.zoo
-r--r--r-- 1 13 46 30612 Feb 18 1989 projector.zoo
-r--r--r-- 1 13 46 7885 Nov 16 15:11 pyro.zoo
-r--r--r-- 1 13 46 158037 Dec 17 19:18 rgb-exchange.zoo
drwxr-xr-x 2 13 46 512 Apr 9 09:02 startrekii
-r--r--r-- 1 13 46 204440 Oct 11 1989 stevie-3_7a.zoo
-rw-r--r-- 1 13 46 10023 Apr 28 21:54 tvbstats.zoo
-rw-rw-r-- 1 13 46 79334 Mar 15 15:16 ue2.5e-patches-1-4.zoo
-r--r--r-- 1 13 46 740 Apr 26 1989 uucode.zoo
-r--r--r-- 1 13 46 50458 Nov 26 21:42 warp-1.11.zoo
-rw-rw-r-- 1 13 46 73039 Dec 22 17:21 zoo-2.00.arc
19:17:51 > QUIT
19:17:51 >> CLOSE
19:17:53 >>> QUIT
19:17:53 <<< 221 Goodbye.
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
Received: by decpa.pa.dec.com; id AA05746; Tue, 8 May 90 16:18:26 -0700
Received: from PUCC.PRINCETON.EDU by pucc.PRINCETON.EDU (IBM VM SMTP R1.2.2MX) with BSMTP id 0326; Tue, 08 May 90 19:17:54 EDT
Received: by PUCC (Mailer R2.07) id 7310; Tue, 08 May 90 19:17:56 EDT
Date: Tue, 8 May 1990 19:17:53 EDT
From: Princeton BITNET FTP Server <[email protected]>
To: wjg::guineau
Subject: BITFTP REPLY
Now to get a file (butils.zoo:
FTP xanth.cs.odu.edu UUENCODE
USER anonymous wjg
CD amiga
GET butils.zoo
QUIT
Notice that if a file you want is in a subdirectory, you must CD there first!
Don't include path names in the GET request.
FTP xanth.cs.odu.edu UUENCODE
USER anonymous wjg
CD amiga/a3000
GET wb20pics.zoo
QUIT
|