forrie@morwyn.UUCP (Forrie Aldrich) (04/05/91)
Has anyone ANY idea as to why BITFTP isn't working anymore? I have sent
many requests to the server and haven't received anything in return.
Any info or leads would be appreciated. Thanks.
Forrie
--
--------------------=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--------------------
Forrest Aldrich, Jr.| ...uunet!eci!morwyn!forrie |forrie@morywn.UUCP
| <email paths> |
CREATIVE CONNECTIONS| ...uunet!zinn!eci!morwyn!forrie |Graphic Illustration
------------------\-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=/------------------
\___ PO Box 1541 - Dover, NH 03820 ___/ forrie@morwyn.UUCP (Forrie Aldrich) (04/22/91)
For those of you who use BITFTP to get your files to the 3b1: I'm curious
about something. I never really had a problem using BITFTP when I was
getting mail sent to a machine that was directly connected to UUNET... but
it seems that when I involve another path with 2 more machines, BITFTP won't
send the files to me... and BITFTP won't respond to the command HELP either,
so I had no choice but to post to the net. Anyone have any ideas as to why
this is a problem? Is there a way to specify the path that the file(s) is/are
to be sent to?
Thanks,
Forrie
--
--------------------=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--------------------
Forrest Aldrich, Jr.| ...uunet!eci!morwyn!forrie |forrie@morwyn.UUCP
| <email paths> |
CREATIVE CONNECTIONS| ...uunet!zinn!eci!morwyn!forrie |Graphic Illustration
------------------\-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=/------------------
\___ PO Box 1541 - Dover, NH 03820 ___/ david@dbk.uucp (David Kozinn) (04/26/91)
In article <91@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes: >For those of you who use BITFTP to get your files to the 3b1: I'm curious >about something. I never really had a problem using BITFTP when I was >getting mail sent to a machine that was directly connected to UUNET... but >it seems that when I involve another path with 2 more machines, BITFTP won't >send the files to me... I believe that the bitftp requires a fully-qualified domain address. Ok, you say, but morwyn.uucp looks like one to me, what's the problem? The problem is that there is no "official" top-level domain called .uucp, so any request with a reply address that points to .uucp usually can't get through. I had this same problem which went away as soon as I started using the FQDN from one of the machines at work. After that, all has worked quite well. -- David Kozinn UUCP: {uunet,mips}!sonyusa!sonyd1!dbk!david Domain: david%dbk@Broadcast.Sony.COM or david@dbk.mony.com GEnie: D.KOZINN
merce@iguana.uucp (Jim Mercer) (04/26/91)
In article <91@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes: >For those of you who use BITFTP to get your files to the 3b1: I'm curious >about something. I never really had a problem using BITFTP when I was >getting mail sent to a machine that was directly connected to UUNET... but >it seems that when I involve another path with 2 more machines, BITFTP won't >send the files to me... and BITFTP won't respond to the command HELP either, >so I had no choice but to post to the net. Anyone have any ideas as to why >this is a problem? Is there a way to specify the path that the file(s) is/are >to be sent to? there are a number of systems that are actively trashing bitftp requests and replies. this is because BITFTP is perceived to be a not a "good thing". i happen to agree. listservers limit the flow of requests, bitftp just spews forth. the systems at work have been swamped twice, resulting in overflowing filesystems. in the first instance, someone ordered an 80 Meg VMS archive. BITFTP, as i understand it was set up to facilitate file transfers between the internet and BITNET. its use has since propigated as widely as users of distantly connected PCBOARD BBS systems. BITFTP is a significant toll on uucpNET (ie USENET less internet). at least, that's my opinion. -- [ Jim Mercer work: jim@lsuc.on.ca home: merce@iguana.uucp +1 519 570-3467 ] [ "Anarchists Unite!" - seen spray painted on a wall ]
john@chance.UUCP (John R. MacMillan) (04/27/91)
|For those of you who use BITFTP to get your files to the 3b1: I'm curious |about something. I never really had a problem using BITFTP when I was |getting mail sent to a machine that was directly connected to UUNET... but |it seems that when I involve another path with 2 more machines, BITFTP won't |send the files to me... and BITFTP won't respond to the command HELP either, |so I had no choice but to post to the net. Anyone have any ideas as to why |this is a problem? It may be that one or more of the sites is dropping BITFTP traffic on the floor. Numerous sysadmins I know have had to deal with people trying to pump large volumes of BITFTP traffic through their sites, tying up modems and disk space (sometimes long distance as well) without so much as asking, and so will no longer allow any BITFTP requests through. Like many things, the abusers of BITFTP have given it a bad name.
bruce@balilly (Bruce Lilly) (04/27/91)
In article <1991Apr26.222142.20836@chance.UUCP> john@chance.UUCP (John R. MacMillan) writes: >|For those of you who use BITFTP to get your files to the 3b1: I'm curious >|about something. I never really had a problem using BITFTP when I was >|getting mail sent to a machine that was directly connected to UUNET... but >|it seems that when I involve another path with 2 more machines, BITFTP won't >|send the files to me... and BITFTP won't respond to the command HELP either, >|so I had no choice but to post to the net. Anyone have any ideas as to why >|this is a problem? > >It may be that one or more of the sites is dropping BITFTP traffic on >the floor. [ ... ] It's also quite likely that BITNET bitrot is causing the message to be dropped. If I send a BITFTP request from home (address bruce%blilly@broadcast.sony.com) it will fail because BITNET horribly mangles the address (I don't have a copy of the exact mangling, but I recall that, for a start, the user name was converted to upper case, and the RFC822/1123 ``local part'' of the address was damaged, causing the message to be dropped as undeliverable at broadcast.sony.com). It works at work (address bruce@broadcast.sony.com). BITFTP manages to mangle return addresses so badly that a response may not make it back to the requestor even though all intermediate site are willing and able to handle the volume. -- Bruce Lilly blilly!balilly!bruce@sonyd1.Broadcast.Sony.COM