Xref: utzoo comp.protocols.tcp-ip.ibmpc:5948 comp.dcom.lans:8202
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!ysub!psuvm!cunyvm!rohvm1!rbyaml
From: RBYAML@ROHVM1.BITNET (Aengus Lawlor)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.dcom.lans
Subject: Re: NCSA ftp problem
Message-ID: <91144.182624RBYAML@ROHVM1.BITNET>
Date: 24 May 91 23:26:24 GMT
References: <227@gordon.UUCP>
Organization: Rohm and Haas Company
Lines: 22

In article <227@gordon.UUCP>, jpd@gordon.UUCP (Jim Drummey) says:
>We've got the 3c503 packet driver running along with IPX and NET3 and
>are having no problems accessing the Novell servers. We also use NCSA Telnet
>and the lpr facility to our unix machines ..that works fine too. The ftp
>however, allows a login OK but hangs as soon as transfer starts. Is there a
>known problem with the NCSA ftp? Other ftps work.
>========================================================================
>Jim Drummey
>Access Technology, Inc.
>Natick, MA 01760              harvard!necntc!gordon!jpd
>========================================================================
We use the same configuration here (3C503s, packet drivers, ipx for packet
drivers, lpr) but with Clarksons CUTCP, which is based on NCSA. It all
works fine here, including FTP. As far as I can remember, it worked fine
before we moved from NCSA to CUTCP, so that shouldn't be a problem.

Aengus.
--
RBYAML@ROHMHAAS.COM                    Aengus Lawlor
RBYAML@ROHVM1.BITNET                   (who used to be ALAWLOR@DIT.IE)
"How about some of that famous Dublin wit, Barman?"
"Certainly, sir. Would that be Dry or Sparkling?"