Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!uwm.edu!linac!att!ucbvax!ASYLUM.SF.CA.US!romkey
From: romkey@ASYLUM.SF.CA.US (John Romkey)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Clarkson 3C503 & PC-NFS
Message-ID: <9103142245.AA07249@asylum.sf.ca.us>
Date: 15 Mar 91 06:45:13 GMT
References: <1728@pilchuck.Data-IO.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: romkey@asylum.sf.ca.us
Organization: The Internet
Lines: 28


   Date: 14 Mar 91 00:19:03 GMT
   From: Cal Jewell <decwrl!uunet.uu.net!pilchuck!jewell>
   I can get PC-NFS to run on the packet driver. I can get 
   WinQVT/NET to run on the packet driver. But, I can't get
   the two to run together. Am I missing something?

I expect so. The packet driver has no provisions for supporting
multiple instances of the same protocol stack (ie: two TCP's). Never
had it, never will. It's a dangerous thing to try to do and unlikely
to work right regardless of the amount of kludgery put into it.

The packet driver is the wrong level to be trying to fix this sort of
problem. It needs to be addressed in the programming interface to the
transport layer (TCP and UDP). There should be only one instance of a
single type of transport layer per machine, unless you're running
multiple network interfaces and appear to the net to be multiple
machines.

We rehash this one about once every week or two. Again, for
everybody's benefit, the packet driver was designed to allow protocol
stacks relative independence of the specific device used to access the
network, and to allow multiple (different) protocol stacks to share
one network device. It was never intended, and will not work, to allow
multiple instances of the same protocol. This applies as well to its
younger siblings, NDIS and ODI.
		- john romkey			Epilogue Technology
USENET/UUCP/Internet:  romkey@asylum.sf.ca.us	FAX: 415 594-1141