Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!uunet!naitc!karl From: karl@naitc.uucp (Karl Denninger) Newsgroups: comp.dcom.lans Subject: Re: PC/NFS and NCSA Telnet reprised Summary: Is this a generic shortcoming, or something which should be fixed? Message-ID: <1990Aug23.161618.20215@naitc.uucp> Date: 23 Aug 90 16:16:18 GMT References: <1990Aug20.185329.8200@naitc.uucp> <999@ncis.tis.llnl.gov> Reply-To: karl@naitc.naitc.com (Karl Denninger) Organization: A.C. Nielsen Bannockburn, IL Lines: 46 In article ssw@cica.cica.indiana.edu (Steve Wallace) writes: >There is a driver for PC-NFS that allows it to use the packet >driver, but the packet driver only supports one application per >protocol type. You could run Novell NetWare and PC-NFS (NetWare >uses IPX and PC-NFS uses ARP, and IP) or NetWare and NCSA telnet. >You can NOT use two programs (i.e. NCSA telnet and PC-NFS) which >use the same protocol. Should someone (perhaps myself) endeavor to fix this? Or is it inherent in the protocol and technology being used? I can't think of a technical limitation on this, but I could be wrong. I guess arp's could get a little hairy (who handles them?!) but socket connections ought to be ok as long as the protocols in use don't use the same sockets. In the case of Telnet and NFS, they don't do this, so it >should< work, at least in my mind. Of course it doesn't; I've tried it. If NCSA is loaded first you can use it -- and then start NFS. As soon as PC/NFS is started (net start rdr) then NCSA can't find a driver to attach to anymore, and it says "sorry!". One possible solution is to use two ethernet cards, but that's kludgy and not what I'd like to do if possible. An annoying thing with the CUTE version for NFS is that it doesn't pay any attention to your definition of the gateways in config.tel. That is, you have to point PC/NFS at the right gateway location, or it won't work off your subnet. Since PC/NFS doesn't listen to RIP broadcasts, this is a real drag; you can't move a gateway without going to all kinds of trouble! At least the nameserver and RARP stuff does work; I knew there was a God. :-) There's another issue -- we have a package which does an "X" server on a PC. Now it would be real nice if it could coexist with PC/NFS and the packet drivers as well. Note that Macs CAN do this, they have a common driver which supports all kinds of things at once, and they even manage to run NCSA Telnet and the other stuff concurrently without hassles! I would think that the PC could do this too... but so far I've been disappointed. Anyone want to take a stab at why I'm all wet on trying to accomplish this? -- Karl Denninger AC Nielsen kdenning@ksun.naitc.com (708) 317-3285 Disclaimer: Contents represent opinions of the author; I do not speak for AC Nielsen on Usenet.